From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [oe-commits] org.oe.dev udev-118: go back in time to udev-115 which seems to work slightly better on some Zaurus models
Date: Sat, 14 Jun 2008 20:14:43 +0200 [thread overview]
Message-ID: <g311qk$q73$1@ger.gmane.org> (raw)
In-Reply-To: <20080614170647.GA3428@cimmeria.hyboria>
Graeme Gregory wrote:
> On Sat, Jun 14, 2008 at 03:34:34PM +0200, Andrea Adami wrote:
>> Koen,
>>
>> no evident problems == same behaviour as 118
>>
>> could you keep an eye on the oebug 4118?
>>
> Well I tried to build for tosa, but Im falling over on the fact the
> kernel doesnt build and libtool seems to be busted :-(
I tracked this problem down to the fact that both libtool-cross and
libtool install stuff into staging.
A possible solution would be to mimic gcc(-cross) so libtool-cross
creates libltdl packages and stages things and libtool doesn't. This
does mean that both libtool-cross and libtool need to be the same version.
To get around the current problem:
bitbake -b packages/libtool/libtool-cross_2.2.4.bb
That will tell packaged-staging to (re)stage the correct headers and m4
files.
regards,
Koen
next prev parent reply other threads:[~2008-06-14 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080613225643.86B4D1881B6@amethyst.openembedded.net>
2008-06-13 23:17 ` [oe-commits] org.oe.dev udev-118: go back in time to udev-115 which seems to work slightly better on some Zaurus models Graeme Gregory
2008-06-14 8:28 ` Koen Kooi
2008-06-14 9:10 ` Andrea Adami
2008-06-14 10:18 ` Koen Kooi
2008-06-14 13:34 ` Andrea Adami
2008-06-14 17:06 ` Graeme Gregory
2008-06-14 18:14 ` Koen Kooi [this message]
2008-06-15 9:27 ` Gordon
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='g311qk$q73$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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