From: Philip Webb <purslow@ca.inter.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] emerging glib fails to create .la files
Date: Sat, 20 Aug 2011 17:39:55 -0400 [thread overview]
Message-ID: <20110820213955.GA3133@ca.inter.net> (raw)
I've run into a strange problem updating my netbook.
I merged glib-2.28.8 successfully as part of a Revdep-Rebuild job,
it being a dep for one of the pkgs in the R-R list.
However after that, merging gtk+-2.24.4 librsvg-2.34.0 libglade-2.6.4
all failed with a libtool error : "libtool: link: /usr/lib/libgio-2.0.0.la
is not a valid libtool archive" or ditto for libgobject ;
indeed, those files do not exist in the netbook,
but in my already updated desktop machine, glib did create them.
The glib merge msgs did include a recommendation to remerge dbus-glib ,
but that required dbus & that too failed with a similar libtool error !
I tried remerging glib , but it still didn't create the needed .la files.
The only item thrown up by Google was a Gentoo forum thread
re a different problem, but recent & suggesting gcc needed updating
or users could run into problems with Gnome-type apps.
I'm presently updating to gcc-4.4.5 (previously 4.4.3),
but that will take > 3 hr in the netbook, so any advice is welcome.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next reply other threads:[~2011-08-20 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 21:39 Philip Webb [this message]
2011-08-20 23:01 ` [gentoo-user] emerging glib fails to create .la files : PS Philip Webb
2011-08-20 23:05 ` [gentoo-user] emerging glib fails to create .la files Dale
2011-08-20 23:28 ` Philip Webb
2011-08-21 2:43 ` Dale
2011-08-21 2:05 ` [gentoo-user] emerging glib fails to create .la files : SOLVED Philip Webb
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=20110820213955.GA3133@ca.inter.net \
--to=purslow@ca.inter.net \
--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