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 22:16:36 +0200	[thread overview]
Message-ID: <87r55e15gb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6047C5D@ex-mb1.corp.adtran.com> (ANDY KENNEDY's message of "Mon, 25 Jul 2011 20:07:45 +0000")

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

  reply	other threads:[~2011-07-25 20:16 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 [this message]
2011-07-25 21:12   ` ANDY KENNEDY
2011-07-25 21:26     ` Peter Korsgaard

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=87r55e15gb.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.