Re: [Wireshark-dev] Problem during compilation

2010-04-27 Thread Maynard, Chris 
“I'll probably put VS2008 Express in a VM (or use a linux VM) for compiling 
Wireshark in which case the problem will be fixed for me.”

… at least until we switch to VS2010 ☺

- Chris
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-27 Thread Graham Bloice 
On 27/04/2010 16:39, Maynard, Chris wrote:
>
> Hi Graham,
>
> While I don’t compile with VS2005, obviously many folks still do.  If
> you ever do have the time, it would probably be beneficial to others
> if you would post your patches, either here on –dev or through bugzilla.
>
> Thanks.
>
> - Chris
>
>  
>
>  
>
>
The problem I have is that while my changes do work for me in producing
a working Wireshark, I haven't currently got the time to correctly fix
all the issues with detecting the compiler version, instead of the SDK. 
I suppose I should at least raise an issue on Bugzilla in case someone
else can tackle it.  I'll try to do the Bugzilla thing before the end of
the week.

I'm almost at the point of getting a new machine at work, and although
I'll still have to use VS2005 for my day job, I'll probably put VS2008
Express in a VM (or use a linux VM) for compiling Wireshark in which
case the problem will be fixed for me.

-- 
Regards,

Graham Bloice

___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-27 Thread Maynard, Chris 
Hi Graham,
While I don’t compile with VS2005, obviously many folks still do.  If you ever 
do have the time, it would probably be beneficial to others if you would post 
your patches, either here on –dev or through bugzilla.
Thanks.
- Chris


From: wireshark-dev-boun...@wireshark.org 
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice
Sent: Tuesday, April 27, 2010 4:56 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Problem during compilation

On 27/04/2010 05:38, ankur madan wrote:
So,is there any other solution for this problem.due to some reason i have 2 
work on VS 2005 only.looking forward for a response.
There are three main issues you will face when trying to compile Wireshark with 
VS2005:

1)  The makefiles and sources attempt to conditionally compile code based on 
the compiler version.  IMHO this is wrong and it should be based on the SDK in 
use.  After all, you can use the latest (Win7) SDK with VS2005.  These are 
mainly around the area of file dialogs, and IPV6 definitions.

2) Compiler behavioural differences, this leads to odd errors with compilation 
like the one you ran into

3)  Some 3rd party libraries are linked with c run-times that are later than 
those supplied with VS2005 (Lua).  This means that the code will compile and 
link but at runtime an error will be generated.  The solution here is to 
specify earlier versions of the library (5.1 for Lua) in config.nmake.

I don't know if some of these issues have been solved and I only carry the 
changes in my local working copy for historical purposes, but they allow me to 
build a working Wireshark with VS2005 (obviously I don't see any 802.15.4 
frames).

I don't have the time to push these changes upstream (particularly the changes 
to use the SDK version not the compiler as they are extensive), especially as 
VS2005 is now 2 versions off the latest compilers.  I can attach a patch that 
includes all my changes if you wish.



--

Regards,



Graham Bloice
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-27 Thread ankur madan 
thanks graham,it worked for me.its compiling successfully

thanks
ankur

On Tue, Apr 27, 2010 at 2:26 PM, Graham Bloice
wrote:

>  On 27/04/2010 05:38, ankur madan wrote:
>
> So,is there any other solution for this problem.due to some reason i have 2
> work on VS 2005 only.looking forward for a response.
>
> There are three main issues you will face when trying to compile Wireshark
> with VS2005:
>
> 1)  The makefiles and sources attempt to conditionally compile code based
> on the compiler version.  IMHO this is wrong and it should be based on the
> SDK in use.  After all, you can use the latest (Win7) SDK with VS2005.
> These are mainly around the area of file dialogs, and IPV6 definitions.
>
> 2) Compiler behavioural differences, this leads to odd errors with
> compilation like the one you ran into
>
> 3)  Some 3rd party libraries are linked with c run-times that are later
> than those supplied with VS2005 (Lua).  This means that the code will
> compile and link but at runtime an error will be generated.  The solution
> here is to specify earlier versions of the library (5.1 for Lua) in
> config.nmake.
>
> I don't know if some of these issues have been solved and I only carry the
> changes in my local working copy for historical purposes, but they allow me
> to build a working Wireshark with VS2005 (obviously I don't see any 802.15.4
> frames).
>
> I don't have the time to push these changes upstream (particularly the
> changes to use the SDK version not the compiler as they are extensive),
> especially as VS2005 is now 2 versions off the latest compilers.  I can
> attach a patch that includes all my changes if you wish.
>
> --
> Regards,
>
> Graham Bloice
>
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-27 Thread Graham Bloice 
On 27/04/2010 05:38, ankur madan wrote:
> So,is there any other solution for this problem.due to some reason i
> have 2 work on VS 2005 only.looking forward for a response.
>
There are three main issues you will face when trying to compile
Wireshark with VS2005:

