From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yi Qingliang <niqingliang2003@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: why recompile gcc-cross/eglibc when update linux package?
Date: Wed, 05 Dec 2012 09:29:18 +0000 [thread overview]
Message-ID: <1354699758.25268.86.camel@ted> (raw)
In-Reply-To: <1370507.95j740KEpU@yiqingliang-pc>
On Wed, 2012-12-05 at 10:16 +0000, Yi Qingliang wrote:
> I update the kernel from 3.6.6 to 3.6.9, and recompile it: bitbake linux
>
> but it will recompile eglibc/gcc-cross first, so long time:( why?
> the eglibc will use kernel header? if so, understand.
> but what about gcc-cross?
Did you change linux-libc-headers or the kernel itself?
If you change the libc-headers, gcc-cross will rebuild since it depends
on eglibc and as you mention, eglibc depends on the headers.
Changing the target kernel recipe shouldn't rebuild any of those.
Cheers,
Richard
next prev parent reply other threads:[~2012-12-05 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 10:16 why recompile gcc-cross/eglibc when update linux package? Yi Qingliang
2012-12-05 9:29 ` Richard Purdie [this message]
2012-12-05 17:37 ` Yi Qingliang
2012-12-05 9:46 ` Marcin Juszkiewicz
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=1354699758.25268.86.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=niqingliang2003@gmail.com \
--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