Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] ia32-base.inc: new include file
Date: Sat, 25 Aug 2012 12:53:21 +0100	[thread overview]
Message-ID: <1345895601.14369.103.camel@ted> (raw)
In-Reply-To: <CAMKF1srk3toCstU+aL66uohw4CPmCZm6szB4f2qswkUsJjTr9g@mail.gmail.com>

On Sat, 2012-08-25 at 01:13 -0700, Khem Raj wrote:
> 
> 
> On Saturday, August 25, 2012, Koen Kooi <koen@dominion.thruhere.net>
> 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
> 
> And its redundant

I thought you tried removing this and we ran into issues?

Regardless, I think this is reason to have this in one place where we
can clean it up. I tried to untangle the GLIBC_EXTRA_CONF bit that was
here until recently and that was more painful than necessary needing
patches to meta-intel and meta-yocto. If we get one good include file,
we then have one place to clean this kind of thing up and it stops BSP
layers having to do their own things badly.

So in summary I think this is a reason to support this change :)

Cheers,

Richard







  reply	other threads:[~2012-08-25 12:05 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 [this message]
2012-08-25 20:20         ` Khem Raj
2012-08-25 11:56     ` Richard Purdie
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=1345895601.14369.103.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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