From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Saul Wold <saul.wold@intel.com>
Subject: Re: [RFC 0/3] Move Old Recipes to meta-extras
Date: Mon, 16 May 2011 20:51:19 +0100 [thread overview]
Message-ID: <1305575479.3424.102.camel@rex> (raw)
In-Reply-To: <BANLkTi=0TcHgXmYpwCjX6P5h6+y9O2YQFw@mail.gmail.com>
On Mon, 2011-05-16 at 10:08 -0700, Khem Raj wrote:
> On Mon, May 16, 2011 at 7:57 AM, Saul Wold <saul.wold@intel.com> wrote:
> > On 05/15/2011 11:19 PM, Khem Raj wrote:
> >>
> >>
> >> On May 14, 2011, at 5:23 PM, Saul Wold<sgw@linux.intel.com> wrote:
> >>
> >>> From: Saul Wold<sgw@linux.intel.com>
> >>>
> >>> This proposes to move the YAFFS2-utils, older clutter-1.4
> >>> and older GCC version (4.3.3 and 3.4.4) as they are unused
> >>> and currently unbuildable.
> >>>
> >>
> >> Are we left with any GPLv2 version of gcc after this ?
> >>
> > Khem,
> >
> > Is not having a GPLv2 version of gcc an issue? For the non-gplv3 version, my
> > understanding is to have an installed user-space for oe-core for a
> > non-development system, therefore gcc is not an issue.
> >
>
> there are certain parts of gcc which go onto target e.g. libgcc libstdc++
These have specific license exceptions allowing non-gpl code to use them
as system libraries though?
Cheers,
Richard
next prev parent reply other threads:[~2011-05-16 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 0:23 [RFC 0/3] Move Old Recipes to meta-extras Saul Wold
2011-05-15 0:23 ` [RFC 2/3] clutter: Clean up old recipes Saul Wold
2011-05-15 0:23 ` [RFC 1/3] yaffs2: Remove yaffs2 from oe-core Saul Wold
2011-05-15 0:23 ` [RFC 3/3] gcc: Move 4.3.3 and Special kernel gcc-3.4.4 to meta-extras Saul Wold
2011-05-16 6:19 ` [RFC 0/3] Move Old Recipes " Khem Raj
2011-05-16 14:57 ` Saul Wold
2011-05-16 17:08 ` Khem Raj
2011-05-16 19:51 ` Richard Purdie [this message]
2011-05-16 20:48 ` Saul Wold
2011-05-16 22:34 ` Khem Raj
2011-05-17 17:23 ` Richard Purdie
2011-05-18 1:19 ` Khem Raj
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=1305575479.3424.102.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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