This is the mail archive of the mailing list for the libstdc++ project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [libstdc++] Un-precious the CC-related variables

On Wed, Aug 13, 2003 at 09:53:41AM -0400, Kaveh R. Ghazi wrote:
> Hmm, the patch went in, right?  I still get an error on irix6.5 as of
> last night:

Patch is in.

> 	creating reloadable object files...
> 	creating a temporary reloadable object file: .libs/

Messages from libtool...

> 	/usr/bin/ld -n32 -64 -r -o .libs/ libE77/.libs/Labort.o
> 	libE77/.libs/Lderf.o [...]
> 	ld64: ERROR   4  : Conflicting flag setting: -32-set-32bit-path
> 	ld64: ERROR   4  : Conflicting flag setting: -64
> 	        -n32 may conflict with -o32
> 	ld64: FATAL   12 : Expecting n32 objects: libE77/.libs/Labort.o is n64.
> 	make[5]: *** [] Error 4
> 	make[5]: Leaving directory
> 	`/caip/u58/ghazi/gcc-testing/build/mips-sgi-irix6.5/mabi=64/libf2c'
> I use CC='cc -n32' for stage1 if that is relevant (I bet it is).

Perhaps 'cc -n32' results in LD being set to '/usr/bin/ld -n32'?  That'd be
my initial not-really-thought-about-it guess.

> I
> have to do that because the system compiler generates o32 by default.

Someday SGI must change that...

> Strangely, it only fails when I do a serial make.  Parallel make -j2
> or higher seems to work. (?)

Absolutely no idea.  That's freaky weird.


Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
    - Brian W. Kernighan

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]