From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: why recompile gcc-cross/eglibc when update linux package?
Date: Wed, 05 Dec 2012 10:46:39 +0100 [thread overview]
Message-ID: <50BF17FF.30507@linaro.org> (raw)
In-Reply-To: <1824060.mVimSNr8td@yiqingliang-pc>
W dniu 05.12.2012 18:37, Yi Qingliang pisze:
> I think the version of linux-libc-headers should be same as kernel, in other
> words, use same source code, so I have updated both of them.
They do not have to. We used 2.6 linux-libc-headers with 2.4 kernels in
past.
prev parent reply other threads:[~2012-12-05 10:01 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
2012-12-05 17:37 ` Yi Qingliang
2012-12-05 9:46 ` Marcin Juszkiewicz [this message]
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=50BF17FF.30507@linaro.org \
--to=marcin.juszkiewicz@linaro.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 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.