From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: A few random things on my to fix list
Date: Tue, 28 Jun 2011 15:58:45 +0100 [thread overview]
Message-ID: <1309273125.20015.319.camel@rex> (raw)
Hi,
I've been merging patches but there are a few things I've noticed which
could use some attention. I've kept a quick list of these:
* Need to have eglibc-dev not
include /usr/include/eglibc-locale-internal-i586-poky-linux/*
* Need to use something like gnomebase.bbclass for glib-networking
* Is the new gcc config, I'd prefer not to hardcode SYSTEMLIBS_DIR for
lib, lib32 and lib64 in GLIBC_DYNAMIC_LINKER* but code them
separately and allow for future manoeuvring in the multilib code
* Consider having the locale generation done by a Makefile and use
PARALLE_MAKE to enable parallelism.
* Consider stripping binaries/libraries in the sysroot (less diskspace
usage, smaller sstate package and faster linking if there is less
file to read?)
* Take a long hard look at the way distrodata is using overrides as it
looks suboptimal
* Move things out of local.conf.sample to local.conf.extended
Cheers,
Richard
reply other threads:[~2011-06-28 15:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1309273125.20015.319.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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