From: Brian Litzinger <brian@worldcontrol.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] libungif and giflib conflict.
Date: Mon, 31 Oct 2005 22:00:37 -0800 [thread overview]
Message-ID: <20051101060037.GA30285@localhost> (raw)
In-Reply-To: <20051101055203.GA19589@crud.crud.mn.org>
> Nick Currier <docfreezzzz@gmail.com> writes:
> > I have to run libungif as all my media is built around mplayer and it simply
> > won't run on the giflib libraries.
On Mon, Oct 31, 2005 at 11:52:03PM -0600, Barry.SCHWARTZ@chemoelectric.org wrote:
> My mplayer is linked with giflib and AFAIK it works as it should. I
> suspect you need to run revdep-rebuild.
> Otherwise I would try installing libungif in /usr/local, the
> old-fashioned way, and put an entry in package.provided or something
> like that.
I had cross dependecies between mplayer and another app.
One required giflib the other libungif.
After getting tired of emerging back and forth I did
(unmerged the other lib)
emerge giflib
cd /usr/lib
ln -s libgif.so.4.1.3 libungif.so.4
All is better now.
--
Brian Litzinger
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-01 6:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 5:36 [gentoo-amd64] libungif and giflib conflict Nick Currier
2005-11-01 5:52 ` Barry.SCHWARTZ
2005-11-01 6:00 ` Brian Litzinger [this message]
2005-11-01 8:36 ` [gentoo-amd64] " Duncan
2005-11-01 15:07 ` Nick Currier
2005-11-01 17:39 ` Brian Litzinger
2005-11-01 18:19 ` [gentoo-amd64] " Duncan
2005-11-02 4:30 ` Nick Currier
2005-11-02 13:09 ` Harm Geerts
2005-11-02 19:42 ` Nick Currier
2005-11-02 20:54 ` [gentoo-amd64] " Duncan
2005-11-02 21:59 ` Harm Geerts
2005-11-02 23:07 ` [gentoo-amd64] " Duncan
2005-11-03 0:52 ` [gentoo-amd64] " Sebastian Redl
2005-11-03 2:32 ` Harm Geerts
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=20051101060037.GA30285@localhost \
--to=brian@worldcontrol.com \
--cc=gentoo-amd64@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