This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

Re: can't build gcc-2.95.2 on SCO OSR 5.0.5


log sharp wrote:

> At http://gcc.gnu.org/install/specific.html#ix86-*-sco3.2v5* , I find this 
> message:"Unlike earlier versions of GCC, the ability to generate COFF with 
> this target is no longer provided." So I used --disable-multilib to 
> configure gcc and have built it successfully. Thank you!

And for the top of tree, that's true.  For 2.95.2, it is not.  2.95.2
does support COFF generation.

> But when I compiled my software with gcc, I found that it can't deal with 
> template class well.It noted me like:
> ......
> TypeCode.o: fatal error: symbol `ObjVar<CORBA_TypeCode>::inout(void)` 
> multiply
> -defined, also in file Any.o
> collect2: ld returned 1 exit status

This was an, err, negative interaction between GCC and the System V
linkers that Jason fixed in the top-of-tree a year or so ago.  I think
the patch was in the 2.95.3 backport set, but I'm not following 2.95.3.
It's definitely in the 2.95.2.pl1 (that's the patch that makes it "patch
level 1") binary kit available on Skunkware.

> My software can be compiled successfully on linux with gcc-2.95.2. I think 
> there is something wrong when I built gcc on SCO. What I did are:
> 
> $ ../gcc-2.95.2/configure --prefix=/usr/gcc-2952 --enable-shared 
> --disable-multilib
> $ make bootstrap
> $ make install
> 
> What's your advice about this?

Aaaah, it's the "--enable-shared" that caused you grief.  This was
definitely naughty unless you specified --disable-multilib.


RJL


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