From: Uriel <uriel99@gmail.com>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] crosstool fails on gentoo
Date: Mon, 2 Jun 2008 21:25:07 +0200 [thread overview]
Message-ID: <5d375e920806021225w3a98fec0l87ae4499838ae91b@mail.gmail.com> (raw)
In-Reply-To: <20080601151213.GA10795@nibiru.local>
Thanks for reminding us how boring and sad life in Plan 9 is without
the sadomasochistic joys and pleassures of crosscompiling in the holy
gnu/auto*hell land.
Specially loved the line:
>> > [ALL ] *** [Gentoo] sanity check failed! ***
Wonder if they had Einstein's definition of insanity in mind... the
(open and closed source) software industry certainly could make a good
textbook example... maybe they will use it for the next DSM.
uriel
On Sun, Jun 1, 2008 at 5:12 PM, Enrico Weigelt <weigelt@metux.de> wrote:
> * Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote:
>
>> On Wednesday 28 May 2008 18:52:14 Lance Spaulding wrote:
>> > I'm trying to use crosstool-ng to build an ARM toolchain but if fails
>> > with the following error message:
>> > [ALL ] *** [Gentoo] sanity check failed! ***
>> > [ALL ] *** libtool.m4 and ltmain.sh have a version mismatch! ***
>> > [ALL ] *** (libtool.m4 = 1.5.23b, ltmain.sh = "1.5.24 Debian 1.5.24-1") ***
>>
>> This was already reported a few days ago:
>> http://sourceware.org/ml/crossgcc/2008-05/msg00080.html
>>
>> > It looks like several people have ran into this error on gentoo but I
>> > haven't been able to find a solution anywhere (and got no replies to
>> > this question in the gentoo forums). Anyone have a fix for this?
>>
>> As suggested by Enrico in that message: "we should recreate the autotools+libtool
>> stuff before compiling."
>
> Right, manually running autoreconf -fi && libtoolize on the already uncompressed
> tree fixed it for me.
>
> Of course this manual hack is ugly, it should be done automatically after
> decompression.
>
>
> cu
> --
> ---------------------------------------------------------------------
> Enrico Weigelt == metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
> Please visit the OpenSource QM Taskforce:
> http://wiki.metux.de/public/OpenSource_QM_Taskforce
> Patches / Fixes for a lot dozens of packages in dozens of versions:
> http://patches.metux.de/
> ---------------------------------------------------------------------
>
>
next prev parent reply other threads:[~2008-06-02 19:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <483D8DBE.4090005@cableone.net>
[not found] ` <200805282337.11349.yann.morin.1998@anciens.enib.fr>
2008-06-01 15:12 ` Enrico Weigelt
2008-06-02 19:25 ` Uriel [this message]
2008-06-02 19:55 ` ron minnich
2008-06-02 19:57 ` erik quanstrom
2008-06-02 20:09 ` Eric Van Hensbergen
2008-06-02 20:37 ` Uriel
2008-06-02 20:45 ` erik quanstrom
2008-06-02 21:00 ` Uriel
2008-06-02 22:32 ` Roman Shaposhnik
2008-06-02 23:00 ` Iruata Souza
2008-06-02 23:21 ` ron minnich
2008-06-03 0:50 ` Iruata Souza
2008-06-03 0:54 ` erik quanstrom
2008-06-03 2:02 ` Nick LaForge
2008-06-05 11:11 ` Enrico Weigelt
2008-06-05 11:21 ` Bruce Ellis
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=5d375e920806021225w3a98fec0l87ae4499838ae91b@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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;
as well as URLs for NNTP newsgroup(s).