From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gconf-1.0.7-r2 ebuild is broken
Date: 26 Nov 2001 18:35:20 +0100 [thread overview]
Message-ID: <1006796121.628.2.camel@zoidberg> (raw)
In-Reply-To: <1121.24.38.252.76.1006655418.squirrel@thinktank.mediafarm.ch>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
sön 2001-11-25 klockan 03.30 skrev Tom von Schwerdtner:
> > When I tried to emerge galeon-1.0, this gconf ebuild was called out as
> > a dependancy.
> >
> > Here's the flaw:
> > (lots more lines like these)
> > xml-dir.c:930: structure has no member named `root'
> > xml-dir.c:936: structure has no member named `root'
> > make[2]: *** [xml-dir.lo] Error 1
> > make[2]: Leaving directory
> > `/var/tmp/portage/gconf-1.0.7-r2/work/GConf-1.0.7/backends'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> > `/var/tmp/portage/gconf-1.0.7-r2/work/GConf-1.0.7'
> > make: *** [all-recursive-am] Error 2
>
> I think this is a dependancy problem....but, I think the fix is:
It's not a dependency problem since GConf doesn't depend on libxml2 we
can't add libxml2 >= 2.4.10 to the dependency-line.
It only shows for people that already have libxml2 <= 2.4.1, if you do,
you should update it to 2.4.10 _AND_ unmerge the old version.
You don't have to unmerge gconf and galeon as suggested below.
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-11-26 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 0:48 [gentoo-dev] gconf-1.0.7-r2 ebuild is broken Collins Richey
2001-11-25 2:30 ` Tom von Schwerdtner
2001-11-26 17:35 ` Mikael Hallendal [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=1006796121.628.2.camel@zoidberg \
--to=hallski@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