From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: eglibc_2.17.bb: Failure expanding variable SELECTED_OPTIMIZATION[:=]
Date: Mon, 09 Sep 2013 16:24:23 +0100 [thread overview]
Message-ID: <1378740263.3484.122.camel@ted> (raw)
In-Reply-To: <20130909135125.GD5834@denix.org>
On Mon, 2013-09-09 at 09:51 -0400, Denys Dmytriyenko wrote:
> Any ideas or suggestions at this point would be greatly appreciated! Thanks.
I have vague recollections about this from something happening in
master. Perhaps try with:
http://git.openembedded.org/bitbake/commit/?id=4d50690489ee8dc329a9b0c7bc4ceb29b71e95e9
applied. This might things more deterministic, perhaps always breaking
or perhaps never.
Have you got two definitions of the "get_optimization" function?
Cheers,
Richard
next prev parent reply other threads:[~2013-09-09 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 18:57 eglibc_2.17.bb: Failure expanding variable SELECTED_OPTIMIZATION[:=] Denys Dmytriyenko
2013-09-09 13:51 ` Denys Dmytriyenko
2013-09-09 15:24 ` Richard Purdie [this message]
2013-09-09 16:22 ` Denys Dmytriyenko
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=1378740263.3484.122.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=denis@denix.org \
--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