All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] musl: Honor BR2_STATIC_LIBS / BR2_SHARED_LIBS
Date: Sun, 18 Oct 2015 21:06:16 +0200	[thread overview]
Message-ID: <8737x89etz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20151018183347.06045571@free-electrons.com> (Thomas Petazzoni's message of "Sun, 18 Oct 2015 18:33:47 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Charles, Yann,
 > On Sun, 18 Oct 2015 16:18:10 +0000, Charles Duffy wrote:
 >> I provided this patch because my build results were unnecessarily enlarged
 >> by dynamic libraries on an otherwise static-only system.
 >> 
 >> It sounds to me like we could optionally disable only dynamic libraries;
 >> leave static libraries always enabled; and end up in a place that works for
 >> everyone.

 > Yeah, that's also my thought. In uClibc, you can enable/disable the
 > shared library build, but not the static library build. So maybe we
 > should do:

 > 	--enable-static \
 > 	$(if $(BR2_STATIC_LIBS),--disable-shared,--enable-shared)

 > I.e, always static, and shared as soon as BR2_STATIC_LIBS is disabled.

Yes, I think that's the safest/easiest/best-matching-the-other-libcs
approach.

-- 
Venlig hilsen,
Peter Korsgaard 

      parent reply	other threads:[~2015-10-18 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  4:29 [Buildroot] [PATCH 1/1] musl: Honor BR2_STATIC_LIBS / BR2_SHARED_LIBS Charles Duffy
2015-10-14 21:35 ` Thomas Petazzoni
2015-10-14 22:23   ` Charles Duffy
2015-10-15  7:38     ` Thomas Petazzoni
2015-10-18 13:09 ` Thomas Petazzoni
2015-10-18 15:58   ` Yann E. MORIN
2015-10-18 16:18     ` Charles Duffy
2015-10-18 16:33       ` Thomas Petazzoni
2015-10-18 18:52         ` Yann E. MORIN
2015-10-18 19:06         ` 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=8737x89etz.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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.