From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Pull request buildroot.git (vapier branch)
Date: Mon, 6 Dec 2010 20:27:54 +0100 [thread overview]
Message-ID: <20101206202754.57658344@surf> (raw)
In-Reply-To: <201012060156.53523.vapier@gentoo.org>
On Mon, 6 Dec 2010 01:56:52 -0500
Mike Frysinger <vapier@gentoo.org> wrote:
> On Sunday, December 05, 2010 07:19:52 Thomas Petazzoni wrote:
> > Yet another question regarding non-MMU support and support for
> > static builds in Buildroot. Obviously, not all packages support
> > non-MMU architectures and/or static build, so it'd be good to not
> > allow the users to select those packages. So the packages known to
> > work for non-MMU and/or static build should be clearly identified.
>
> you can do shared libs under nommu systems. binding the two makes no
> sense.
I know you can do shared libs with no-MMU systems, I've already used
FDPIC on Blackfin, thanks.
I didn't mean those two things to be bound together. But it's well
known that :
* Some packages do not support static build
* Some packages do not support no-MMU
Those two sets of packages are not identical, that's why I proposed two
different options. A package that doesn't support static build should
do:
depends on !BR2_PREFER_STATIC_LIB
and all packages that do not work on !MMU should do
depends on BR2_USE_MMU
My intention is that users can't mistakenly select packages that do not
build statically and/or do not work on !MMU systems.
Is this more clear ?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101206/fd256e41/attachment.pgp>
next prev parent reply other threads:[~2010-12-06 19:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 22:52 [Buildroot] Pull request buildroot.git (vapier branch) Mike Frysinger
2010-12-05 10:57 ` Thomas Petazzoni
2010-12-05 12:19 ` Thomas Petazzoni
2010-12-06 6:56 ` Mike Frysinger
2010-12-06 19:27 ` Thomas Petazzoni [this message]
2010-12-06 20:10 ` Mike Frysinger
2010-12-07 12:28 ` Peter Korsgaard
2010-12-07 20:35 ` Thomas Petazzoni
2010-12-07 21:31 ` Mike Frysinger
2010-12-07 21:48 ` Peter Korsgaard
2010-12-07 22:02 ` Mike Frysinger
2010-12-06 7:50 ` Mike Frysinger
2010-12-06 19:39 ` Thomas Petazzoni
2010-12-06 20:20 ` Mike Frysinger
2010-12-06 20:44 ` Thomas Petazzoni
2010-12-06 20:55 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2011-02-07 5:49 Mike Frysinger
2011-01-20 3:10 Mike Frysinger
2011-01-10 14:28 Mike Frysinger
2010-11-23 21:48 Mike Frysinger
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=20101206202754.57658344@surf \
--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