From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: glib-1.2.10-r5 broken for lame
Date: Wed, 23 May 2007 09:27:37 +0200 [thread overview]
Message-ID: <200705230927.41312.bo.andresen@zlin.dk> (raw)
In-Reply-To: <f30on0$49m$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On Wednesday 23 May 2007 08:57:57 Sven Köhler wrote:
> > trying to update my system , glib is broken
> >
> > here is the output
>
> Seems like a libtool problem. Please try to update libtool, and then try
> to update glib again.
>
> Maybe that works.
Or maybe not.. ;) Downgrading libtool on the other hand would work..
# SED=sed emerge -1 glib
would work too..
https://bugs.gentoo.org/show_bug.cgi?id=168198
--
Bo Andresen
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-23 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 8:45 [gentoo-user] glib-1.2.10-r5 broken for lame Stéphane ANCELOT
2007-05-23 6:57 ` [gentoo-user] " Sven Köhler
2007-05-23 7:27 ` Bo Ørsted Andresen [this message]
2007-05-23 7:35 ` Naga
2007-05-23 16:59 ` Stéphane ANCELOT
2007-05-23 7:34 ` [gentoo-user] " Naga
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=200705230927.41312.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--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