Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 364885 - sys-apps/findutils-4.5.9: failed to make
Summary: sys-apps/findutils-4.5.9: failed to make
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: AMD64 OS X
: Normal major (vote)
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-26 03:36 UTC by James G. Kim
Modified: 2011-08-05 14:53 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James G. Kim 2011-04-26 03:36:10 UTC
When I emerge sys-apps/findutils-4.5.9, emake failed with the following messages.

It could be avoided with adding the lines below before emake.

cd "${S}"
touch doc/find.info

Reproducible: Always

Steps to Reproduce:
1. emerge =sys-apps/findutils-4.5.9
Actual Results:  
find.texi:10: @include `../locate/dblocation.texi': No such file or directory.
find.texi:573: warning: undefined flag: LOCATE_DB.
find.texi:2731: warning: undefined flag: LOCATE_DB.
find.texi:2733: warning: undefined flag: LOCATE_DB.
find.texi:3216: warning: undefined flag: LOCATE_DB.
find.texi:3402: warning: undefined flag: LOCATE_DB.
find.texi:5362: warning: undefined flag: LOCATE_DB.
find.texi:5370: warning: undefined flag: LOCATE_DB.
makeinfo: Removing output file `find.info' due to errors; use --force to preserve.
make[1]: *** [find.info] Error 1

...

emake failed
 * ERROR: sys-apps/findutils-4.5.9 failed (install phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  62:  Called call-ebuildshell 'src_install'
 *   environment, line 579:  Called src_install
 *   environment, line 3121:  Called die
 * The specific snippet of code:
 *       emake DESTDIR="${D}" install || die;
Comment 1 Markus Duft (RETIRED) gentoo-dev 2011-05-24 06:08:54 UTC
sounds like it could be related to bug #352254. wrong timestamps could force an autoreconf or documentation updates even when dependencies are missing.

could you check, wether the modification times of files on the disk match with those in the archive?
Comment 2 James G. Kim 2011-05-24 06:23:04 UTC
(In reply to comment #1)
> sounds like it could be related to bug #352254. wrong timestamps could force an
> autoreconf or documentation updates even when dependencies are missing.
> 
> could you check, wether the modification times of files on the disk match with
> those in the archive?

How can I check it? Please let me know which files need to be compared.
Comment 3 Markus Duft (RETIRED) gentoo-dev 2011-05-24 06:45:51 UTC
check the times of doc/find.texi and find.info:

 ls -la ${S}/doc/find.*
 tar --wildcards -tvzf /usr/portage/distfiles/findutils-4.5.9.tar.gz findutils-4.5.9/doc/find.*

PORTDIR is usually ${EPREFIX}/usr/portage, ${S} is usually ${EPREFIX}/var/tmp/portage/sys-apps/findutils-4.5.9/work/findutils-4.5.9

you'll have to start a build for ${S} to exist of course... :) and: find.info should be newer than find.texi in both cases.
Comment 4 James G. Kim 2011-05-24 07:02:36 UTC
(In reply to comment #3)
> check the times of doc/find.texi and find.info:
> 
>  ls -la ${S}/doc/find.*
>  tar --wildcards -tvzf /usr/portage/distfiles/findutils-4.5.9.tar.gz
> findutils-4.5.9/doc/find.*
> 
> PORTDIR is usually ${EPREFIX}/usr/portage, ${S} is usually
> ${EPREFIX}/var/tmp/portage/sys-apps/findutils-4.5.9/work/findutils-4.5.9
> 
> you'll have to start a build for ${S} to exist of course... :) and: find.info
> should be newer than find.texi in both cases.

The modification times of files on the disk are exactly same as those in the archive, and like you said, find.info is newer than find.texi in both cases.
Comment 5 Markus Duft (RETIRED) gentoo-dev 2011-05-24 07:15:51 UTC
hm, ok, so somebody with a mac will have to take it from here ;)
Comment 6 Kim Robertson 2011-06-01 23:21:05 UTC
Hi,
I am having the same issue on a solaris based prefix.

kim@ra:~$ ls -la /opt/gentoo/var/tmp/portage/sys-apps/findutils-4.5.9/work/findutils-4.5.9/doc/find.*
-rw-r--r-- 1 kim staff   6091 Apr 30  2010 /opt/gentoo/var/tmp/portage/sys-apps/findutils-4.5.9/work/findutils-4.5.9/doc/find.info
-rw-r--r-- 1 kim staff 298848 Apr 30  2010 /opt/gentoo/var/tmp/portage/sys-apps/findutils-4.5.9/work/findutils-4.5.9/doc/find.info-1
-rw-r--r-- 1 kim staff 208090 Apr 30  2010 /opt/gentoo/var/tmp/portage/sys-apps/findutils-4.5.9/work/findutils-4.5.9/doc/find.texi
kim@ra:~$ tar --wildcards -tvzf /opt/gentoo/usr/portage/distfiles/findutils-4.5.9.tar.gz findutils-4.5.9/doc/find.*
-rw-r--r-- 0/0          298848 2010-04-30 09:27 findutils-4.5.9/doc/find.info-1
-rw-r--r-- 0/0            6091 2010-04-30 09:27 findutils-4.5.9/doc/find.info
-rw-r--r-- 0/0          208090 2010-04-30 09:18 findutils-4.5.9/doc/find.texi

What do I need to look at for the cause? I can go through and run the compile it manually step by step.
Comment 7 yegle 2011-06-06 15:56:36 UTC
Before this bug is fixed, can we add some notice into the bootstrap guide first?

http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-macos.xml

I've stuck in this problem for days and finally find that I can emerge findutils-4.4.0 instead to finish the bootstrap process...

Hope this can help anyone who was doing a bootstrap of Gentoo Prefix :-)
Comment 8 Kim Robertson 2011-06-07 00:05:09 UTC
I also had the issue but it seems that it is just findutils-4.5.9.
I got findutils-4.5.8 to compile and install.

My work around was:
echo "=sys-apps/findutils-4.5.9" >> $EPREFIX/etc/portage/package.mask
Comment 9 Naohiro Aota gentoo-dev 2011-06-21 13:06:51 UTC
 }
 
 src_install() {
+	emake -C locate dblocation.texi
 	emake DESTDIR="${D}" install || die
 	dodoc NEWS README TODO ChangeLog
 }

The error saying, there is no ../locate/dblocation.texi availabe.
How about adding a workaound (the above added line) to create the file?
Comment 10 Fabian Groffen gentoo-dev 2011-06-21 13:09:01 UTC
hmm, looks simple enough to me
Comment 11 Alexey Shvetsov archtester gentoo-dev 2011-07-02 13:15:14 UTC
Same bug on amd64-linux
Comment 12 Naohiro Aota gentoo-dev 2011-08-05 08:51:55 UTC
ping. What's going on this bug? Since the package is in @system, we should fix or unkeyword ASAP.
Comment 13 Fabian Groffen gentoo-dev 2011-08-05 09:08:39 UTC
I committed your patch, thanks!
Comment 14 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2011-08-05 14:53:22 UTC
For the record, I never had a problem on amd64-linux (rhel4).