From: Nicholas Burlett <nrb23@cornell.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] findutils-4.1.7.ebuild fails
Date: 21 Jan 2002 10:37:17 -0500 [thread overview]
Message-ID: <1011627438.30501.2.camel@gemini> (raw)
In-Reply-To: <1011560706.24209.29.camel@inventor.gentoo.org>
This bug is now in the database as Bug 260. Thanks for the help :->
-nick
On Sun, 2002-01-20 at 16:05, Daniel Robbins wrote:
> Please report this to bugs.gentoo.org. We won't ignore it.
>
> On Sun, 2002-01-20 at 12:06, Nicholas Burlett wrote:
> > the findutils-4.1.7.ebuild fails shortly into the compile run. I'm
> > trying to do a emerge --world update, but findutils fails on each
> > attempt. Can anyone point me in the right direction?
> >
> > The following is the tail end of the emerge output:
> >
> > make[2]: Entering directory
> > `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/find'
> > Making all in testsuite
> > make[3]: Entering directory
> > `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/find/testsuite'
> > make[3]: Nothing to be done for `all'.
> > make[3]: Leaving directory
> > `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/find/testsuite'
> > make[3]: Entering directory
> > `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/find'
> > source='fstype.c' object='fstype.o' libtool=no \
> > depfile='.deps/fstype.Po' tmpdepfile='.deps/fstype.TPo' \
> > depmode=gcc /bin/sh ../depcomp \
> > i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I../intl
> > -DLOCALEDIR=\"/usr/share/locale\" -mcpu=i686 -march=i686 -O3 -pipe -c
> > -o fstype.o `test -f fstype.c || echo './'`fstype.c
> > fstype.c:162: afs/venus.h: No such file or directory
> > fstype.c:170: sys/ioccom.h: No such file or directory
> > fstype.c: In function `in_afs':
> > fstype.c:178: storage size of `vi' isn't known
> > fstype.c:184: `VIOC_FILE_CELL_NAME' undeclared (first use in this
> > function)
> > fstype.c:184: (Each undeclared identifier is reported only once
> > fstype.c:184: for each function it appears in.)
> > make[3]: *** [fstype.o] Error 1
> > make[3]: Leaving directory
> > `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/find'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory
> > `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/find'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> > `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7'
> > make: *** [all-redirect] Error 2
> >
> > !!! ERROR: The ebuild did not complete successfully.
> > !!! Function src_compile, Line 4, Exitcode 2
> > !!! (no error message)
> >
> > !!! emerge aborting on
> > /usr/portage/sys-apps/findutils/findutils-4.1.7.ebuild .
> >
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> --
> Daniel Robbins <drobbins@gentoo.org>
> Chief Architect/President http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2002-01-21 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 19:06 [gentoo-dev] findutils-4.1.7.ebuild fails Nicholas Burlett
2002-01-20 21:05 ` Daniel Robbins
2002-01-21 15:37 ` Nicholas Burlett [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=1011627438.30501.2.camel@gemini \
--to=nrb23@cornell.edu \
--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