All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-arm][PATCH 1/3] linux-libc-headers: Use Yocto's default to avoid same arch rebuilds
Date: Tue, 19 Feb 2013 15:03:57 +0100	[thread overview]
Message-ID: <20130219150357.76a0788e@e6520eb> (raw)
In-Reply-To: <1361282381.5927.41.camel@ted>

Le Tue, 19 Feb 2013 05:59:41 -0800,
Richard Purdie <richard.purdie@linuxfoundation.org> a écrit :

> On Tue, 2013-02-19 at 14:44 +0100, Eric Bénard wrote:
> > Hi Otavio,
> > 
> > Le Tue, 19 Feb 2013 09:37:25 -0300,
> > Otavio Salvador <otavio@ossystems.com.br> a écrit :
> > 
> > > This avoids full rebuild in case of compatible machine changes (e.g
> > > i.MX53 and i.MX6) and fixes the build failures seen in autobuilder.
> > > 
> > aren't Frescale's headers needed for some GPU/VPU libraries ?
> 
> The GPU/VPU libraries should be looking at the kernel headers, not the
> libc headers.
> 
yes, I just looked at the recipe efter sending the mail and remembered
the difference ;-)

> If you put the kernel headers in as libc headers, it means the whole
> stack is machine specific and will entirely rebuild with each machine
> switch. The libc headers are meant to be machine independent.
> 
> I suspect the situation after these patches still isn't perfect (see my
> other reply) however it is *much* improved and I much appreciate this
> being fixed. We've seen build repeated failures on the autobuilder for
> what seems like months due to this problem.

very good.

Eric


  reply	other threads:[~2013-02-19 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 12:37 [meta-fsl-arm][PATCH 0/3] Stop using Freescale as linux-libc-headers Otavio Salvador
2013-02-19 12:37 ` [meta-fsl-arm][PATCH 1/3] linux-libc-headers: Use Yocto's default to avoid same arch rebuilds Otavio Salvador
2013-02-19 13:44   ` Eric Bénard
2013-02-19 13:59     ` Richard Purdie
2013-02-19 14:03       ` Eric Bénard [this message]
2013-02-19 14:02     ` Eric Bénard
2013-02-19 12:37 ` [meta-fsl-arm][PATCH 2/3] qt4: Use kernel staging include files Otavio Salvador
2013-02-19 12:37 ` [meta-fsl-arm][PATCH 3/3] mesa: Rename to follow OE-Core upgrade Otavio Salvador
2013-02-19 13:56 ` [meta-fsl-arm][PATCH 0/3] Stop using Freescale as linux-libc-headers Richard Purdie
2013-02-19 14:04   ` Otavio Salvador
2013-02-19 19:37 ` 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=20130219150357.76a0788e@e6520eb \
    --to=eric@eukrea.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.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.