From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] ia32-base.inc: new include file
Date: Sat, 25 Aug 2012 12:56:36 +0100 [thread overview]
Message-ID: <1345895796.14369.106.camel@ted> (raw)
In-Reply-To: <3BDCB1BC-7393-4B42-BE04-3BE9A8C90123@dominion.thruhere.net>
On Sat, 2012-08-25 at 09:45 +0200, Koen Kooi wrote:
> Op 25 aug. 2012, om 06:34 heeft tom.zanussi@intel.com het volgende geschreven:
>
> > From: Tom Zanussi <tom.zanussi@intel.com>
> >
> > This is the ia32-base.inc moved over from meta-intel. See meta-intel
> > for the complete history of contributions to this file.
> >
> > Here's the initial commit text that explains the purpose of this file:
> >
> > The meta-intel BSPs currently have a number of machine settings common
> > to all - factor these out into a common include file.
> >
> > Also add several new intel-specific XSERVER variables for building
> > XSERVER variables in BSPs.
> >
> > Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> > ---
> > meta/conf/machine/include/ia32-base.inc | 58 +++++++++++++++++++++++++++++++++
> >
> > +# glibc-related variables
> > +#
> > +GLIBC_ADDONS ?= "nptl"
>
> That's a distro setting
Yes and no. It makes sense for architectures to have sane defaults and I
class nptl on ia32 as that. We want OE-Core to function distroless but
allow distros to change things where it makes sense to them. So I'd
argue this is reasonable.
I seem to remember a number of issues where ia32 defaulted to something
less sane going back in time and you needed this on every ia32 machine.
As has been pointed out, this is probably redundant now. If that is the
case, great, lets clean it up. As I mention to Khem, having one place to
cleanup is better than a whole load of different places.
So I see more in favour of merging this and working on improvements than
not merging it as things stand.
Cheers,
Richard
next prev parent reply other threads:[~2012-08-25 12:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 4:32 [PATCH 0/1] add ia32-base.inc tom.zanussi
2012-08-25 4:34 ` [PATCH 1/1] ia32-base.inc: new include file tom.zanussi
2012-08-25 7:35 ` Richard Purdie
2012-08-25 7:45 ` Koen Kooi
2012-08-25 8:13 ` Khem Raj
2012-08-25 11:53 ` Richard Purdie
2012-08-25 20:20 ` Khem Raj
2012-08-25 11:56 ` Richard Purdie [this message]
2012-08-25 14:17 ` Koen Kooi
2012-08-25 15:51 ` Richard Purdie
2012-08-25 7:59 ` Phil Blundell
2012-08-25 11:50 ` Richard Purdie
2012-08-29 22:21 ` [PATCH 0/1] add ia32-base.inc Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2011-11-18 16:59 tom.zanussi
2011-11-18 16:59 ` [PATCH 1/1] ia32-base.inc: new include file tom.zanussi
2011-11-18 19:17 ` Khem Raj
2011-11-18 20:19 ` Tom Zanussi
2011-11-19 14:52 ` Otavio Salvador
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=1345895796.14369.106.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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