From: Bart Verwilst <verwilst@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] gconf-1.0.7 ebuild fails
Date: Tue Nov 6 10:41:02 2001 [thread overview]
Message-ID: <200111061739.fA6HdT403664@riker.skynet.be> (raw)
In-Reply-To: <1005068147.27202.7.camel@nosferatu.lan>
On Tuesday 06 November 2001 18:35, you wrote:
<snip>
||
|| NOTE: do not merge libxml2 again !!
One last remark:
libxml2 is needed by KDE 2.2.x, so it's necessary te merge libxml2 again as
well after doing the "find /var/db/pkg -iname 'libxml*.ebuild' |xargs -i \
ebuild {} unmerge" command. libxml2 installs in a different location than
libxml, so there really is no problem... I did the same, and it works for
me... (i installed libxml2 after gconf was compiled successfully...)
||
||
|| PS: please use our new gentoo-user list for user related questions, and
|| help, thanks :)
||
||
|| Greetings
--
Bart Verwilst
Gentoo Linux Developer, Desktop Team
Gent, Belgium
next prev parent reply other threads:[~2001-11-06 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 4:18 [gentoo-dev] gconf-1.0.7 ebuild fails Collins Richey
2001-11-06 10:34 ` Martin Schlemmer
2001-11-06 10:41 ` Bart Verwilst [this message]
2001-11-07 4:02 ` Achim Gottinger
2001-11-07 5:46 ` Mikael Hallendal
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=200111061739.fA6HdT403664@riker.skynet.be \
--to=verwilst@gentoo.org \
--cc=gentoo-dev@cvs.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