More problems with building crosscomp. Solaris->powerpc
(vxworks)
Brian Ford (ford@vss.fsi.com)
Tue, 3 Nov 1998 09:54:44 -0600
On Mon, 2 Nov 1998, Alexander V. Voinov wrote:
> Dear Colleages,
>
> I'm trying to build egcs-1.1b as a crosscompiler from sun-solaris-2.5.1
> to powerpc-wrs-vxworks.
>
> I have overcome the problem wiht 'as -ppc'
> setting appropriate link by hand: ../gcc/as-new --->
> .../usr/bin/powerpc-wrs-elf32
> to previously built binutils configured for powerpc-*-elf32 because they
> don't know about vxvworks.
>
> The next problem arises: It infinitely loops at rebuilding libgcc2.a. I
> have
> hacked it by hand, just to go on, and then it fell in something similar
> later. I was too tired to record what happened...
>
This is not really infinite, it just seems that way. It is building using
multi-lib so that it has libraries for every possible combination. ie.
big-little endian, etc. Try configuring with --disable-multilib
> Also when I sometimes forgot to mention LANGUAGES="c c++ f77",
> it made the following diagnostics for objc:
> vxTypesOld.h conflicts with objc/hash.h
> (some symbol already defined).
>
Use "make cross" and "make install-cross" as they are the recommended
methods for egcs. They will, however, only build LANGUAGES="c c++". If
you need f77 try hacking the top level Makefile.in.
> What is the true procedure if any to accomplished the task stated?
>
> Thank you in advance
>
> Alexander
>
> ________________________________________________
> To get help for the crossgcc list, send mail to
> crossgcc-request@cygnus.com with the text 'help'
> (without the quotes) in the body of the message.
>
I'm not an expert on this stuff, but I have successfully build a
sparc-sun-solaris2.6->powerpc-unknown-eabi tool chain.
--
Brian Ford
Software Engineer
Vital Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
________________________________________________
To get help for the crossgcc list, send mail to
crossgcc-request@cygnus.com with the text 'help'
(without the quotes) in the body of the message.