This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.


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

Re: specs File


Terry Lee Tucker wrote:
> 
> Configuring a cross compiler Linux -> SCO5. While building gcc, I get
> the following message:
> _muldi3
> /usr/local/i386-sco5/bin/as: unrecognized option `-b'
> 
> When I look at the specs file generated by the build, I see this in
>   *asm:
>   -b %{!mcoff:elf} %{mcoff:coff %{static:%e-static not valid with
>
> -b is not a valid option for as. Why is it doing this?

 The '-b' is a valid option for 'as' !  But not for GNU as...  GNU as is
not the
default 'as' in SCO world, it is the SCO 'as' which comes with every
SCO5 system.

 Just blame the narrow-mindness of the GCC ports... The SCO5 port
assumes you
always making a native compiler, using SCO as and ld, and so on... (The
SCO5
port isn't the only one... hmmm are there anything else than the
embedded targets
which are cross-compilers as default or have something like '#ifdef
CROSS_COMPILE'
in their target config headers...)

 Be prepared to do your own port for cross-compiling...  My 'specs' for
SCO5 has
the ASM_SPEC as empty and the LINK_SPEC as :

*link:
-m %{!mcoff:elf_i386}%{mcoff:i386coff %{static: %e-static not valid with
-mcoff} %{shared: %e-shared not valid with -mcoff} %{symbolic:
%e-symbolic not valid with -mcoff} %{fpic: %e-fpic not valid with
-mcoff} %{fPIC: %e-fPIC not valid with -mcoff}}
%{p:-L/usr/local/i386-sco3.2v5/lib/libp} %{h*} %{static:-dn -Bstatic}
%{shared:-G -dy %{!z*:-z text}} %{symbolic:-Bsymbolic -G -dy %{!z*:-z
text}} %{z*} %{R*} %{Y*} %{G:-G}

So it gives a '-m elf_i386' without a '-mcoff', and a '-m i386coff' with
a '-mcoff',
in the GCC command line, to the GNU linker. The GNU ld should support
both ELF and
COFF (please check yours with '/usr/local/i386-sco5/bin/ld -V').

Cheers, Kai

PS. If you are going to try Sparc/Solaris7 and x86/Solaris7 as targets
too, they
are 'free' too, for home-use and so on, be prepared to tinker with the
'-rpath-link'
too --- the binaries are using shared libs (.so files) as default, just
as SCO5, and
the dynamic linker must be found...



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


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