Multilib Support

Khem Raj raj.khem@gmail.com
Mon Jul 13 23:30:00 GMT 2009


On Mon, Jul 13, 2009 at 2:11 PM, Yann E.
MORIN<yann.morin.1998@anciens.enib.fr> wrote:
> David,
> All,
>
> (original message missing on the mailing list, so entirely quoted below
> for reference).
>
> On Monday 13 July 2009 18:58:08 David DeBonis wrote:
>> I am currently adding multilib support to crosstool-ng through a patch
>> specific to the Xilinx Microblaze soft processor with MMU support.  The
>> patch works to a point.  I can dumpspecs on the object files that are
>> created and see some custom configs (i.e. xl-barrel-shift).  I create
>> glibc variants into subdirectories of the lib directory and can see all
>> of the variant .so's in the targets/XXX/build/build-libc directory and
>> sub-directories.
>
> How do you go to generate all the variants?
>
> Normally, gcc builds a multilib compiler by default. crosstool-NG disables
> multilib support in scripts/build/cc/gcc.sh, at line 170 and 277.
>
> Then, the glibc's ./configure checks for multilib support in the compiler
> ad builds all relevant combinations, and they should get installed when
> you run "make install".

thats not the way it happens. multilib support in gcc generates appropriate
startup files and runtime library variants for supported multilibs

For glibc you have to build it each time for a given variant with correct
compiler options.


Thx

-Khem

--
For unsubscribe information see http://sourceware.org/lists.html#faq



More information about the crossgcc mailing list