From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gcc Recipes
Date: Wed, 31 Mar 2010 13:10:24 +0100 [thread overview]
Message-ID: <1270037424.14554.47.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <y2oac9c93b11003310445gb3deec55va9bd2664d0336584@mail.gmail.com>
On Wed, 2010-03-31 at 13:45 +0200, Frans Meulenbroeks wrote:
> But still I wonder what is e.g. the use of recipes like 4.1.1 (which
> btw was released in may 2006).
Binary compatibility with existing distributions which use that version
of gcc. This is particularly important for kernel modules where the
exact compiler version needs to match, and it is also something of an
issue for folks using C++.
p.
next prev parent reply other threads:[~2010-03-31 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 11:28 gcc Recipes Richard Purdie
2010-03-31 11:45 ` Frans Meulenbroeks
2010-03-31 12:10 ` Phil Blundell [this message]
2010-03-31 13:00 ` Richard Purdie
2010-03-31 16:12 ` Mark Richards
2010-03-31 17:25 ` Khem Raj
2010-03-31 20:20 ` Richard Purdie
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=1270037424.14554.47.camel@mill.internal.reciva.com \
--to=philb@gnu.org \
--cc=openembedded-devel@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