Wireshark · Wireshark-dev: Re: [Wireshark-dev] Wireshark-dev Digest, Vol 48, Issue 38

[Vishal Kumar Singh <vishal.ismdh@xxxxxxxxx>]

Hi Bruno and All,

I simply created the makefile and run the command make. I am not very sure if I have to do something before that or not like 
(1) run ./configure

Probably, the error is in the makefile, because in all the dissector, i am getting the same list of errors.

Vishal Kumar Singh
Software Engineer
A R I C E N T

On Tue, May 18, 2010 at 12:30 AM, <wireshark-dev-request@xxxxxxxxxxxxx> wrote:

Send Wireshark-dev mailing list submissions to
       wireshark-dev@xxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
       https://wireshark.org/mailman/listinfo/wireshark-dev
or, via email, send a message with subject or body 'help' to
       wireshark-dev-request@xxxxxxxxxxxxx

You can reach the person managing the list at
       wireshark-dev-owner@xxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wireshark-dev digest..."


Today's Topics:

  1. Re: Wireshark 1.4 (Stephen Fisher)
  2. Re: Wireshark 1.4 (Stephen Fisher)
  3. buildbot failure in Wireshark (development) on    Windows-7-x64
     (buildbot-no-reply@xxxxxxxxxxxxx)
  4. Re: Wireshark 1.4 (Jaap Keuter)
  5. Regarding Compilation of Custom Dissector (Vishal Kumar Singh)
  6. Re: Regarding Compilation of Custom Dissector (Bruno Matos)
  7. buildbot failure in Wireshark (development) on
     Ubuntu-10.04-x64 (buildbot-no-reply@xxxxxxxxxxxxx)
  8. buildbot failure in Wireshark (development) on    Windows-7-x64
     (buildbot-no-reply@xxxxxxxxxxxxx)
  9. buildbot failure in Wireshark (development) on
     Solaris-10-SPARC (buildbot-no-reply@xxxxxxxxxxxxx)


----------------------------------------------------------------------

Message: 1
Date: Sun, 16 May 2010 18:42:29 -0600
From: Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Wireshark 1.4
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <20100517004229.GA21637@shadow.local>
Content-Type: text/plain; charset=us-ascii

On Sat, May 15, 2010 at 10:22:44AM +0200, Jaap Keuter wrote:

> Indeed, I'm wracking my brain. Check the docbook directory for the
> current list.

Thanks.  This should help from the Unix CLI: svn log -r
{2009-05-16}:{2010-05-16} > svn_log and search for ourselves :)


--
Steve


------------------------------

Message: 2
Date: Sun, 16 May 2010 19:07:00 -0600
From: Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Wireshark 1.4
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <20100517010700.GA73116@shadow.local>
Content-Type: text/plain; charset=us-ascii

On Tue, May 11, 2010 at 04:40:36PM -0700, Gerald Combs wrote:

> If you have added a new feature in the past year, please review the
> release notes to make sure it's listed.

Besides the initial new packet list work, it looks like I didn't add
many visible features in the last year:

 - The new packet list's columns can be dragged and drop to re-order
 - capinfos now displays the snapshot length of a capture file
 - Wireshark now properly detects MIT Kerberos 1.5 and higher

Not sure if the second two are even worth mentioning though, especially
the third.

The new packet list has been a default on feature for a while now.  Are
we going to pull the old code/configure script option for this release
or leave it in?


--
Steve


------------------------------

Message: 3
Date: Sun, 16 May 2010 20:05:29 -0700
From: buildbot-no-reply@xxxxxxxxxxxxx
Subject: [Wireshark-dev] buildbot failure in Wireshark (development)
       on      Windows-7-x64
To: wireshark-dev@xxxxxxxxxxxxx
Message-ID: <20100517030530.65766861F4@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development).
Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/292

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: windows-7-x64

Build Reason:
Build Source Stamp: 32837
Blamelist: morriss

BUILD FAILED: failed nmake docs

sincerely,
 -The Buildbot



------------------------------

Message: 4
Date: Mon, 17 May 2010 08:30:24 +0200
From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Subject: Re: [Wireshark-dev] Wireshark 1.4
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <4BF0E280.1060308@xxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 05/17/2010 03:07 AM, Stephen Fisher wrote:
> On Tue, May 11, 2010 at 04:40:36PM -0700, Gerald Combs wrote:
>
>> If you have added a new feature in the past year, please review the
>> release notes to make sure it's listed.
>
> Besides the initial new packet list work, it looks like I didn't add
> many visible features in the last year:
>
>    - The new packet list's columns can be dragged and drop to re-order
>    - capinfos now displays the snapshot length of a capture file
>    - Wireshark now properly detects MIT Kerberos 1.5 and higher
>
> Not sure if the second two are even worth mentioning though, especially
> the third.
>
> The new packet list has been a default on feature for a while now.  Are
> we going to pull the old code/configure script option for this release
> or leave it in?
>

