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 Windows-XP-Win64 > http://buildbot.wireshark.org/trunk/waterfall > I'll give up on compiling wireshark 64-bit for a couple of days.
Setting CPU won't have any effect since config.nmake clobbers it based on the value of WIRESHARK_TARGET_PLATFORM: # # Machine type for the compiler and linker # TARGET_MACHINE (Used for link /MACHINE) should be one of "X86" or "X64" # (sorry ARM, Alpha, MIPS, and Itanium fans). # CPU (Used by win32.mak) should be one of "i386" or "AMD64". !if "$(WIRESHARK_TARGET_PLATFORM)" == "win32" TARGET_MACHINE=X86 CPU=i386 !else if "$(WIRESHARK_TARGET_PLATFORM)" == "win64" TARGET_MACHINE=X64 CPU=AMD64 !else !error Your mysterious moon-man architecture "$(WIRESHARK_TARGET_PLATFORM)" frightens and confuses us. !endif The whole point of having WIRESHARK_TARGET_PLATFORM is so that variables like CPU, TARGET_MACHINE, and other options will be set to their correct values automatically. -- Join us for Sharkfest’09 | Stanford University, June 15 – 18 http://www.cacetech.com/sharkfest.09/ ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <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?subject=unsubscribe
