All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_PREFER_STATIC_LIB and external toolchain
Date: Mon, 25 Jul 2011 23:26:48 +0200	[thread overview]
Message-ID: <87aac2127b.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6047CB6@ex-mb1.corp.adtran.com> (ANDY KENNEDY's message of "Mon, 25 Jul 2011 21:12:35 +0000")

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

      reply	other threads:[~2011-07-25 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 20:07 [Buildroot] BR2_PREFER_STATIC_LIB and external toolchain ANDY KENNEDY
2011-07-25 20:16 ` Peter Korsgaard
2011-07-25 21:12   ` ANDY KENNEDY
2011-07-25 21:26     ` Peter Korsgaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87aac2127b.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.