From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 0/1] [1.2] poky-tiny: Separate the libc features required for meta-toolchain
Date: Mon, 16 Apr 2012 18:06:04 -0700 [thread overview]
Message-ID: <cover.1334624662.git.dvhart@linux.intel.com> (raw)
This addresses [YOCTO #2295], in which the meta-toolchain target would fail for
the poky-tiny DISTRO definition due to its reduced libc feature set. This is not
an optimal solution as it significantly increases the size of the C libraries
(by 461KB). However, by making the features easily removed, those looking for
truly tiny libc configurations can easily revert to the smaller set. Out of the
box, we want poky-tiny to be able to build meta-toolchain.
In the future, we need to address WHY meta-toolchain cannot be built without
these features and look at how to reduce the impact of meta-toolchain on the
target eglibc build.
The following changes since commit c936fca6e163bc19bc08cbd0036b31ca6f6c3ed6:
bitbake.conf: Add PARALLEL_MAKE to BB_HASHBASE_WHITELIST (2012-04-16 23:37:45 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib dvhart/tiny
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/tiny
Darren Hart (1):
poky-tiny: Separate the libc features required for meta-toolchain
meta-yocto/conf/distro/poky-tiny.conf | 18 ++++++++++++------
1 files changed, 12 insertions(+), 6 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-04-17 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 1:06 Darren Hart [this message]
2012-04-17 1:06 ` [PATCH 1/1] poky-tiny: Separate the libc features required for meta-toolchain Darren Hart
2012-04-17 8:09 ` [PATCH 0/1] [1.2] " Richard Purdie
2012-04-17 14:04 ` Darren Hart
2012-04-18 12:13 ` Richard Purdie
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=cover.1334624662.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=yocto@yoctoproject.org \
/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.