1)  The makefiles and sources attempt to conditionally compile code
based on the compiler version.  IMHO this is wrong and it should be
based on the SDK in use.  After all, you can use the latest (Win7) SDK
with VS2005.  These are mainly around the area of file dialogs, and IPV6
definitions.

2) Compiler behavioural differences, this leads to odd errors with
compilation like the one you ran into

3)  Some 3rd party libraries are linked with c run-times that are later
than those supplied with VS2005 (Lua).  This means that the code will
compile and link but at runtime an error will be generated.  The
solution here is to specify earlier versions of the library (5.1 for
Lua) in config.nmake.

I don't know if some of these issues have been solved and I only carry
the changes in my local working copy for historical purposes, but they
allow me to build a working Wireshark with VS2005 (obviously I don't see
any 802.15.4 frames).

I don't have the time to push these changes upstream (particularly the
changes to use the SDK version not the compiler as they are extensive),
especially as VS2005 is now 2 versions off the latest compilers.  I can
attach a patch that includes all my changes if you wish.

-- 
Regards,

Graham Bloice

___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-27 Thread Guy Harris 

On Apr 26, 2010, at 9:38 PM, ankur madan wrote:

> So,is there any other solution for this problem.

Use the latest version from SVN; I checked in a change that should fix the 
compiler warnings.
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-27 Thread Guy Harris 

On Apr 26, 2010, at 2:35 AM, Graham Bloice wrote:

> IMHO the current code is incorrect as it incorrectly casts a 32 bit value to 
> a 64 bit one and then calls proto_tree_add_uint64 with it when the value 
> really is a 32 bit one (lines 981-985):
> 
> if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
>   packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
>   proto_tree_add_uint64(field_tree, hf_ieee802154_aux_sec_key_source, 
> tvb, offset, 4, packet->key_source.addr32);
>   proto_item_set_len(ti, 1 + 4);
>   offset += sizeof (guint32);

That particular *instance* of the "Key Source for processing of the protected 
frame" happens to be 32 bits.

The one right after it, however, happens to be 64 bits.

The only change I could see making would be to make 
hf_ieee802154_aux_sec_key_source an FT_BYTES field, if it's not an integral 
value but just a collection of bytes.

The only bug is that, in line 982, casting a guint32 to a guint64 and then 
assigning the result to a guint32 is silly.  Just get rid of the cast.

Why that's not being picked up by the buildbot, I don't know.  Maybe some 
versions of MSVC catch it and others don't?

> and the other errors simply need a cast to gchar to allow them to compile 
> (lines 2006 - 2013).
> 
> I've attached a patch that works for me.

I've checked in a change to remove the one cast and add the others.  (You can't 
use proto_tree_add_uint() to add an FT_UINT64 field such as 
"wpan.aux_sec.key_source".)
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread ankur madan 
So,is there any other solution for this problem.due to some reason i have 2
work on VS 2005 only.looking forward for a response.

On Tue, Apr 27, 2010 at 1:32 AM, Jeff Morriss wrote:

