From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: qmake issue
Date: Mon, 04 Jan 2010 21:32:22 +0100 [thread overview]
Message-ID: <hhtj8l$acs$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b11001041214w71476fedrcfa5a9cfb7137ebc@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04-01-10 21:14, Frans Meulenbroeks wrote:
> 2010/1/4 Richard Purdie <rpurdie@rpsys.net>:
>> On Mon, 2010-01-04 at 08:31 +0100, Frans Meulenbroeks wrote:
>>> Yeah figured out after a brief discussion on #oe that they probably
>>> didn't need to be staged.
>>>
>>> Actually the recipe does not contain any staging, so this is a side
>>> effect of the new automated staging.
>>> It could well be that other, non qmake recipes also suffer from this.
>>>
>>> The fix for mythtv is probably to have an empty do_stage()
>>>
>>> However as a general rule the -L and -I flags to staging should be
>>> last, not first.
>>> And, ideally, when building a recipe the old contents from that
>>> package in staging should be removed first.
>>> By removing that we avoid the problem that if rX adds a file A to
>>> staging and rY does not do so any more, the file A still remains in
>>> staging (although perhaps incompatible with what rY made.
>>
>> If packaged staging is enabled this should happen already...
>>
>> Cheers,
>>
>> Richard
>>
> Ehm, I use angstrom unstable head on the beagleboard.I've been told on
> #oe that angstrom used pacakged staging.
> I've removed my tmp dir and rebuild from scratch on dec 30, 2009,
> including mythtv.
> Yesterday I rebuild the latest version of mythtv, and it linked
> against the myth lib in staging (produced by the same recipe).
> As the lib was changed between those versions it gave a linking error.
> After removing the lib from staging manually and rebuilding mythtv
> builds properly.
> To me this seems there is still a problem.
Packaged-staging only works if you have built opkg-native, otherwise it
won't remove things from staging. The problem is that you can't to
'bitbake opkg-native' twice, so the angstrom buildscripts now do:
http://dominion.thruhere.net/git/cgit.cgi/openembedded/commit/?h=org.openembedded.dev&id=6fb8200b0002fad7ed4b67b7b5a01a54bc3db91c
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLQlBWMkyGM64RGpERAtFbAJ9bzOb4XvpCme4V2E9t8ER9tYcVsACcC7nq
qqFJxVxAQKpndDkZeEANHe0=
=AvU+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-04 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 16:33 qmake issue Frans Meulenbroeks
2010-01-03 21:09 ` Phil Blundell
2010-01-04 7:31 ` Frans Meulenbroeks
2010-01-04 15:56 ` Richard Purdie
2010-01-04 20:14 ` Frans Meulenbroeks
2010-01-04 20:32 ` Koen Kooi [this message]
2010-01-04 20:41 ` Frans Meulenbroeks
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='hhtj8l$acs$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.