From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 3/3] gcc-4.6: Backport PR46934 fix
Date: Tue, 18 Oct 2011 09:47:21 -0700 [thread overview]
Message-ID: <4E9DAD99.9080508@intel.com> (raw)
In-Reply-To: <7B75FA82-846A-4B85-872E-0B611C41C11D@dominion.thruhere.net>
On 10/18/2011 07:18 AM, Koen Kooi wrote:
>
> Op 18 okt. 2011, om 03:39 heeft Khem Raj het volgende geschreven:
>
>> We have been hitting this issue on ARM/thumb and
>> have a workaround in place to compile samba
>> http://git.openembedded.org/openembedded/commit/recipes/samba/samba_3.2.15.bb?id=4ba7aa07c0dcd28f94515ff9927e2a04403fcf15
>> This backport should fix the gcc bug
>
> Can I have a rough ETA when this is going into master? There are meta-oe patches depending on this. No rush, this is just to order my patch queue more intelligently :)
>
Koen,
We are working on it, I am doing builds with these changes to day and
will submit a consolidated pull for tonight and if all goes well RP will
pull tomorrow.
Sau!
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-10-18 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 1:38 [PATCH 0/3] gcc update and bug fix Khem Raj
2011-10-18 1:39 ` [PATCH 1/3] bluez4: Add glib-2.0 to DEPENDS Khem Raj
2011-10-18 1:39 ` [PATCH 2/3] gcc-4.6: Upgrade SRCREV to latest FSF 4.6 branch Khem Raj
2011-10-18 1:39 ` [PATCH 3/3] gcc-4.6: Backport PR46934 fix Khem Raj
2011-10-18 7:54 ` Martin Jansa
2011-10-18 14:18 ` Koen Kooi
2011-10-18 16:47 ` Saul Wold [this message]
2011-10-18 16:54 ` Koen Kooi
2011-10-20 17:19 ` [PATCH 0/3] gcc update and bug fix Saul Wold
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=4E9DAD99.9080508@intel.com \
--to=saul.wold@intel.com \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox