From: AGottinger@t-online.de (Achim Gottinger)
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] gconf-1.0.7 ebuild fails
Date: Wed Nov 7 04:02:01 2001 [thread overview]
Message-ID: <3BE912B7.3F645BEF@gentoo.org> (raw)
In-Reply-To: 200111061739.fA6HdT403664@riker.skynet.be
Bart Verwilst wrote:
>
> 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...)
>
libxml stores it's headers in /usr/include/gnome-xml and has a symlink
to that dir called libxml in that dir
libxml2 stores it's headers directly in /usr/include/libxml
gconf uses headers in a way like <libxml/[whatever.h]> so I guess it's
just a problem of the include paths order
passed to gcc.
Well I tried to patch gconf by replacing all <libxml'x with <gnome-xml's
in the backends subfolder. After that
it builded. I just commited the patch to cvs.
achim~
> ||
> ||
> || 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
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-11-07 11:01 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
2001-11-07 4:02 ` Achim Gottinger [this message]
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=3BE912B7.3F645BEF@gentoo.org \
--to=agottinger@t-online.de \
--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