From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Kang Kai <Kai.Kang@windriver.com>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Question about apply eglibc configurability to create minimal image
Date: Thu, 9 Jun 2011 17:34:28 +0200 [thread overview]
Message-ID: <BANLkTimV_znbLegSD-E3EEeFqEasmDHa4Q@mail.gmail.com> (raw)
In-Reply-To: <4DF0E4A8.1000608@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
2011/6/9 Mark Hatle <mark.hatle@windriver.com>
> On 6/9/11 5:57 AM, Kang Kai wrote:
> > Hi Mark,
> >
> > I am focus on eglibc itself compilation with disabling all the
> > configurable options, right now eglibc can be compiled with disable all
> > the configurable options.
> >
> > But when I build core-image-minimal in a clear new directory, some
> > packages build failed and they need eglibc supports, such as
>
> core-image-minimal is simply to large of an image to see some of the
> advantages
> of the eglibc configuration. Realistically the advantages come on single
> application or small (busybox + single application) systems.
>
Then again if you are in that usecase you're probably better off (spacewise)
using static linking
Frans
[-- Attachment #2: Type: text/html, Size: 1084 bytes --]
next prev parent reply other threads:[~2011-06-09 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DF0A70C.7080501@windriver.com>
2011-06-09 10:59 ` [poky] Question about apply eglibc configurability to create minimal image Koen Kooi
2011-06-09 15:20 ` Mark Hatle
2011-06-09 15:34 ` Frans Meulenbroeks [this message]
2011-06-09 15:38 ` Mark Hatle
2011-06-10 2:50 ` Kang Kai
2011-06-17 10:05 ` Kang Kai
2011-06-17 15:46 ` Mark Hatle
2011-06-17 16:10 ` Koen Kooi
2011-06-21 7:35 ` Kang Kai
2011-06-27 2:09 ` Kang Kai
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=BANLkTimV_znbLegSD-E3EEeFqEasmDHa4Q@mail.gmail.com \
--to=fransmeulenbroeks@gmail.com \
--cc=Kai.Kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox