This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: can't build gcc-2.95.2 on SCO OSR 5.0.5
- To: log sharp <sharplog at hotmail dot com>
- Subject: Re: can't build gcc-2.95.2 on SCO OSR 5.0.5
- From: Robert Lipe <robertlipe at usa dot net>
- Date: Thu, 22 Feb 2001 22:23:34 -0600
- Cc: gcc at gcc dot gnu dot org
- References: <F102R881Np7vXee4fDG0000164f@hotmail.com>
log sharp wrote:
> RJL, thank you for your reply. I have rebuilt gcc following what you said,
> but it raise the same message:
>
> /usr/gcc-install/gcc-build/gcc/xgcc
> -B/usr/gcc-install/gcc-build/gcc/
> -B/usr/gcc-2952/i386-pc-sco3.2v5.0.5/bin/ -c -DHAVE_CONFIG_H -g -mcoff -I.
> -I..
> /../../../gcc-2.95.2/libiberty/../include -fpic
> ../../../../gcc-2.95.2/libibert
> y/argv.c -o pic/argv.o
> xgcc: -fpic is not valid with -mcoff
>
> How can I get off the flag '-moff'? I think that flag is unuseful.
-mcoff isn't unuseful to everyone. By default, 2.95.2 for OpenServer
will allow both generation ELF and COFF. But -mcoff and -fpic don't go
together. By default, 2.95.2 does not build libiberty with -mcoff and
-fpic, so there's something going on in your local configuration.
Please provide your precise configure and bootstrap lines.
If you just absolutely don't want coff support, I think that 2.95 will
allow you to pass --disable-multilib and that should whack the COFF
stuff completely. But it's not a heavily tested flag...