From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: libtool problem
Date: Tue, 03 Feb 2009 14:47:51 +0200 [thread overview]
Message-ID: <gm9ed7$rf$1@ger.gmane.org> (raw)
In-Reply-To: <tkrat.913134b2bec76c1f@igpm.rwth-aachen.de>
Helmut Jarausch wrote:
> On 3 Feb, Dirk Heinrichs wrote:
>> Am Dienstag, 3. Februar 2009 13:15:55 schrieb Helmut Jarausch:
>>
>>> since a short time many (not all) packages fail to build with a message
>>> like
>>> /bin/sed: can't read /usr/lib/gcc/i686-pc-linux-gnu/4.3.2/libgomp.la
>>>
>>> The problem is that I have upgraded to gcc-4.3.3 so there is no path
>>> /usr/lib/gcc/i686-pc-linux-gnu/4.3.2
>>> anymore.
>>>
>>> I have rebuilt libtool, sourced /etc/profile
>>> still I cannot get rid of this problem.
>> Did you run "fix_libtool_files.sh 4.3.2"?
>>
>
> Thanks!
> Where does this beast come from?
It's also in the official documentation. Chapter "Gentoo GCC Upgrade
Guide", section "Frequent Error Messages" :P
http://www.gentoo.org/doc/en/gcc-upgrading.xml#doc_chap5
next prev parent reply other threads:[~2009-02-03 12:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 12:15 [gentoo-user] libtool problem Helmut Jarausch
2009-02-03 12:18 ` Dirk Heinrichs
2009-02-03 12:24 ` Helmut Jarausch
2009-02-03 12:27 ` Justin
2009-02-03 12:47 ` Nikos Chantziaras [this message]
2009-02-03 12:25 ` Volker Armin Hemmann
2009-02-03 13:12 ` Neil Bothwick
2009-02-03 15:03 ` Helmut Jarausch
2009-02-03 15:23 ` Mike Kazantsev
2009-02-03 15:36 ` Neil Bothwick
2009-02-04 3:25 ` [gentoo-user] " ABCD
2009-02-04 9:50 ` Neil Bothwick
2009-02-04 18:17 ` Dirk Heinrichs
2009-02-04 20:21 ` Alan McKinnon
2009-02-04 20:40 ` Dirk Heinrichs
2009-02-04 21:07 ` Alan McKinnon
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='gm9ed7$rf$1@ger.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@lists.gentoo.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