> Graham Bloice wrote:
> > On 26/04/2010 10:35, Graham Bloice wrote:
> >> On 26/04/2010 10:10, ankur madan wrote:
> >>> I have latest version code from the svn and latest development
> >>> wireshark version.1.3.4 installed.i am still not able to resolve this
> >>> issue.any help or comments are welcome
> >>>
> >>> thanks
> >>> ankur
> >>>
> >>> On Mon, Apr 26, 2010 at 12:51 PM, ankur madan  >>> > wrote:
> >>>
> >>> I am compiling on windows XP n 32 bit.
> >>>
> >>>
> >>> On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher
>  >>> mailto:st...@stephen-fisher.com>>
> wrote:
> >>>
> >>> On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:
> >>>
> >>> > packet-ieee802154.c(982) : warning C4244: '=' : conversion
> from
> >>> > 'guint64' to 'gu int32', possible loss of data
> >>>
> >>> I see that you're compiling on Windows, but which version and
> >>> is it
> >>> 32-bit or 64-bit?
> >>>
> >>>
> >> Personally I'm just carrying fixes to this in my local source tree as
> >> I haven't had time to push a patch back into the repo.  I don't know
> >> why this compiles OK on the buildbot and not with VC8.
> >>
> >> IMHO the current code is incorrect as it incorrectly casts a 32 bit
> >> value to a 64 bit one and then calls proto_tree_add_uint64 with it
> >> when the value really is a 32 bit one (lines 981-985):
> >>
> >> if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
> >>   packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
> >>   proto_tree_add_uint64(field_tree,
> >> hf_ieee802154_aux_sec_key_source, tvb, offset, 4,
> >> packet->key_source.addr32);
> >>   proto_item_set_len(ti, 1 + 4);
> >>   offset += sizeof (guint32);
> >>
> >> and the other errors simply need a cast to gchar to allow them to
> >> compile (lines 2006 - 2013).
> >>
> >> I've attached a patch that works for me.
> >>
> > Oops.  Compile before posting, the last second change to
> > proto_tree_add_uint64 should have been to proto_tree_add_uint.
> > Corrected patch supplied.
> >
> > Also note that if you are using VC8 you may run into other compilation
> > or run-time issues.  I strongly recommend you grab a copy of the VS 2008
> > Express edition or even the 2010 version if you want to live at the
> > bleeding edge.
>
> The problem with this patch is that hf_ieee802154_aux_sec_key_source is
> an FT_UINT64.  Trying to use proto_tree_add_uint() on it will result in
> a dissector assertion (see epan/proto.c: proto_tree_add_uint()).
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread Jeff Morriss 
Graham Bloice wrote:
> On 26/04/2010 10:35, Graham Bloice wrote:
>> On 26/04/2010 10:10, ankur madan wrote:
>>> I have latest version code from the svn and latest development 
>>> wireshark version.1.3.4 installed.i am still not able to resolve this 
>>> issue.any help or comments are welcome
>>>  
>>> thanks
>>> ankur
>>>
>>> On Mon, Apr 26, 2010 at 12:51 PM, ankur madan >> > wrote:
>>>
>>> I am compiling on windows XP n 32 bit.
>>>
>>>
>>> On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher
>>> mailto:st...@stephen-fisher.com>> wrote:
>>>
>>> On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:
>>>
>>> > packet-ieee802154.c(982) : warning C4244: '=' : conversion from
>>> > 'guint64' to 'gu int32', possible loss of data
>>>
>>> I see that you're compiling on Windows, but which version and
>>> is it
>>> 32-bit or 64-bit?
>>>
>>>
>> Personally I'm just carrying fixes to this in my local source tree as 
>> I haven't had time to push a patch back into the repo.  I don't know 
>> why this compiles OK on the buildbot and not with VC8.
>>
>> IMHO the current code is incorrect as it incorrectly casts a 32 bit 
>> value to a 64 bit one and then calls proto_tree_add_uint64 with it 
>> when the value really is a 32 bit one (lines 981-985):
>>
>> if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
>>   packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
>>   proto_tree_add_uint64(field_tree, 
>> hf_ieee802154_aux_sec_key_source, tvb, offset, 4, 
>> packet->key_source.addr32);
>>   proto_item_set_len(ti, 1 + 4);
>>   offset += sizeof (guint32);
>>
>> and the other errors simply need a cast to gchar to allow them to 
>> compile (lines 2006 - 2013).
>>
>> I've attached a patch that works for me.
>>
> Oops.  Compile before posting, the last second change to 
> proto_tree_add_uint64 should have been to proto_tree_add_uint.  
> Corrected patch supplied.
> 
> Also note that if you are using VC8 you may run into other compilation 
> or run-time issues.  I strongly recommend you grab a copy of the VS 2008 
> Express edition or even the 2010 version if you want to live at the 
> bleeding edge.

The problem with this patch is that hf_ieee802154_aux_sec_key_source is 
an FT_UINT64.  Trying to use proto_tree_add_uint() on it will result in 
a dissector assertion (see epan/proto.c: proto_tree_add_uint()).
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread Graham Bloice 
On 26/04/2010 11:36, ankur madan wrote:
> Hi,
>the error which i was getting in packet-ieee802154.c has been
> resolved using the patch given.Now i am getting following linking error:
>  
>Creating library libwireshark.lib and object libwireshark.exp
> GeoIP.lib(GeoIP.obj) : fatal error LNK1103: debugging information
> corrupt; recom
> pile module
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\l
> ink.EXE"' : return code '0x44f'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\n
> make.exe"' : return code '0x2'
> Stop.
>  
>
As I mentioned building with VC8 (VS2005) is not easy.  You can either
switch to VC 2008 (Express is free as in beer) as recommended, or edit
config.nmake to disable GEOIP functionality.  You may still need to more
than that though to complete a VC8 compile as the Lua library is
compiled with a later version that leads to C run-time issues.

-- 
Regards,

Graham Bloice

___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread ankur madan 
Hi,
   the error which i was getting in packet-ieee802154.c has been resolved
using the patch given.Now i am getting following linking error:

   Creating library libwireshark.lib and object libwireshark.exp
GeoIP.lib(GeoIP.obj) : fatal error LNK1103: debugging information corrupt;
recom
pile module
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
8\VC\BIN\l
ink.EXE"' : return code '0x44f'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
8\VC\BIN\n
make.exe"' : return code '0x2'
Stop.

