[Buildroot] BR2_PREFER_STATIC_LIB and external toolchain

[Buildroot] BR2_PREFER_STATIC_LIB and external toolchain

[ANDY KENNEDY]

When I select both PREFER_STATIC and external toolchain, I get .so's 
copied to the RFS from the external toolchain.  Would it cause anyone
any heartburn if I we make the install to target dependant on
PREFER_STATIC?  I'll do up the patches, I just want to know if that
would upset anyone before I send out the patch ;).

Andy

[Buildroot] BR2_PREFER_STATIC_LIB and external toolchain

[Peter Korsgaard]

>>>>> "ANDY" == ANDY KENNEDY <ANDY.KENNEDY@adtran.com> writes:

 ANDY> When I select both PREFER_STATIC and external toolchain, I get .so's 
 ANDY> copied to the RFS from the external toolchain.  Would it cause anyone
 ANDY> any heartburn if I we make the install to target dependant on
 ANDY> PREFER_STATIC?  I'll do up the patches, I just want to know if that
 ANDY> would upset anyone before I send out the patch ;).

Yes, I noticed as well today. Unfortunately it isn't as simple as making
copy_toolchain_lib_root a noop with static linking, as E.G. glibc afaik
still needs libnss*.so* in the target rootfs when static linking is
used.

-- 
Bye, Peter Korsgaard

[Buildroot] BR2_PREFER_STATIC_LIB and external toolchain

[ANDY KENNEDY]

 
> Yes, I noticed as well today. Unfortunately it isn't as simple as
> making
> copy_toolchain_lib_root a noop with static linking, as E.G. glibc
> afaik
> still needs libnss*.so* in the target rootfs when static linking is
> used.

Really?  What are the libnss*-pic.a for then?

Also, another bone of contention is that I'm getting header files
in the target.  Where does that happen?

Andy

[Buildroot] BR2_PREFER_STATIC_LIB and external toolchain

[Peter Korsgaard]

>>>>> "ANDY" == ANDY KENNEDY <ANDY.KENNEDY@adtran.com> writes:

 >> Yes, I noticed as well today. Unfortunately it isn't as simple as
 >> making
 >> copy_toolchain_lib_root a noop with static linking, as E.G. glibc
 >> afaik
 >> still needs libnss*.so* in the target rootfs when static linking is
 >> used.

 ANDY> Really?  What are the libnss*-pic.a for then?

I don't normally use glibc toolchains for embedded, but I believe you
only have those if you built glibc with --enable-static-nss. By default
glibc will dlopen libnss instead (to handle dynamic name resolution).

 ANDY> Also, another bone of contention is that I'm getting header files
 ANDY> in the target.  Where does that happen?

Those should get removed at the end through the target-finalize step in
the toplevel Makefile unless you have BR2_HAVE_DEVFILES enabled.

-- 
Bye, Peter Korsgaard