Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
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 16:23:14 -0800	[thread overview]
Message-ID: <E5ADEF30-DBC9-4250-ACA4-F889D8CFDA89@gmail.com> (raw)
In-Reply-To: <1424295668.11836.19.camel@linuxfoundation.org>


> On Feb 18, 2015, at 1:41 PM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> On Wed, 2015-02-18 at 10:38 -0800, Khem Raj wrote:
>>> On Feb 18, 2015, at 5:06 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
>>> On Wed, 2015-02-18 at 11:51 +0000, Richard Purdie wrote:
>>>> On Wed, 2015-02-18 at 01:01 -0800, Khem Raj wrote:
>>> The series needs:
>>> 
>>> TUNE_CCARGS_x86 := "${@oe_filter_out('-mfpmath=sse', '${TUNE_CCARGS}', d)}"
>>> +TUNE_CCARGS_x86-64 := "${@oe_filter_out('-mfpmath=sse', '${TUNE_CCARGS}', d)}”
>>> 
>> 
>> hmmm I assumed x86 was common across 32bit and 64bit x86 but seems not so I replaced the old patch instead of appending it 
> 
> Thanks, I'll update the patch for the next round.
> 
>> 
>>> since the x86 override doesn't cover x86_64. I'll queue that and run yet
>>> another build. We do have another poky-tiny issue too:
>>> 
>>> https://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/204
>>> 
>> 
>> OK. I am creating a local config to use tiny config for libc and weed out remaining build issues for tiny config 
> 
> Cool, thanks.
> 
> The next build is in progress and looking greener than the last. Next up
> it appears we still have multilib issues:

I have pushed a new patchset to same branch. That should fix the tiny build issues.

> 
> https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/201


| dcigettext.c: In function '__dcigettext':
| dcigettext.c:856:30: error: '__libc_setlocale_lock' undeclared (first use in this function)
|         __libc_rwlock_unlock (__libc_setlocale_lock);

is what I see.

I have fixed this in the latest patchset. So lets start with the new patchset.


> There is a possibility this "from sstate" build may have run into a
> problem with sstate but something looks to be wrong with glibc in some
> regard.
> 
> Cheers,
> 
> Richard
> 



  reply	other threads:[~2015-02-19  0:23 UTC|newest]

Thread overview: 40+ 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 ` [yocto] " Burton, Ross
2015-02-02 10:53   ` Khem Raj
2015-02-02 10:54   ` Khem Raj
2015-02-02 17:25     ` Burton, Ross
2015-02-02 17:40       ` Khem Raj
2015-02-02 17:50         ` Burton, Ross
2015-02-02 18:33           ` Khem Raj
2015-02-02 21:45             ` Burton, Ross
2015-02-03  5:03               ` Khem Raj
2015-02-03 11:55                 ` Burton, Ross
2015-02-03 14:43                 ` Dan McGregor
2015-02-12  7:35                   ` Khem Raj
2015-02-14  7:53                     ` Burton, Ross
2015-02-14 10:06                     ` Richard Purdie
2015-02-14 13:08                       ` Burton, Ross
2015-02-14 15:15                         ` Dan McGregor
2015-02-15 21:59                       ` Richard Purdie
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                       ` [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-18  7:46                         ` Richard Purdie
2015-02-18  9:01                           ` Khem Raj
2015-02-18 11:51                             ` Richard Purdie
2015-02-18 13:06                               ` Richard Purdie
2015-02-18 18:38                                 ` Khem Raj
2015-02-18 21:41                                   ` Richard Purdie
2015-02-19  0:23                                     ` Khem Raj [this message]
2015-02-19  0:28                                       ` Khem Raj
2015-02-19  0:31                                         ` Khem Raj
2015-02-19  3:36                                           ` Khem Raj
     [not found] ` <54CFA8A5.7090504@mvista.com>
2015-02-02 17:26   ` Burton, Ross
2015-02-02 17:43     ` Khem Raj
2015-02-20 18:03 ` Richard Purdie
2015-02-21  0:27   ` Peter Urbanec
2015-02-24  6:34     ` Khem Raj
2015-02-21  9:22   ` Richard Purdie
2015-02-24  6:59     ` 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=E5ADEF30-DBC9-4250-ACA4-F889D8CFDA89@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox