findutils-4.1.7.ebuild fails to build on my box as follows: [snip] Making all in intl make[2]: Entering directory `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/intl' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/findutils-4.1.7/work/findutils-4.1.7/intl' Making all in find 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' i686-pc-linux-gnu-gcc -mcpu=i686 -march=i686 -O3 -pipe -o find find.o fstype.o parser.o pred.o tree.o util.o version.o ../lib/libfind.a fstype.o: In function `filesystem_type_uncached': fstype.o(.text+0x1c3): undefined reference to `pioctl' collect2: ld returned 1 exit status make[3]: *** [find] 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 . If there's anything more you need to know that I didn't think to include, feel free to email me: nrb23@cornell.edu
Not sure as to why this happens ... what version binutils are you using ?
could this be the problem? bash-2.05a# /usr/lib/portage/bin/pkglist | grep binutils sys-devel/binutils-2.11.92.0.12.3-r1 sys-devel/binutils-2.11.90.0.7 I'm not sure why there are two binutils in the package list..
no, that's not the problem. Hmm...
And I'm assuming that this happens every time you try to merge the findutils ebuild? It dies in the exact same place?
Yes, although I haven't attempted to re-build it since I reported the bug.
try rebuilding it with an updated Portage tree and see what happens.
due to lack of info, marking as WORKSFORME for now.
the problem is still there and IMHO it is AFS-related. if you have AFS installed, the findutils ebuild fails at exactly the same location.
I have just confirmed the afs findutils bug, Have to look into how to fix it
I found when I added the following lines to the findutils ebuild, things worked. --- findutils-4.1.7-r1.ebuild 2002-11-08 09:05:10.000000000 -0700 +++ findutils-4.1.7-r1.ebuild.new 2002-11-07 16:51:50.000000000 -0700 @@ -22,6 +22,10 @@ use nls || myconf="${myconf} --disable-nls" + export CPPFLAGS=-I/usr/afsws/include + export LDFLAGS=-lpam + export LIBS=/usr/afsws/lib/pam_afs.so.1 + ./configure --host=${CHOST} \ --prefix=/usr \ --localstatedir=/var/spool/locate \ I don't propose this as a fix, but simply as where to look for a fix. I'll leave the final resolution to the paid experts ;-)
I commited this as a temp fix if use afs is present THX
