From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Dan McGregor <danismostlikely@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Wed, 18 Feb 2015 11:51:49 +0000 [thread overview]
Message-ID: <1424260309.25541.23.camel@linuxfoundation.org> (raw)
In-Reply-To: <BCB8524E-91CB-41F6-83C0-7B90E60BC82D@gmail.com>
On Wed, 2015-02-18 at 01:01 -0800, Khem Raj wrote:
> OK thats why I am not seeing it on my qemux86 build.
>
> this leaves us with only one problem - glibc/qemuarm issue
>
> http://errors.yoctoproject.org/Errors/Details/8679/
>
> I have seen this error with eglibc-2.19 and glibc 2.20 as well on x86 and arm as well in cases when using
> toolchain from sstate and rebuilding glibc with that. I assume this could be unrelated to glibc upgrade
> and may be a latent problem. Could be missing dependency on a native tool or some such. I have been attributing it to gold
> but that just might have been a red herring.
>
> I will see if I can get to reproduce it.
I tried another build with the three patches from your oe-core contrib
branch applied. Error report out is:
http://errors.yoctoproject.org/Errors/Search/?items=10&query=b75fed99f2aa86b49844dd0cf06991767f6f26d3
i.e. we're still seeing SSE errors in glibc builds. Am I missing some
patches or something?
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Wed, 18 Feb 2015 11:51:49 +0000 [thread overview]
Message-ID: <1424260309.25541.23.camel@linuxfoundation.org> (raw)
In-Reply-To: <BCB8524E-91CB-41F6-83C0-7B90E60BC82D@gmail.com>
On Wed, 2015-02-18 at 01:01 -0800, Khem Raj wrote:
> OK thats why I am not seeing it on my qemux86 build.
>
> this leaves us with only one problem - glibc/qemuarm issue
>
> http://errors.yoctoproject.org/Errors/Details/8679/
>
> I have seen this error with eglibc-2.19 and glibc 2.20 as well on x86 and arm as well in cases when using
> toolchain from sstate and rebuilding glibc with that. I assume this could be unrelated to glibc upgrade
> and may be a latent problem. Could be missing dependency on a native tool or some such. I have been attributing it to gold
> but that just might have been a red herring.
>
> I will see if I can get to reproduce it.
I tried another build with the three patches from your oe-core contrib
branch applied. Error report out is:
http://errors.yoctoproject.org/Errors/Search/?items=10&query=b75fed99f2aa86b49844dd0cf06991767f6f26d3
i.e. we're still seeing SSE errors in glibc builds. Am I missing some
patches or something?
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Wed, 18 Feb 2015 11:51:49 +0000 [thread overview]
Message-ID: <1424260309.25541.23.camel@linuxfoundation.org> (raw)
In-Reply-To: <BCB8524E-91CB-41F6-83C0-7B90E60BC82D@gmail.com>
On Wed, 2015-02-18 at 01:01 -0800, Khem Raj wrote:
> OK thats why I am not seeing it on my qemux86 build.
>
> this leaves us with only one problem - glibc/qemuarm issue
>
> http://errors.yoctoproject.org/Errors/Details/8679/
>
> I have seen this error with eglibc-2.19 and glibc 2.20 as well on x86 and arm as well in cases when using
> toolchain from sstate and rebuilding glibc with that. I assume this could be unrelated to glibc upgrade
> and may be a latent problem. Could be missing dependency on a native tool or some such. I have been attributing it to gold
> but that just might have been a red herring.
>
> I will see if I can get to reproduce it.
I tried another build with the three patches from your oe-core contrib
branch applied. Error report out is:
http://errors.yoctoproject.org/Errors/Search/?items=10&query=b75fed99f2aa86b49844dd0cf06991767f6f26d3
i.e. we're still seeing SSE errors in glibc builds. Am I missing some
patches or something?
Cheers,
Richard
next prev parent reply other threads:[~2015-02-18 11:52 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 10:02 [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-02 10:40 ` Burton, Ross
2015-02-02 10:40 ` [yocto] " Burton, Ross
2015-02-02 10:40 ` Burton, Ross
2015-02-02 10:53 ` Khem Raj
2015-02-02 10:53 ` [yocto] " Khem Raj
2015-02-02 10:54 ` Khem Raj
2015-02-02 10:54 ` [yocto] " Khem Raj
2015-02-02 17:25 ` Burton, Ross
2015-02-02 17:25 ` [yocto] " Burton, Ross
2015-02-02 17:25 ` Burton, Ross
2015-02-02 17:40 ` Khem Raj
2015-02-02 17:40 ` [yocto] " Khem Raj
2015-02-02 17:40 ` Khem Raj
2015-02-02 17:50 ` Burton, Ross
2015-02-02 17:50 ` [yocto] " Burton, Ross
2015-02-02 17:50 ` Burton, Ross
2015-02-02 18:33 ` Khem Raj
2015-02-02 18:33 ` [yocto] " Khem Raj
2015-02-02 18:33 ` Khem Raj
2015-02-02 21:45 ` Burton, Ross
2015-02-02 21:45 ` [yocto] " Burton, Ross
2015-02-02 21:45 ` Burton, Ross
2015-02-03 5:03 ` Khem Raj
2015-02-03 5:03 ` [yocto] " Khem Raj
2015-02-03 11:55 ` Burton, Ross
2015-02-03 11:55 ` [yocto] " Burton, Ross
2015-02-03 11:55 ` Burton, Ross
2015-02-03 14:43 ` Dan McGregor
2015-02-03 14:43 ` [OE-core] " Dan McGregor
2015-02-12 7:35 ` [OE-core] " Khem Raj
2015-02-12 7:35 ` [OE-core] [yocto] " Khem Raj
2015-02-12 7:35 ` Khem Raj
2015-02-14 7:53 ` [OE-core] " Burton, Ross
2015-02-14 7:53 ` [OE-core] [yocto] " Burton, Ross
2015-02-14 7:53 ` Burton, Ross
2015-02-14 10:06 ` [OE-core] " Richard Purdie
2015-02-14 10:06 ` [OE-core] [yocto] " Richard Purdie
2015-02-14 10:06 ` Richard Purdie
2015-02-14 13:08 ` [OE-core] " Burton, Ross
2015-02-14 13:08 ` [OE-core] [yocto] " Burton, Ross
2015-02-14 13:08 ` Burton, Ross
2015-02-14 15:15 ` Dan McGregor
2015-02-14 15:15 ` [OE-core] " Dan McGregor
2015-02-15 21:59 ` [OE-core] " Richard Purdie
2015-02-15 21:59 ` [OE-core] [yocto] " Richard Purdie
2015-02-15 21:59 ` Richard Purdie
2015-02-17 17:50 ` [OE-core] " Martin Jansa
2015-02-17 17:50 ` [OE-core] [yocto] " Martin Jansa
2015-02-17 17:50 ` Martin Jansa
2015-02-17 19:02 ` [PATCH 1/2] valgrind: add glibc-2.21 to glibc.patch Martin Jansa
2015-02-17 19:02 ` [PATCH 2/2] license.bbclass: fix unexpected operator for LICENSE values with space Martin Jansa
2015-02-18 7:15 ` [OE-core] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-18 7:15 ` [OE-core] [yocto] " Khem Raj
2015-02-18 7:15 ` Khem Raj
2015-02-18 7:46 ` [OE-core] " Richard Purdie
2015-02-18 7:46 ` [OE-core] [yocto] " Richard Purdie
2015-02-18 7:46 ` Richard Purdie
2015-02-18 9:01 ` [OE-core] " Khem Raj
2015-02-18 9:01 ` [OE-core] [yocto] " Khem Raj
2015-02-18 9:01 ` Khem Raj
2015-02-18 11:51 ` Richard Purdie [this message]
2015-02-18 11:51 ` [OE-core] " Richard Purdie
2015-02-18 11:51 ` Richard Purdie
2015-02-18 13:06 ` [OE-core] " Richard Purdie
2015-02-18 13:06 ` [yocto] " Richard Purdie
2015-02-18 13:06 ` [yocto] " Richard Purdie
2015-02-18 18:38 ` [OE-core] " Khem Raj
2015-02-18 18:38 ` [yocto] " Khem Raj
2015-02-18 18:38 ` [yocto] " Khem Raj
2015-02-18 21:41 ` [OE-core] " Richard Purdie
2015-02-18 21:41 ` [yocto] " Richard Purdie
2015-02-18 21:41 ` [yocto] " Richard Purdie
2015-02-19 0:23 ` [OE-core] " Khem Raj
2015-02-19 0:23 ` [yocto] " Khem Raj
2015-02-19 0:23 ` [yocto] " Khem Raj
2015-02-19 0:28 ` [OE-core] " Khem Raj
2015-02-19 0:28 ` [yocto] " Khem Raj
2015-02-19 0:28 ` [yocto] " Khem Raj
2015-02-19 0:31 ` [OE-core] " Khem Raj
2015-02-19 0:31 ` [yocto] " Khem Raj
2015-02-19 0:31 ` [yocto] " Khem Raj
2015-02-19 3:36 ` [OE-core] " Khem Raj
2015-02-19 3:36 ` [yocto] " Khem Raj
2015-02-19 3:36 ` [yocto] " Khem Raj
2015-02-02 16:41 ` akuster
2015-02-02 17:26 ` Burton, Ross
2015-02-02 17:26 ` [yocto] " Burton, Ross
2015-02-02 17:26 ` Burton, Ross
2015-02-02 17:43 ` Khem Raj
2015-02-02 17:43 ` [yocto] " Khem Raj
2015-02-02 17:43 ` Khem Raj
2015-02-20 18:03 ` Richard Purdie
2015-02-20 18:03 ` [yocto] " Richard Purdie
2015-02-21 0:27 ` [OE-core] " Peter Urbanec
2015-02-21 0:27 ` [OE-core] [yocto] " Peter Urbanec
2015-02-21 0:27 ` Peter Urbanec
2015-02-24 6:34 ` [OE-core] " Khem Raj
2015-02-24 6:34 ` [OE-core] [yocto] " Khem Raj
2015-02-24 6:34 ` Khem Raj
2015-02-21 9:22 ` [OE-core] " Richard Purdie
2015-02-21 9:22 ` [OE-core] [yocto] " Richard Purdie
2015-02-21 9:22 ` Richard Purdie
2015-02-24 6:59 ` [OE-core] " Khem Raj
2015-02-24 6:59 ` [OE-core] [yocto] " Khem Raj
2015-02-24 6:59 ` Khem Raj
2015-02-24 21:58 ` [OE-core] " Khem Raj
2015-02-24 21:58 ` [OE-core] [yocto] " Khem Raj
2015-02-24 21:58 ` 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=1424260309.25541.23.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=danismostlikely@gmail.com \
--cc=openembedded-core@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.