From: Denys Dmytriyenko <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: eglibc_2.17.bb: Failure expanding variable SELECTED_OPTIMIZATION[:=]
Date: Mon, 09 Sep 2013 12:22:07 -0400 [thread overview]
Message-ID: <20130909162207.GF5834@denix.org> (raw)
In-Reply-To: <1378740263.3484.122.camel@ted>
On Mon, Sep 09, 2013 at 04:24:23PM +0100, Richard Purdie wrote:
> On Mon, 2013-09-09 at 09:51 -0400, Denys Dmytriyenko wrote:
> > Any ideas or suggestions at this point would be greatly appreciated! Thanks.
Richard,
> 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.
Ah, good call! Massaging the patch onto 1.18 seems to have solved the parsing
breakage - it passed 10 out of 10 tries so far. I'll keep testing and run a
few real builds, but would you be willing to backport it to 1.18? Please let
me know if you need an updated patch re-submitted. Thanks.
> Have you got two definitions of the "get_optimization" function?
I grepped through all my layers and eglibc_2.17.inc is the only place where it
gets defined and used.
--
Denys
prev parent reply other threads:[~2013-09-09 16:22 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
2013-09-09 16:22 ` Denys Dmytriyenko [this message]
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=20130909162207.GF5834@denix.org \
--to=denis@denix.org \
--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.