From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 03/10] liburcu: Update to 0.8.4
Date: Fri, 27 Jun 2014 12:39:05 +0200 [thread overview]
Message-ID: <lyd2dur60m.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1403863939.28648.5.camel@ted> (Richard Purdie's message of "Fri, 27 Jun 2014 11:12:19 +0100")
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
>> This new package seems to blacklist[1] gcc-4.8.0 till gcc-4.8.2 which is
>> used by OE.
>
> OE-Core is using gcc 4.9 by default now?
yes; but 4.8.2 is still in the tree.
> That said do we know which fix is needed for gcc 4.8.x?
The urcu commit which blacklists gcc 4.8 refers to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854
The patch mentioned in this report is applied to our gcc 4.8.2
meta/recipes-devtools/gcc/gcc-4.8/0048-PR58854_fix_arm_apcs_epilogue.patch
Enrico
next prev parent reply other threads:[~2014-06-27 10:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 0:13 [PATCH 00/10] Updates and a bug fix Saul Wold
2014-06-25 0:13 ` [PATCH 01/10] sqlite3: Update to 3.8.5.0 Saul Wold
2014-06-25 0:13 ` [PATCH 02/10] libusb1: Update to 1.0.19 Saul Wold
2014-06-25 0:13 ` [PATCH 03/10] liburcu: Update to 0.8.4 Saul Wold
2014-06-27 9:56 ` Enrico Scholz
2014-06-27 10:12 ` Richard Purdie
2014-06-27 10:39 ` Enrico Scholz [this message]
2014-06-25 0:13 ` [PATCH 04/10] gnupg: Update to 2.0.23 Saul Wold
2014-06-25 0:13 ` [PATCH 05/10] curl: Update to 7.37 Saul Wold
2014-06-25 0:13 ` [PATCH 06/10] xcb-util-renderutil: Update to version 0.3.9 Saul Wold
2014-06-25 0:13 ` [PATCH 07/10] man-pages: Update to 3.69 Saul Wold
2014-06-25 0:13 ` [PATCH 08/10] mobile-broadband-provider-info: Update SRCREV Saul Wold
2014-06-25 0:13 ` [PATCH 09/10] ca-certificates: Update to 20140325 Saul Wold
2014-06-25 0:13 ` [PATCH 10/10] curl: Convert CURLGNUTL to PACKAGECONFIG Saul Wold
2014-09-25 19:27 ` Martin Jansa
2014-09-25 22:44 ` Burton, Ross
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=lyd2dur60m.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.