From: "Liebich Wolfgang" <wolfgang.liebich@siemens.com>
To: <gentoo-user@lists.gentoo.org>
Subject: SOLVED: [gentoo-user] Probleme beim Update von "mutt"
Date: Tue, 27 Sep 2005 11:57:17 +0200 [thread overview]
Message-ID: <649A59E9F7977F449E5792357A9DDB2CAB6F9F@nets13ha.ww300.siemens.net> (raw)
Hi,
Sorry about the wrong language, I thought I was writing to "gentoo-user-de" :-/
Thanks for the tip - I could recompile mutt fine now.
Ciao,
Wolfgang Liebich
> -----Ursprüngliche Nachricht-----
> Von: Michael Schreckenbauer [mailto:grimlog@gmx.de]
> Gesendet: Dienstag, 27. September 2005 11:45
> An: gentoo-user@lists.gentoo.org
> Betreff: Re: [gentoo-user] Probleme beim Update von "mutt"
>
> Hi Wolfgang,
>
> Am Dienstag, 27. September 2005 11:07 schrieb Liebich Wolfgang:
> > Hi,
> > Nachdem ich beim Starten von mutt auf einmal eine Fehlermeldung wg.
> > fehlerhafter libgdbm.so.2 (Länge 0!) bekam, Versuchte ich,
> mutt neu zu
> > installieren. Das ging aber schief mit einer (mir unverständlichen)
> > autoconf-Fehlermeldung. Kann hier jemand etwas damit
> anfangen? Unten habe
> > ich eh hinkopiert, was ich gemacht habe (Da ich keinen Mutt
> habe, muß ich
> > derzeit outlook verwenden *seufz*)...
>
> this is an english talking ML, but as I'm german too, I'll
> try to answer this.
> There's app-text/dgs:
> * app-text/dgs
> Available versions: 1234
> Installed: none
> Homepage: http://ronaldmcnightrider.ytmnd.com/
> Description: fake ebuild to force removal of
> broken path_dps.m4
>
> Maybe this fixes your problem, the last line in your error
> message sounds like
> that.
>
> > TIA,
> > Wolfgang Liebich, dazed & confused...
>
> HTH,
> Michael
>
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list
reply other threads:[~2005-09-27 10:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=649A59E9F7977F449E5792357A9DDB2CAB6F9F@nets13ha.ww300.siemens.net \
--to=wolfgang.liebich@siemens.com \
--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