From: BoehmeSilvio <Boehme.Silvio@afb.de>
To: "'gentoo-dev@cvs.gentoo.org'" <gentoo-dev@cvs.gentoo.org>
Subject: [gentoo-dev] less-358-r3.ebuild
Date: Tue Nov 6 04:26:01 2001 [thread overview]
Message-ID: <E19CBDD9F21ED111A96A00805F0D6AE0EADBC2@AFBWNT01> (raw)
Hi,
there is a new ebuild for "less". But this fails while building
command.o.
I tried the r2 and got the same error.
In the first bootstrap/system merge less compiles just fine.
By
Silvio
> -----Original Message-----
> From: Collins Richey [mailto:erichey2@home.com]
> Sent: Tuesday, November 06, 2001 12:17 PM
> To: gentoo
> Subject: [gentoo-dev] gconf-1.0.7 ebuild fails
>
>
> I'm trying to emerge galeon-0.12.6 which has a dependancy for
> gconf-1.0.7. Gconf fails with
>
> xml-dir.c: In function `dir_load_doc':
> xml-dir.c:841: structure has no member named `root
> (lots of these lines)
> xml-dir.c: In function `dir_make_new_entry':
> xml-dir.c:896: structure has no member named `root'
> xml-dir.c: In function `dir_fill_cache_from_doc':
> xml-dir.c:929: structure has no member named `root'
> 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/work/GConf-1.0.7/backends'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/gconf-1.0.7/work/GConf-1.0.7'
> make: *** [all-recursive-am] Error 2
>
> Thanks,
> --
> Collins Richey
> Denver Area
> gentoo_rc6 xfce+sylpheed
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
>
reply other threads:[~2001-11-06 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E19CBDD9F21ED111A96A00805F0D6AE0EADBC2@AFBWNT01 \
--to=boehme.silvio@afb.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