Thanks Gerald Guy,
Since http://buildbot.wireshark.org/trunk/waterfall shows green yellow
on wireshark win32 I've been downloading the latest svn compiled wireshark
win32 once or twice a day for a few days now and they all seem really stable
so far and even seems to be stable on my Windows
Hi Brian,
As stated here
(http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html),
you need to install cygwin and python to be able to compile Wireshark
on your box. If you follow the guide, it will work flawlessly :)
Regards,
Pascal.
2009/3/17 Brian Daniel
Brian Daniel wrote:
Thanks Gerald Guy,
Since http://buildbot.wireshark.org/trunk/waterfall shows green
yellow on wireshark win32 I've been downloading the latest svn
compiled wireshark win32 once or twice a day for a few days now and
they all seem really stable so far and even seems to
OK, this is the part I was getting confused on...
Don't use Cygwin's gcc!
yet it tells me to
2.2.2. Install Cygwin
Download http://www.cygwin.com/setup.exe the cygwin installer and start
it.
Trying it...
On Tue, Mar 17, 2009 at 9:06 AM, Brian Daniel daniel_br...@colstate.eduwrote:
Thanks
Brian Daniel wrote:
OK, this is the part I was getting confused on...
Don't use Cygwin's gcc!
yet it tells me to
2.2.2. Install Cygwin
Download http://www.cygwin.com/setup.exe the cygwin installer and
start it.
Trying it...
Because although Cygwin is required to manage other
On Mar 17, 2009, at 9:25 AM, Brian Daniel wrote:
CPU=IA64
So you have an Itanium machine on which you'll be running Wireshark?
I don't think we have any Itanium builds of any of the libraries, just
x86-64 builds.
___
CPU=i386 failed also CPU=AMD64
Systems available to me:
Intel E6550, 4Gig RAM, XP Pro 32-bit (wireshark win32 worked)
Intel Q6600, 4Gig RAM, Windows Vista 64-bit Home Prem
Intel T7500, 3Gig RAM, XP Pro 32-bit + Windows 7 beta 64-bit
offline 6 pending for Windows-XP-Win64
Brian Daniel wrote:
CPU=i386 failed also CPU=AMD64
Systems available to me:
Intel E6550, 4Gig RAM, XP Pro 32-bit (wireshark win32 worked)
Intel Q6600, 4Gig RAM, Windows Vista 64-bit Home Prem
Intel T7500, 3Gig RAM, XP Pro 32-bit + Windows 7 beta 64-bit
offline 6 pending for
You should now, along with updating SVN. I just checked in a change to use
WIRESHARK_TARGET_PLATFORM (note the fixed spelling) instead of PLATFORM.
Config.nmake sets CPU according to WIRESHARK_TARGET_PLATFORM. You shouldn't have
to set it yourself.
Brian Daniel wrote:
Yep, turns out I need to
Cool thanks folks! Since http://buildbot.wireshark.org/trunk/waterfall shows
failed on both wireshark win32 and win64, I'll hold off on my svn update
until later tonight when both are green.
On Wed, Mar 11, 2009 at 12:18 PM, Gerald Combs ger...@wireshark.org wrote:
You should now, along with
Thanks Gerald! Where is the list of CPU abbreviation codes? such as AMD64?
I didn't think it would care about the CPU since I've currently left it
selected CPU=win32.
I'm currently on a Core2 Duo CPU E6550 running XP Pro SP3
Once this works on win32 (known to usually work), I'll also try this on
On Mar 10, 2009, at 2:34 PM, Brian Daniel wrote:
config.nmake(63) : fatal error U1050: Your mysterious moon-man
architecture BPC frightens and confuses us.
Make sure that nothing sets PLATFORM to BPC:
Guy Harris wrote:
On Mar 10, 2009, at 2:34 PM, Brian Daniel wrote:
config.nmake(63) : fatal error U1050: Your mysterious moon-man
architecture BPC frightens and confuses us.
Make sure that nothing sets PLATFORM to BPC:
On Mar 10, 2009, at 5:08 PM, Gerald Combs wrote:
Should we use something more Wireshark-specific, e.g.
WIRESHRK_TARGET_PLATFORM
instead?
That might work better. When Googling for information about this I
found at least a couple of instances of some annoying bit of software
insisting
I just checked in a change which adds preliminary support for 64-bit (x86-64)
compilation on Windows. You can enable 64-bit compilation by setting
PLATFORM=win64. Due to the version of Lua in wireshark-win64-libs repository
you'll probably have to use Visual C++ 2008.
A lot of changes were made
15 matches
Mail list logo
