[Ns-bugs] [Bug 838] ns-3 can't compile on MacOS with 32bit processor
code@nsnam.ece.gatech.edu
code at nsnam.ece.gatech.edu
Tue Mar 16 10:23:16 PDT 2010
http://www.nsnam.org/bugzilla/show_bug.cgi?id=838
--- Comment #3 from Tommaso Pecorella <tommaso.pecorella at unifi.it> 2010-03-16 13:23:14 EDT ---
I did some more tests, and I'm clueless tbh. It seems that waf is kinda
overriding my architecture. Anyway.
Machine A: Intel Core 2 Duo (32bit)
Machine B: Quad-Core Intel Xeon (64bit)
Both are running the very same OS (10.6.2) and same development tools (gcc
4.2.1).
On both the command "arch" gives the same answer: "i386", as the Xeon is
running a 32-bit kernel.
Starting the "dumb's test", as is: "nm -go -arch i386 whatever.o" / "nm -go
-arch x86_64 whatever.o" will tell me what architecture the .o has been
compiled for.
Machine B: all the .o tested are x86_64, no matter what the "arch" command
said. Weird, but it works. It's a 64bit cpu anyway.
Machine A: all the .o tested are x86_64 BUT ONE.
cairo_wideint_1.o (it's the only one) is arch 386. Hence the error and the
linker upset.
Beat me in the head if I can understand what's going on. It's like if
cairo_wideint had its own private compiler options, but it doesn't.
I'm clueless, but the bug is confirmed here.
By the way, ns-3.7 is just compiling fine. The bug is in the actual dev. At
this point I'm wondering if it's affecting also 386-32 bit linux architectures
as well.
--
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Ns-bugs
mailing list