thanks
ankur


On Mon, Apr 26, 2010 at 3:23 PM, Graham Bloice
wrote:

>   On 26/04/2010 10:35, Graham Bloice wrote:
>
> On 26/04/2010 10:10, ankur madan wrote:
>
> I have latest version code from the svn and latest development wireshark
> version.1.3.4 installed.i am still not able to resolve this issue.any help
> or comments are welcome
>
> thanks
> ankur
>
> On Mon, Apr 26, 2010 at 12:51 PM, ankur madan wrote:
>
>> I am compiling on windows XP n 32 bit.
>>
>>
>> On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher > > wrote:
>>
>>> On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:
>>>
>>> > packet-ieee802154.c(982) : warning C4244: '=' : conversion from
>>> > 'guint64' to 'gu int32', possible loss of data
>>>
>>> I see that you're compiling on Windows, but which version and is it
>>> 32-bit or 64-bit?
>>>
>>>
> Personally I'm just carrying fixes to this in my local source tree as I
> haven't had time to push a patch back into the repo.  I don't know why this
> compiles OK on the buildbot and not with VC8.
>
> IMHO the current code is incorrect as it incorrectly casts a 32 bit value
> to a 64 bit one and then calls proto_tree_add_uint64 with it when the value
> really is a 32 bit one (lines 981-985):
>
> if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
>   packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
>   proto_tree_add_uint64(field_tree,
> hf_ieee802154_aux_sec_key_source, tvb, offset, 4,
> packet->key_source.addr32);
>   proto_item_set_len(ti, 1 + 4);
>   offset += sizeof (guint32);
>
> and the other errors simply need a cast to gchar to allow them to compile
> (lines 2006 - 2013).
>
> I've attached a patch that works for me.
>
> Oops.  Compile before posting, the last second change to
> proto_tree_add_uint64 should have been to proto_tree_add_uint.  Corrected
> patch supplied.
>
> Also note that if you are using VC8 you may run into other compilation or
> run-time issues.  I strongly recommend you grab a copy of the VS 2008
> Express edition or even the 2010 version if you want to live at the bleeding
> edge.
>
> --
> Regards,
>
> Graham Bloice
>
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread Graham Bloice 
On 26/04/2010 10:35, Graham Bloice wrote:
> On 26/04/2010 10:10, ankur madan wrote:
>> I have latest version code from the svn and latest development
>> wireshark version.1.3.4 installed.i am still not able to resolve this
>> issue.any help or comments are welcome
>>  
>> thanks
>> ankur
>>
>> On Mon, Apr 26, 2010 at 12:51 PM, ankur madan > > wrote:
>>
>> I am compiling on windows XP n 32 bit.
>>
>>
>> On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher
>> mailto:st...@stephen-fisher.com>> wrote:
>>
>> On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:
>>
>> > packet-ieee802154.c(982) : warning C4244: '=' : conversion from
>> > 'guint64' to 'gu int32', possible loss of data
>>
>> I see that you're compiling on Windows, but which version and
>> is it
>> 32-bit or 64-bit?
>>
>>
> Personally I'm just carrying fixes to this in my local source tree as
> I haven't had time to push a patch back into the repo.  I don't know
> why this compiles OK on the buildbot and not with VC8.
>
> IMHO the current code is incorrect as it incorrectly casts a 32 bit
> value to a 64 bit one and then calls proto_tree_add_uint64 with it
> when the value really is a 32 bit one (lines 981-985):
>
> if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
>   packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
>   proto_tree_add_uint64(field_tree,
> hf_ieee802154_aux_sec_key_source, tvb, offset, 4,
> packet->key_source.addr32);
>   proto_item_set_len(ti, 1 + 4);
>   offset += sizeof (guint32);
>
> and the other errors simply need a cast to gchar to allow them to
> compile (lines 2006 - 2013).
>
> I've attached a patch that works for me.
>
Oops.  Compile before posting, the last second change to
proto_tree_add_uint64 should have been to proto_tree_add_uint. 
Corrected patch supplied.

Also note that if you are using VC8 you may run into other compilation
or run-time issues.  I strongly recommend you grab a copy of the VS 2008
Express edition or even the 2010 version if you want to live at the
bleeding edge.

-- 
Regards,

Graham Bloice

Index: packet-ieee802154.c
===
--- packet-ieee802154.c (revision 32563)
+++ packet-ieee802154.c (working copy)
@@ -979,8 +979,8 @@
 field_tree = proto_item_add_subtree(ti, ett_ieee802154_aux_sec_key_id);
 /* Add key source, if it exists. */
 if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
