From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] libogg, libvorbis and kdemultimedia-cvs
Date: Thu, 12 Jun 2003 10:22:06 +0200 [thread overview]
Message-ID: <200306121022.07012.pauldv@gentoo.org> (raw)
In-Reply-To: <200306121211.24479.luke@trolltech.com>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 495 bytes --]
On Thursday 12 June 2003 04:11, Luke Graham wrote:
> Are these symlinks really correct?
>
It looks like a mess, maybe try to unmerge vorbis and then remerge it, in
separate steps. You might also want to delete some of the spurious symlinks
after unmerging.
> Do the kde people know something we dont?
Only that you seem to have a header/library mismatch in your vorbis libraries.
--
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-06-12 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 2:11 [gentoo-dev] libogg, libvorbis and kdemultimedia-cvs Luke Graham
2003-06-12 8:22 ` Paul de Vrieze [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=200306121022.07012.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-dev@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