Well, as long as there are some serious usability bugs[1] I would be presenting
the old packet list to my users. I would like to see the attention going to
addressing these issues, and, for now, leave the old code in.

Thanks,
Jaap

[1] http://wiki.wireshark.org/Development/OptimizePacketList



------------------------------

Message: 5
Date: Mon, 17 May 2010 18:48:15 +0530
From: Vishal Kumar Singh <vishal.ismdh@xxxxxxxxx>
Subject: [Wireshark-dev] Regarding Compilation of Custom Dissector
To: wireshark-dev@xxxxxxxxxxxxx
Message-ID:
       <AANLkTilJmsdtSKEwLlnYK5Gs8LsP9leMrr-jX7phlrim@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi All,

When I run the Makefile using make. It gives following error :-

packet-lte_rlc.h:31:21: error: config.h: No such file or directory
packet-lte_rlc.h:37:25: error: epan/packet.h: No such file or directory

What might me the probable reason for this ? Please, help me out.

Best Regards,
Vishal Kumar Singh
Software Engineer
A R I C E N T
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.wireshark.org/lists/wireshark-dev/attachments/20100517/1fa06f7f/attachment.htm

------------------------------

Message: 6
Date: Mon, 17 May 2010 14:40:46 +0100
From: Bruno Matos <bruno.matos@xxxxxxxxx>
Subject: Re: [Wireshark-dev] Regarding Compilation of Custom Dissector
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <262F245D-2BB4-4CF0-B6B9-9E27A5425CFE@xxxxxxxxx>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes


On 2010/05/17, at 14:18, Vishal Kumar Singh wrote:

> Hi All,
>
> When I run the Makefile using make. It gives following error :-
>
> packet-lte_rlc.h:31:21: error: config.h: No such file or directory
> packet-lte_rlc.h:37:25: error: epan/packet.h: No such file or
> directory
>
> What might me the probable reason for this ? Please, help me out.
>
> Best Regards,
> Vishal Kumar Singh
> Software Engineer
> A R I C E N T
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe


Hi Vishai,

What were the steps you take?

Regards.

--
Bruno Matos
bruno.matos@xxxxxxxxx





------------------------------

Message: 7
Date: Mon, 17 May 2010 08:32:51 -0700
From: buildbot-no-reply@xxxxxxxxxxxxx
Subject: [Wireshark-dev] buildbot failure in Wireshark (development)
       on      Ubuntu-10.04-x64
To: wireshark-dev@xxxxxxxxxxxxx
Message-ID: <20100517153252.E31FF861FA@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark (development).
Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/56

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: ubuntu-10.04-x64

Build Reason:
Build Source Stamp: 32842
Blamelist: morriss

BUILD FAILED: failed svn

sincerely,
 -The Buildbot



------------------------------

Message: 8
Date: Mon, 17 May 2010 08:34:11 -0700
From: buildbot-no-reply@xxxxxxxxxxxxx
Subject: [Wireshark-dev] buildbot failure in Wireshark (development)
       on      Windows-7-x64
To: wireshark-dev@xxxxxxxxxxxxx
Message-ID: <20100517153411.F06A086028@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development).
Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/295

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: windows-7-x64

Build Reason:
Build Source Stamp: 32842
Blamelist: morriss

BUILD FAILED: failed svn

sincerely,
 -The Buildbot



------------------------------

Message: 9
Date: Mon, 17 May 2010 08:51:18 -0700
From: buildbot-no-reply@xxxxxxxxxxxxx
Subject: [Wireshark-dev] buildbot failure in Wireshark (development)
       on      Solaris-10-SPARC
To: wireshark-dev@xxxxxxxxxxxxx
Message-ID: <20100517155118.93DB157000@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain

The Buildbot has detected a new failure of Solaris-10-SPARC on Wireshark (development).
Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/Solaris-10-SPARC/builds/214

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: solaris-10-sparc

Build Reason:
Build Source Stamp: 32842
Blamelist: morriss

BUILD FAILED: failed svn

sincerely,
 -The Buildbot



------------------------------

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev


End of Wireshark-dev Digest, Vol 48, Issue 38
*********************************************