From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] flex: disabled packaged staging of native builds
Date: Tue, 17 Aug 2010 10:25:59 -0700 [thread overview]
Message-ID: <4C6AC627.9050801@mentor.com> (raw)
In-Reply-To: <AANLkTi=YwSNSqe8eSykO_ajEc6dsMBdXFdzBA+to-fEV@mail.gmail.com>
Frans Meulenbroeks wrote:
> 2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
>> On Mon, Aug 16, 2010 at 7:43 PM, Tom Rini <tom_rini@mentor.com> wrote:
>>> Jason Kridner wrote:
>>>> ---
>>>> recipes/flex/flex.inc | 4 +++-
>>>> 1 files changed, 3 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/recipes/flex/flex.inc b/recipes/flex/flex.inc
>>>> index 49b26e8..5d3f076 100644
>>>> --- a/recipes/flex/flex.inc
>>>> +++ b/recipes/flex/flex.inc
>>>> @@ -4,7 +4,7 @@ LICENSE = "BSD"
>>>> DEPENDS = "gettext"
>>>> -INC_PR = "r5"
>>>> +INC_PR = "r6"
>>>> S = "${WORKDIR}/flex-${PV}"
>>>> @@ -16,3 +16,5 @@ inherit autotools gettext
>>>> # static-only library; that might be an error
>>>> FILES_${PN} += "${libdir}/libfl.a"
>>>> +
>>>> +PSTAGING_DISABLED_virtclass-native = "1"
>>> I assume you've ran into 2.3.35 not being relocation happy? Have you been
>>> able to look at this at all? 2.3.31 works so it's something 'bad' done
>>> upstream. Thanks!
>> I did, but I didn't look into the details. bison-native wouldn't
>> rebuild when I used my flex-native pstage. bitbake -c clean
>> flex-native fixed it, so...
>
> After that would rebuilding from pstage cause the error again?
> I'm a little bit worried that we inhibit PSTAGING because e.g.
> something else is wrong (e.g. a change elsewhere that should have been
> resulted in a flex PR bump).
So, this change is fine itself. The problem is that flex 2.3.35 has
introduced a hardcoded path somewhere into the binary. So blacklisting
and bumping PR means that pstaging is sane again.
> Besides (but this is more a global remark): it would be nice if a
> recipe disables something that there is a short description why this
> is done. (at least in the commit message, but imho preferably in the
> recipe, so in half a year time, people still know why it is done and
> can much easier judge if it can be removed).
Yes, I agree with that, a comment why is good.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-08-17 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 22:45 [PATCH] flex: disabled packaged staging of native builds Jason Kridner
2010-08-16 23:43 ` Tom Rini
2010-08-17 0:07 ` Jason Kridner
2010-08-17 8:20 ` Frans Meulenbroeks
2010-08-17 17:25 ` Tom Rini [this message]
2010-08-17 19:19 ` Jason Kridner
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=4C6AC627.9050801@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 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.