From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto <yocto@yoctoproject.org>,
openembeded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core@lists.openemebedded.org
Subject: Re: [yocto] [RFT] gcc 5.0 recipes available for testing
Date: Fri, 20 Feb 2015 06:04:18 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1502200603100.28632@localhost> (raw)
In-Reply-To: <BB19F3C7-2950-4E41-BF62-70BFE4FB9C9B@gmail.com>
On Fri, 20 Feb 2015, Khem Raj wrote:
> Hi All
>
> Encouraged by help received on testing out glibc 2.21, now I have put together OE recipes for gcc-5
>
> GCC 5.0 is in prerelease stage 4 ( open for regression and doc fixes only)
>
> https://gcc.gnu.org/ml/gcc/2015-01/msg00156.html
>
> The recipes are available here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-5.0
>
> you just need the topmost commit and then set
>
> GCCVERSION = "5.0"
> SDKGCCVERSION = "5.0"
>
> in local.conf
i assume this new layer should be used *in place* of the current OE
layer for testing purposes?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
WARNING: multiple messages have this Message-ID (diff)
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto <yocto@yoctoproject.org>,
openembeded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core@lists.openemebedded.org
Subject: Re: [RFT] gcc 5.0 recipes available for testing
Date: Fri, 20 Feb 2015 06:04:18 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1502200603100.28632@localhost> (raw)
In-Reply-To: <BB19F3C7-2950-4E41-BF62-70BFE4FB9C9B@gmail.com>
On Fri, 20 Feb 2015, Khem Raj wrote:
> Hi All
>
> Encouraged by help received on testing out glibc 2.21, now I have put together OE recipes for gcc-5
>
> GCC 5.0 is in prerelease stage 4 ( open for regression and doc fixes only)
>
> https://gcc.gnu.org/ml/gcc/2015-01/msg00156.html
>
> The recipes are available here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-5.0
>
> you just need the topmost commit and then set
>
> GCCVERSION = "5.0"
> SDKGCCVERSION = "5.0"
>
> in local.conf
i assume this new layer should be used *in place* of the current OE
layer for testing purposes?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-02-20 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 10:55 [RFT] gcc 5.0 recipes available for testing Khem Raj
2015-02-20 11:04 ` Robert P. J. Day [this message]
2015-02-20 11:04 ` Robert P. J. Day
2015-02-20 11:10 ` [yocto] " Khem Raj
2015-02-20 11:10 ` Khem Raj
2015-02-20 11:14 ` [yocto] " Robert P. J. Day
2015-02-20 11:14 ` Robert P. J. Day
2015-02-20 14:36 ` Dan McGregor
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=alpine.LFD.2.11.1502200603100.28632@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openemebedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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.