-  packet->key_source.addr32 = (guint64) tvb_get_ntohl(tvb, offset);
-  proto_tree_add_uint64(field_tree, hf_ieee802154_aux_sec_key_source, 
tvb, offset, 4, packet->key_source.addr32);
+  packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
+  proto_tree_add_uint(field_tree, hf_ieee802154_aux_sec_key_source, 
tvb, offset, 4, packet->key_source.addr32);
   proto_item_set_len(ti, 1 + 4);
   offset += sizeof (guint32);
 }
@@ -2003,14 +2003,14 @@
 if (adata) block[i] |= (1 << 6); /* Adata */
 i++;
 /* Nonce: Source Address || Frame Counter || Security Level */
-block[i++] = (addr >> 56) & 0xff;
-block[i++] = (addr >> 48) & 0xff;
-block[i++] = (addr >> 40) & 0xff;
-block[i++] = (addr >> 32) & 0xff;
-block[i++] = (addr >> 24) & 0xff;
-block[i++] = (addr >> 16) & 0xff;
-block[i++] = (addr >> 8) & 0xff;
-block[i++] = (addr >> 0) & 0xff;
+block[i++] = (gchar)((addr >> 56) & 0xff);
+block[i++] = (gchar)((addr >> 48) & 0xff);
+block[i++] = (gchar)((addr >> 40) & 0xff);
+block[i++] = (gchar)((addr >> 32) & 0xff);
+block[i++] = (gchar)((addr >> 24) & 0xff);
+block[i++] = (gchar)((addr >> 16) & 0xff);
+block[i++] = (gchar)((addr >> 8) & 0xff);
+block[i++] = (gchar)((addr >> 0) & 0xff);
 block[i++] = (counter >> 24) & 0xff;
 block[i++] = (counter >> 16) & 0xff;
 block[i++] = (counter >> 8) & 0xff;
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread Graham Bloice 
On 26/04/2010 10:10, ankur madan wrote:
> I have latest version code from the svn and latest development
> wireshark version.1.3.4 installed.i am still not able to resolve this
> issue.any help or comments are welcome
>  
> thanks
> ankur
>
> On Mon, Apr 26, 2010 at 12:51 PM, ankur madan  > wrote:
>
> I am compiling on windows XP n 32 bit.
>
>
> On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher
> mailto:st...@stephen-fisher.com>> wrote:
>
> On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:
>
> > packet-ieee802154.c(982) : warning C4244: '=' : conversion from
> > 'guint64' to 'gu int32', possible loss of data
>
> I see that you're compiling on Windows, but which version and
> is it
> 32-bit or 64-bit?
>
>
Personally I'm just carrying fixes to this in my local source tree as I
haven't had time to push a patch back into the repo.  I don't know why
this compiles OK on the buildbot and not with VC8.

IMHO the current code is incorrect as it incorrectly casts a 32 bit
value to a 64 bit one and then calls proto_tree_add_uint64 with it when
the value really is a 32 bit one (lines 981-985):

if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
  packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
  proto_tree_add_uint64(field_tree,
hf_ieee802154_aux_sec_key_source, tvb, offset, 4,
packet->key_source.addr32);
  proto_item_set_len(ti, 1 + 4);
  offset += sizeof (guint32);

and the other errors simply need a cast to gchar to allow them to
compile (lines 2006 - 2013).

I've attached a patch that works for me.

-- 
Regards,

Graham Bloice

Index: packet-ieee802154.c
===
--- packet-ieee802154.c (revision 32563)
+++ packet-ieee802154.c (working copy)
@@ -979,8 +979,8 @@
 field_tree = proto_item_add_subtree(ti, ett_ieee802154_aux_sec_key_id);
 /* Add key source, if it exists. */
 if (packet->key_id_mode == KEY_ID_MODE_KEY_EXPLICIT_4) {
-  packet->key_source.addr32 = (guint64) tvb_get_ntohl(tvb, offset);
-  proto_tree_add_uint64(field_tree, hf_ieee802154_aux_sec_key_source, 
tvb, offset, 4, packet->key_source.addr32);
+  packet->key_source.addr32 = tvb_get_ntohl(tvb, offset);
+  proto_tree_add_uint32(field_tree, hf_ieee802154_aux_sec_key_source, 
tvb, offset, 4, packet->key_source.addr32);
   proto_item_set_len(ti, 1 + 4);
   offset += sizeof (guint32);
 }
@@ -2003,14 +2003,14 @@
 if (adata) block[i] |= (1 << 6); /* Adata */
 i++;
 /* Nonce: Source Address || Frame Counter || Security Level */
