This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-1.1b on sco-3.2v5.0.4 gcc/pic/libgcc.a with mixed COFF and ELF files?
- To: Joao Cardoso <jcardoso at inescn dot pt>, egcs at cygnus dot com
- Subject: Re: egcs-1.1b on sco-3.2v5.0.4 gcc/pic/libgcc.a with mixed COFF and ELF files?
- From: Robert Lipe <robertl at dgii dot com>
- Date: Wed, 9 Sep 1998 10:01:34 -0500
- References: <35F56F98.AF9C87DC@inescn.pt>
> I think that the following is incorrect.
It may be incorrect. I'm unsure of the rules of this game.
> The system is sco-3.2v5.0.4, egcs-1.1b, and "/etc/default/cc" (the
> default
> cc options) is empty, generating COFF by default.
>
>
> bash-2.02# pwd
> /src/egcs-1.1b-objdir/gcc/pic
> bash-2.02# ar x libgcc.a
> bash-2.02# file *.o| fgrep iAPX
[ Things from libgcc1.a are COFF. ]
The Makefiles go to a considerable amount of effort to be sure that
libgcc1 components are _not_ built by the compiler being built. In the
OpenServer case with native cc, t his means libgcc1 is COFF. This sure
looks intentional to me.
The OSR5 linker does DTRT when mixing simple COFF and ELF functions like
this.
Is this actually causing you a problem, or is this just an observed oddity?
RJL