This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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

Re: Multi-architecture installation


David:

David Korn wrote:
> 
> >> ../src/configure --prefix=/usr/local
> >--includedir=/usr/local/gcc-2.95.2/include
> >--libdir=/usr/local/gcc-2.95.2/lib --with-gnu-as --with-gnu-ld
> >--target=mips4el-elf --with-newlib --enable-languages=c

>   That's sound; it's basically a variation on the way cross compilers
> keep from conflicting with the native compiler.  Replace /gcc-2.95.2/
> with /$target/, IYSWIM.


I was under the impression that the files in these directories were
shared among all targets w/ the same gcc version. There's only a few
files... (8 file names) They all appear to be from binutils....

Whups. libopcodes.a is clearly target specific.
??? I thought that binutils and gcc appended the target name to any
file that was target specific. Isn't this a naming conflict that would
trip up a large number of people?

> >By the way, I still haven't found an authoritative list of all the
> >options that can be supplied to configure when building gcc. If
> >someone knows where I can find that info, I'd appreciate hearing about
> >it.
> 
>   I'm afraid configure.in is about all the documentation there is...


Thanks...
Hey, there's no mention of libdir in there.
A grep for libdir in Makefile.in and config-ml.in succeeds. Much to
learn...

-Bill

------
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]