-block[i++] = (addr >> 56) & 0xff;
-block[i++] = (addr >> 48) & 0xff;
-block[i++] = (addr >> 40) & 0xff;
-block[i++] = (addr >> 32) & 0xff;
-block[i++] = (addr >> 24) & 0xff;
-block[i++] = (addr >> 16) & 0xff;
-block[i++] = (addr >> 8) & 0xff;
-block[i++] = (addr >> 0) & 0xff;
+block[i++] = (gchar)((addr >> 56) & 0xff);
+block[i++] = (gchar)((addr >> 48) & 0xff);
+block[i++] = (gchar)((addr >> 40) & 0xff);
+block[i++] = (gchar)((addr >> 32) & 0xff);
+block[i++] = (gchar)((addr >> 24) & 0xff);
+block[i++] = (gchar)((addr >> 16) & 0xff);
+block[i++] = (gchar)((addr >> 8) & 0xff);
+block[i++] = (gchar)((addr >> 0) & 0xff);
 block[i++] = (counter >> 24) & 0xff;
 block[i++] = (counter >> 16) & 0xff;
 block[i++] = (counter >> 8) & 0xff;
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread ankur madan 
I have latest version code from the svn and latest development wireshark
version.1.3.4 installed.i am still not able to resolve this issue.any help
or comments are welcome

thanks
ankur

On Mon, Apr 26, 2010 at 12:51 PM, ankur madan  wrote:

> I am compiling on windows XP n 32 bit.
>
>
> On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher 
> wrote:
>
>> On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:
>>
>> > packet-ieee802154.c(982) : warning C4244: '=' : conversion from
>> > 'guint64' to 'gu int32', possible loss of data
>>
>> I see that you're compiling on Windows, but which version and is it
>> 32-bit or 64-bit?
>>
>>
>> --
>> Steve
>>
>> ___
>> Sent via:Wireshark-dev mailing list 
>> Archives:http://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>> mailto:wireshark-dev-requ...@wireshark.org
>> ?subject=unsubscribe
>>
>
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-26 Thread ankur madan 
I am compiling on windows XP n 32 bit.

On Mon, Apr 26, 2010 at 3:37 AM, Stephen Fisher wrote:

> On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:
>
> > packet-ieee802154.c(982) : warning C4244: '=' : conversion from
> > 'guint64' to 'gu int32', possible loss of data
>
> I see that you're compiling on Windows, but which version and is it
> 32-bit or 64-bit?
>
>
> --
> Steve
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-25 Thread Stephen Fisher 
On Fri, Apr 23, 2010 at 02:42:35PM +0530, ankur madan wrote:

> packet-ieee802154.c(982) : warning C4244: '=' : conversion from 
> 'guint64' to 'gu int32', possible loss of data

I see that you're compiling on Windows, but which version and is it 
32-bit or 64-bit?


-- 
Steve
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-23 Thread ankur madan 
Hi,
   i am using the latest version.i checked out the code from,
http://anonsvn.wireshark.org/wireshark/trunk/




On Fri, Apr 23, 2010 at 5:33 PM, Anders Broman
wrote:

>  What version are you trying to build?
>
>  --
>  *From:* wireshark-dev-boun...@wireshark.org [mailto:
> wireshark-dev-boun...@wireshark.org] *On Behalf Of *ankur madan
> *Sent:* den 23 april 2010 12:43
> *To:* Developer support list for Wireshark
> *Subject:* Re: [Wireshark-dev] Problem during compilation
>
>
> Hi,
>  Upto wht time i will get the solution.
>  looking forward for your response.
>
> thanks
> ankur
> On Fri, Apr 23, 2010 at 2:42 PM, ankur madan wrote:
>
>> Hi, i found this error also..
>>
>> packet-ieee802154.c(982) : error C2220: warning treated as error - no
>> 'object' f
>> ile generated
>> packet-ieee802154.c(982) : warning C4244: '=' : conversion from 'guint64'
>> to 'gu
>> int32', possible loss of data
>> packet-ieee802154.c(2006) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>> packet-ieee802154.c(2007) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>> packet-ieee802154.c(2008) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>> packet-ieee802154.c(2009) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>> packet-ieee802154.c(2010) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>> packet-ieee802154.c(2011) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>> packet-ieee802154.c(2012) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>> packet-ieee802154.c(2013) : warning C4244: '=' : conversion from 'guint64'
>> to 'g
>> char', possible loss of data
>>
>> thanks
>> ankur
>>
>>   On Fri, Apr 23, 2010 at 1:46 PM, Anders Broman <
>> anders.bro...@ericsson.com> wrote:
>>
>>>   Hi,
>>> I think you'll find the real error earlier in the printout...
>>> /Anders
>>>
>>>  --
>>> *From:* wireshark-dev-boun...@wireshark.org [mailto:
>>> wireshark-dev-boun...@wireshark.org] *On Behalf Of *ankur madan
>>> *Sent:* den 23 april 2010 10:06
>>> *To:* wireshark-dev@wireshark.org
>>> *Subject:* [Wireshark-dev] Problem during compilation
>>>
>>>   Hi,i am building the code,according to steps mentioned in wireshark
>>> dev guide.i am recieving the following error during the build.
>>> Please let me know the reason for this.
>>> The output show is the following:
>>> packet-ipmi-bridge.c
>>> packet-ipmi-chassis.c
>>> packet-ipmi-picmg.c
>>> packet-ipmi-se.c
>>> packet-ipmi-storage.c
>>> packet-ipmi-transport.c
>>> packet-ipmi-pps.c
>>> packet-ipmi-update.c
>>> packet-dcerpc-nt.c
>>> Generating Code...
>>> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>>> 8\VC\BIN\c
>>> l.EXE"' : return code '0x2'
>>> Stop.
>>> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>>> 8\VC\BIN\n
>>> make.exe"' : return code '0x2'
>>> Stop.
>>> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>>> 8\VC\BIN\n
>>> make.exe"' : return code '0x2'
>>> Stop.
>>>
>>> thanks
>>> ankur
>>>
>>>
>>> ___
>>> Sent via:Wireshark-dev mailing list 
>>> Archives:http://www.wireshark.org/lists/wireshark-dev
>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>>> mailto:wireshark-dev-requ...@wireshark.org
>>> ?subject=unsubscribe
>>>
>>
>>
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-23 Thread Anders Broman 
What version are you trying to build?


