From: "Tom von Schwerdtner" <tvon@etria.org>
To: gentoo-dev@gentoo.org
Cc: erichey2@home.com
Subject: Re: [gentoo-dev] gconf-1.0.7-r2 ebuild is broken
Date: Sun, 25 Nov 2001 03:30:18 +0100 (CET) [thread overview]
Message-ID: <1121.24.38.252.76.1006655418.squirrel@thinktank.mediafarm.ch> (raw)
In-Reply-To: <20011124174827.02d558ca.erichey2@home.com>
> 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:
remerge libxml2
and to be safe, unmerge old libxml2, gconf and galeon before merging the new
ones.
HTH,
-Tom
next prev parent reply other threads:[~2001-11-25 2:39 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 [this message]
2001-11-26 17:35 ` 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=1121.24.38.252.76.1006655418.squirrel@thinktank.mediafarm.ch \
--to=tvon@etria.org \
--cc=erichey2@home.com \
--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