From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/8] package/autotools: add --{enable, disable}-{shared, static} automatically
Date: Wed, 15 Jun 2011 09:09:52 +0200 [thread overview]
Message-ID: <87r56v8ta7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110615084756.5d787906@skate> (Thomas Petazzoni's message of "Wed, 15 Jun 2011 08:47:56 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
Thomas> Ok. Thanks a lot for doing this testing!
>>
>> Another more serious issue is that some non-library packages like bmon
>> interprete --enable-static as link the binary statically, leading to
>> bloat (E.G. ~900KB instead of ~100KB).
Thomas> Is --enable-static supposed to have this semantic ? If not, then we
Thomas> should fix the package. If yes, then we can fix those packages manually
Thomas> by adding --disable-static to <pkg>_CONF_OPT, no ?
I haven't been able to find an official specification of the
--enable-static semantic, but so far I've only noticed bmon having this
issue, so it might be local - It does kind of make sense though.
Thomas> Or maybe this isn't worth the trouble after all, and we could just use
Thomas> --disable-static by default. I'm not personally using static linking,
Thomas> so adding the production of .a files was just done because it appeared
Thomas> to be cost-free and could have been useful to some users. So I wouldn't
Thomas> complain if we decide to revert back to --disable-static for target
Thomas> packages.
Ok. I'll test a bit more and see if I find other packages misbehaving as
well. If I don't then I'l just add the workaround for bmon.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-06-15 7:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 21:56 [Buildroot] [pull request] Pull request for branch for-2011.08/no-mmu-blackfin Thomas Petazzoni
2011-05-30 21:56 ` [Buildroot] [PATCH 1/8] blackfin: support external toolchains provided by blackfin.uclibc.org Thomas Petazzoni
2011-05-30 21:56 ` [Buildroot] [PATCH 2/8] toolchain: introduce BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS Thomas Petazzoni
2011-05-30 21:56 ` [Buildroot] [PATCH 3/8] busybox: tune config according to BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS Thomas Petazzoni
2011-05-30 21:56 ` [Buildroot] [PATCH 4/8] busybox: adjust configuration for non-MMU targets Thomas Petazzoni
2011-05-30 21:57 ` [Buildroot] [PATCH 5/8] Mark some packages as not usable on non-MMU systems Thomas Petazzoni
2011-06-12 19:55 ` Peter Korsgaard
2011-06-12 22:14 ` Thomas Petazzoni
2011-05-30 21:57 ` [Buildroot] [PATCH 6/8] Remove unused variable definitions Thomas Petazzoni
2011-05-30 21:57 ` [Buildroot] [PATCH 7/8] package/autotools: add --{enable, disable}-{shared, static} automatically Thomas Petazzoni
2011-06-12 19:59 ` Peter Korsgaard
2011-06-12 22:16 ` Thomas Petazzoni
2011-06-13 21:39 ` Peter Korsgaard
2011-06-14 6:54 ` Thomas Petazzoni
2011-06-15 6:37 ` Peter Korsgaard
2011-06-15 6:47 ` Thomas Petazzoni
2011-06-15 7:09 ` Peter Korsgaard [this message]
2011-06-15 7:28 ` ANDY KENNEDY
2011-06-15 7:33 ` Peter Korsgaard
2011-05-30 21:57 ` [Buildroot] [PATCH 8/8] packages: remove --{enable, disable}-{shared, static} from autotools packages Thomas Petazzoni
2011-06-12 21:06 ` [Buildroot] [pull request] Pull request for branch for-2011.08/no-mmu-blackfin 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=87r56v8ta7.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.