From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: staging problem
Date: Sun, 23 May 2010 17:59:14 +0200 [thread overview]
Message-ID: <htbjci$p3q$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTikD-rYl148gtkJZB859Q-hOdV0AXYxuyBdpodpY@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-05-10 17:17, Khem Raj wrote:
> On Sun, May 23, 2010 at 2:22 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> On 21-05-10 16:47, Gary Thomas wrote:
>>>> Trying a clean build
>>>> MACHINE="beagleboard"
>>>> DISTRO="angstrom-2008.1"
>>>> org.openembedded.dev 2c153f33b8ebb807a622ad9ae92ed5341a356740
>>>>
>>>> I get failures like this (in many packages):
>
> I pushed a fix:
>
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=104b91c471125482eb83893425fb031557e892b4
>
> That seems to solve the duplicate header problem for me and tk still
> builds. As the commit says, do a 'bitbake glibc' afterwards to have
> packaged-staging restore the headers.
>
>> hmm. Its deleting the libc header file isn't it. why cant they co-exist.?
packaged-staging reaps all files the recipe staged, so if the recipe is
*overwriting* headers like it was doing you will have missing headers
till you reinstall them. Your glibc regexp.h was gone already.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL+VDSMkyGM64RGpERAlE+AJ0ZLmcPYIy4SymSufBGwDefYY9HJQCfSfsz
cCbXntNX8XdT8vxA5cdPUd8=
=C3cu
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-05-23 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:47 staging problem Gary Thomas
2010-05-21 20:27 ` Khem Raj
2010-05-21 20:42 ` Koen Kooi
2010-05-21 22:17 ` Gary Thomas
2010-05-22 11:51 ` Gary Thomas
2010-05-22 19:25 ` Koen Kooi
2010-05-23 9:22 ` Koen Kooi
2010-05-23 15:17 ` Khem Raj
2010-05-23 15:59 ` Koen Kooi [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='htbjci$p3q$1@dough.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.