From: wireshark-dev-boun...@wireshark.org 
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of ankur madan
Sent: den 23 april 2010 12:43
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Problem during compilation


Hi,
 Upto wht time i will get the solution.
 looking forward for your response.

thanks
ankur
On Fri, Apr 23, 2010 at 2:42 PM, ankur madan 
mailto:ankurmad...@gmail.com>> wrote:
Hi, i found this error also..

packet-ieee802154.c(982) : error C2220: warning treated as error - no 'object' f
ile generated
packet-ieee802154.c(982) : warning C4244: '=' : conversion from 'guint64' to 'gu
int32', possible loss of data
packet-ieee802154.c(2006) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data
packet-ieee802154.c(2007) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data
packet-ieee802154.c(2008) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data
packet-ieee802154.c(2009) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data
packet-ieee802154.c(2010) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data
packet-ieee802154.c(2011) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data
packet-ieee802154.c(2012) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data
packet-ieee802154.c(2013) : warning C4244: '=' : conversion from 'guint64' to 'g
char', possible loss of data

thanks
ankur

On Fri, Apr 23, 2010 at 1:46 PM, Anders Broman 
mailto:anders.bro...@ericsson.com>> wrote:
Hi,
I think you'll find the real error earlier in the printout...
/Anders


From: 
wireshark-dev-boun...@wireshark.org<mailto:wireshark-dev-boun...@wireshark.org> 
[mailto:wireshark-dev-boun...@wireshark.org<mailto:wireshark-dev-boun...@wireshark.org>]
 On Behalf Of ankur madan
Sent: den 23 april 2010 10:06
To: wireshark-dev@wireshark.org<mailto:wireshark-dev@wireshark.org>
Subject: [Wireshark-dev] Problem during compilation

Hi,i am building the code,according to steps mentioned in wireshark dev guide.i 
am recieving the following error during the build.
Please let me know the reason for this.
The output show is the following:
packet-ipmi-bridge.c
packet-ipmi-chassis.c
packet-ipmi-picmg.c
packet-ipmi-se.c
packet-ipmi-storage.c
packet-ipmi-transport.c
packet-ipmi-pps.c
packet-ipmi-update.c
packet-dcerpc-nt.c
Generating Code...
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\c
l.EXE"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\n
make.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\n
make.exe"' : return code '0x2'
Stop.

thanks
ankur

___
Sent via:Wireshark-dev mailing list 
mailto:wireshark-dev@wireshark.org>>
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev

mailto:wireshark-dev-requ...@wireshark.org<mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe


___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-23 Thread ankur madan 
Hi,
 Upto wht time i will get the solution.
 looking forward for your response.

thanks
ankur
On Fri, Apr 23, 2010 at 2:42 PM, ankur madan  wrote:

