What is multilib support?

[Mike Frysinger]

On Thursday 22 September 2005 08:19 pm, Khem Raj wrote:
> Joseph M Dupre (AVAB Inc.) wrote:
> >On 22 Sep 2005 at 18:11, Mike Frysinger wrote:
> >>support for multiple library formats with one toolchain
> >>
> >>for example, the typical amd64 toolchain supports both the 32bit (x86)
> >>and 64bit (x86_64) formats ... or you could have a mips toolchain
> >>which supports o32, n32, and n64 -mike
> >
> >So if my intent is to use the uClibc library exclusively on a given
> >platform, there is no need for multilib support in the toolchain,
> >correct?

correct

> Depends if you want same toolchain to generate code for other ABI (e.g.
> MIPS) or not.

well since uClibc only supports o32 on mips atm, mips isnt a good example :)

> >I just saw in the .config file for buildroot that some features are
> >only tested with multilib enabled.  I guess I won't worry about it
> >until I run into problems.
> >
> >I am assuming that including multilib support is likely to increase
> >the size of the executables.  So I'd rather not use it.
>
> No it will not inrease size of executable. It just builds additional
> libraries. Which are exclusive sets
> and only one will get linked depending upon what option you are chosing.
>
> However there will be additional shared libraries on the target if that
> counts then yes the size will increase.

yep
-mike