Re: Multi-architecture installation

[William Burns <bburns at aeroflex dot com>]

Hello All:

I was just looking through this archive and stumbled across your
messages. Please forgive the lack of timeliness of my reply and feel
free to correct any inaccuracies you find.

I've been working on building a cross gcc w/ a MIPS64el-elf target.
I've been having some problems which I think are worked out now, but I
figured I'd pass the info along just in case it helps you.

Aeroflex has been attempting to locate a cross gcc in the /usr/local
directory. We are also using the newlib library.

On my system I am using a host gcc from the egcs-1.1.2-24 package.
This seems to conflict w/ our attempts to install gcc-2.95.2 into
/usr/local.

First off, when installing binutils, we found it necessary to clear
out the contents of /usr/local/bin, /usr/local/include and
/usr/local/lib in between build attempts. The older gcc looks in some
of those directories before looking in the equivalent /usr
directories.

In effect, installing the required newlib include files in
/usr/local/include crippled the host side gcc. Using the host gcc now
requires a "-I /usr/include" in order for that directory to take
effect before /usr/local/include.

Possibly installing gcc-2.95.2 as your host gcc before attempting to
build the cross compilers will resolve these issues.

One of our people discovered a "unified source tree" build method that
is working better for us than our previous attempts to build each
tarball separately. If you want to check it out, try this URL:
ftp://ftp.aeroflex.com/pub/ecard/aero-xgcc-1.1.0-3.spec
ftp://ftp.aeroflex.com/pub/ecard/

We're still trying to figure out how to keep the cross compiler
install from putting any files in /usr/local/include or
/usr/local/lib. Until we get that worked out I'm still worried about
conflicts w/ older host side gcc's.

-Bill


     To: David Korn <dkorn at pixelpower dot com>, "'Joel Sherrill'"
<joel dot sherrill at
     OARcorp dot com> 
     Subject: Re: Multi-architecture installation 
     From: "Pierre Saucourt-Harmel (r54698)" <pierre dot
saucourt-harmel at motorola
     dot com> 
     Date: Thu, 29 Mar 2001 09:26:55 +0200 
     CC: crossgcc at sourceware dot cygnus dot com 
     Organization: Motorola 
     References:
    
<718D38CAB6E0D011B2C90060970C28A56427D7@exchangeserver.pixelpower.com>



David Korn wrote:

> >I know this works well with the RTEMS cross toolsets.  We distribute
> >RPMs for crosses to about 10 architectures.  They all install into the
> >same --prefix and there are no conflicts.
> >
> >One warning would be to avoid giving options like --program-prefix
> >which change the names of the installed tools.  The default install
> >names are clear enough.

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