> Hi, i found this error also..
>
> packet-ieee802154.c(982) : error C2220: warning treated as error - no
> 'object' f
> ile generated
> packet-ieee802154.c(982) : warning C4244: '=' : conversion from 'guint64'
> to 'gu
> int32', possible loss of data
> packet-ieee802154.c(2006) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
> packet-ieee802154.c(2007) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
> packet-ieee802154.c(2008) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
> packet-ieee802154.c(2009) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
> packet-ieee802154.c(2010) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
> packet-ieee802154.c(2011) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
> packet-ieee802154.c(2012) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
> packet-ieee802154.c(2013) : warning C4244: '=' : conversion from 'guint64'
> to 'g
> char', possible loss of data
>
> thanks
> ankur
>
>   On Fri, Apr 23, 2010 at 1:46 PM, Anders Broman <
> anders.bro...@ericsson.com> wrote:
>
>>   Hi,
>> I think you'll find the real error earlier in the printout...
>> /Anders
>>
>>  --
>> *From:* wireshark-dev-boun...@wireshark.org [mailto:
>> wireshark-dev-boun...@wireshark.org] *On Behalf Of *ankur madan
>> *Sent:* den 23 april 2010 10:06
>> *To:* wireshark-dev@wireshark.org
>> *Subject:* [Wireshark-dev] Problem during compilation
>>
>>   Hi,i am building the code,according to steps mentioned in wireshark dev
>> guide.i am recieving the following error during the build.
>> Please let me know the reason for this.
>> The output show is the following:
>> packet-ipmi-bridge.c
>> packet-ipmi-chassis.c
>> packet-ipmi-picmg.c
>> packet-ipmi-se.c
>> packet-ipmi-storage.c
>> packet-ipmi-transport.c
>> packet-ipmi-pps.c
>> packet-ipmi-update.c
>> packet-dcerpc-nt.c
>> Generating Code...
>> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>> 8\VC\BIN\c
>> l.EXE"' : return code '0x2'
>> Stop.
>> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>> 8\VC\BIN\n
>> make.exe"' : return code '0x2'
>> Stop.
>> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>> 8\VC\BIN\n
>> make.exe"' : return code '0x2'
>> Stop.
>>
>> thanks
>> ankur
>>
>>
>> ___
>> Sent via:Wireshark-dev mailing list 
>> Archives:http://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>> mailto:wireshark-dev-requ...@wireshark.org
>> ?subject=unsubscribe
>>
>
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-23 Thread ankur madan 
Hi, i found this error also..

packet-ieee802154.c(982) : error C2220: warning treated as error - no
'object' f
ile generated
packet-ieee802154.c(982) : warning C4244: '=' : conversion from 'guint64' to
'gu
int32', possible loss of data
packet-ieee802154.c(2006) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data
packet-ieee802154.c(2007) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data
packet-ieee802154.c(2008) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data
packet-ieee802154.c(2009) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data
packet-ieee802154.c(2010) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data
packet-ieee802154.c(2011) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data
packet-ieee802154.c(2012) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data
packet-ieee802154.c(2013) : warning C4244: '=' : conversion from 'guint64'
to 'g
char', possible loss of data

thanks
ankur

On Fri, Apr 23, 2010 at 1:46 PM, Anders Broman
wrote:

>  Hi,
> I think you'll find the real error earlier in the printout...
> /Anders
>
>  --
> *From:* wireshark-dev-boun...@wireshark.org [mailto:
> wireshark-dev-boun...@wireshark.org] *On Behalf Of *ankur madan
> *Sent:* den 23 april 2010 10:06
> *To:* wireshark-dev@wireshark.org
> *Subject:* [Wireshark-dev] Problem during compilation
>
>   Hi,i am building the code,according to steps mentioned in wireshark dev
> guide.i am recieving the following error during the build.
> Please let me know the reason for this.
> The output show is the following:
> packet-ipmi-bridge.c
> packet-ipmi-chassis.c
> packet-ipmi-picmg.c
> packet-ipmi-se.c
> packet-ipmi-storage.c
> packet-ipmi-transport.c
> packet-ipmi-pps.c
> packet-ipmi-update.c
> packet-dcerpc-nt.c
> Generating Code...
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\c
> l.EXE"' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\n
> make.exe"' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\n
> make.exe"' : return code '0x2'
> Stop.
>
> thanks
> ankur
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Problem during compilation

2010-04-23 Thread Anders Broman 
Hi,
I think you'll find the real error earlier in the printout...
/Anders


From: wireshark-dev-boun...@wireshark.org 
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of ankur madan
Sent: den 23 april 2010 10:06
To: wireshark-dev@wireshark.org
Subject: [Wireshark-dev] Problem during compilation

Hi,i am building the code,according to steps mentioned in wireshark dev guide.i 
am recieving the following error during the build.
Please let me know the reason for this.
The output show is the following:
packet-ipmi-bridge.c
packet-ipmi-chassis.c
packet-ipmi-picmg.c
packet-ipmi-se.c
packet-ipmi-storage.c
packet-ipmi-transport.c
packet-ipmi-pps.c
packet-ipmi-update.c
packet-dcerpc-nt.c
Generating Code...
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\c
l.EXE"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\n
make.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\n
make.exe"' : return code '0x2'
Stop.

thanks
ankur
___
Sent via:Wireshark-dev mailing list 
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe