From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: fakeroot fails to build
Date: Wed, 25 Feb 2009 09:14:53 -0600 [thread overview]
Message-ID: <49A5606D.3050507@dls.net> (raw)
In-Reply-To: <1235550209.2621.28.camel@andromeda>
Michael 'Mickey' Lauer wrote:
> Am Mittwoch, den 25.02.2009, 08:57 +0100 schrieb Koen Kooi:
>> On 25-02-09 07:53, Mike (mwester) wrote:
>>> fakeroot fails to build -- any idea how we can fix this?
>> By reverting the merge of the sane-defaults branch that got merged with
>> zero review
>
> Ah right, I probably didn't wait long enough. Ok, I might as well revert
> it and continue working in other branches. Is there a command to revert
> merging a whole branch or do I need to call git-revert for every
> revision?
Don't revert everything just because of one fakeroot problem -- I can
work around that by adding (another) PREFERRED_VERSION to use the older one.
This issue is not related to the sane-defaults branch at all; that was
not my point. This type of build failure has been happening for the
past week or two on a number of recipes -- my posting the fakeroot
failure to the list was just a random selection out of the list of
similar problems.
I'd much prefer to figure out what the specific libtool issue is and fix
that, rather than revert the sane-defaults changes (and by the way, I
did review that branch and did not see anything which seemed problematic
to me, or I would have said something!)
So it sounds like there's not a libtool problem; rather I need to
upgrade to the new libtool entirely then. :-( That's unfortunate,
really unfortunate timing -- but timing is not an OE issue. :-(
(BTW, the reason libtool got locked down for me is because it made
pkgconfig fail to build, so I might be back with questions on how to
make that work if that failure still exists.)
((Also, are there any non-angstrom distros still left in OE, besides
SlugOS? I really feel like I'm swimming upstream all the time with OE
-- things break for me so often that just don't seem to affect anyone
else...))
-Mike
next prev parent reply other threads:[~2009-02-25 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 6:53 fakeroot fails to build Mike (mwester)
2009-02-25 7:57 ` Koen Kooi
2009-02-25 8:23 ` Michael 'Mickey' Lauer
2009-02-25 15:04 ` Koen Kooi
2009-02-25 15:14 ` Mike (mwester) [this message]
2009-02-25 15:43 ` OE breakages, was: " Koen Kooi
2009-02-26 13:05 ` Bernhard Guillon
2009-02-27 19:30 ` Rodrigo Vivi
2009-02-25 18:25 ` Minimal distro (was: fakeroot fails to build) Michael 'Mickey' Lauer
2009-02-25 18:59 ` Tom Rini
2009-02-25 8:06 ` fakeroot fails to build Michael 'Mickey' Lauer
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=49A5606D.3050507@dls.net \
--to=mwester@dls.net \
--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