From: Meino Christian Cramer <Meino.Cramer@gmx.de>
To: gentoo-user@lists.gentoo.org, volker.armin.hemmann@tu-clausthal.de
Subject: Re: [gentoo-user] Library problem after upgrade to gcc-4.1.1
Date: Tue, 24 Oct 2006 11:13:47 +0200 (CEST) [thread overview]
Message-ID: <20061024.111347.78713699.Meino.Cramer@gmx.de> (raw)
In-Reply-To: <200609112145.01584.volker.armin.hemmann@tu-clausthal.de>
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
Subject: Re: [gentoo-user] Library problem after upgrade to gcc-4.1.1
Date: Mon, 11 Sep 2006 21:45:01 +0200
> On Monday 11 September 2006 20:52, JC Denton wrote:
> > Hi!
> >
> > I upgraded to gcc-4.1.1 but when I did emerge --deep --update --newuse
> > world I got the following:
> >
> > libtool: link: warning:
> > `/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/../../..//lib*.la seems to be moved
> >
> > where lib*.la stands for some libraries.
> >
> > For example: libgconf-2.la is in this list of warnings and it is located
> > under /usr/lib/ Is there a link I have to set up?
> >
> > I was emerging gnucash when I saw this warnings but I think it occured also
> > with other programs.
> >
> > What does this mean and how can I fix that?
>
> AFAIR this is harmless, and can be ignored. It is caused, because the files
> are installed in a temp-dir and copied over by portage.
>
> but you should use the search funktion of your favorite mail archive, this
> question has been answered somewhere.
>
> --
> gentoo-user@gentoo.org mailing list
>
I searched the archives, I searched via Google...I found just another
thread saying that there is "some thread in the past" which handles
the problem...but I cannot find the thread.
Instead I found a patch here
http://sources.catmur.co.uk/viewcvs/svn/gentoo/patches/sys-devel/libtool/no-seems-to-be-moved.patch?rev=596&view=markup
which seem to try to solce the problem...but also it seems not to be
included in the official gentoo distro.
How can I prevent these tons of "seems to be moved" messages while
compiling "bigger tasks" ? They do slowdown the process.
As an example:
I did a revdep-rebuild for:
net-libs/libsoup-2.2.94
gnome-extra/evolution-data-server-1.6.2
mail-client/evolution-2.6.2-r1
media-libs/libmp4v2-1.4.1
media-libs/faad2-2.0-r11 [2.0-r3] USE="(-xmms*)"
which results in 9100 messages of the described kind. I think, that
can be avoided ... especially when it is harmless (== superflous)
warning.
Kind regards,
mcc
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-10-24 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 18:52 [gentoo-user] Library problem after upgrade to gcc-4.1.1 JC Denton
2006-09-11 19:45 ` Hemmann, Volker Armin
2006-10-24 9:13 ` Meino Christian Cramer [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=20061024.111347.78713699.Meino.Cramer@gmx.de \
--to=meino.cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
--cc=volker.armin.hemmann@tu-clausthal.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