From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] make: requires dynamic libraries
Date: Sun, 20 Sep 2015 18:58:21 +0200 [thread overview]
Message-ID: <20150920185821.53cb363b@free-electrons.com> (raw)
In-Reply-To: <CALq67GCCHMGowurww4w=W7wpAzCDUJHnFLhMDnDo1_33SGNnbQ@mail.gmail.com>
Hello,
On Sun, 20 Sep 2015 09:40:25 -0500, Ryan Barnett wrote:
> I am going to go disabling guile support in a static only
> configuration. I ran into an issue with setting GC_NO_DLOPEN define in
> that there then becomes multiple definitions of locale_charset between
> libintl and libguile and I wasn't sure how to properly fix it. Looking
> at what guile is used for in make, it doesn't appear extremely useful
> especially in a static only configuration.
I think we should disable guile support completely, not only for static
only builds. I don't really see the usefulness of guile support in
make in the context of Buildroot.
Generally speaking, I think we should --disable-<foo> or
--without-<foo> explicitly for as many options as possible, unless they
are explicitly handled in Buildroot.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-20 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 0:38 [Buildroot] [PATCH] make: requires dynamic libraries Ryan Barnett
2015-09-17 21:27 ` Thomas Petazzoni
2015-09-20 14:40 ` Ryan Barnett
2015-09-20 16:58 ` Thomas Petazzoni [this message]
2015-09-20 17:04 ` Thomas Petazzoni
2015-09-20 17:16 ` Baruch Siach
2015-09-20 17:21 ` Ryan Barnett
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=20150920185821.53cb363b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox