Summary: | dev-libs/xapian-bindings-1.3.5: fail to emerge with '*** No rule to make target 'docs/index.html', needed by 'all-am'.' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | PetaMem R&D <info> |
Component: | Current packages | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugs, franz.trischberger, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Complete build log |
Description
PetaMem R&D
2016-04-09 08:59:55 UTC
The excerpt from the build log does not contain the actual error. Please post a complete build log. Created attachment 430002 [details]
Complete build log
Please educate me where the "actual error" is visible here.
Thanks for the build log! Sorry for not looking carefully at your description. It contains the error after all: make[3]: *** No rule to make target 'docs/index.html', needed by 'all-am'. Stop. In the full build log I can see a "make -j16". Does emerging with MAKEOPTS="-j1" help? If so, the Makefile is not parallel safe. > In the full build log I can see a "make -j16". Does emerging with > MAKEOPTS="-j1" help? If so, the Makefile is not parallel safe. Ok. # MAKEOPTS="-j1" emerge -a dev-libs/xapian-bindings yields exactly the same result. I mean 1.3.4 worked as well with parallel build (btw - we have not -j16 but load limitation, so the 16 seems to come from autodetecting the number of CPUs) I solved the problem for now by masking 1.3.5 and above so far so good: # emerge -a app-text/xapian-omega dev-libs/xapian dev-libs/xapian-bindings These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] dev-libs/xapian-1.3.4-r2 [1.3.5] [ebuild UD ] app-text/xapian-omega-1.3.4 [1.3.5] [ebuild R ] dev-libs/xapian-bindings-1.3.4 Would you like to merge these packages? [Yes/No] Yes >>> Verifying ebuild manifests >>> Emerging (1 of 3) dev-libs/xapian-1.3.4-r2::gentoo >>> Installing (1 of 3) dev-libs/xapian-1.3.4-r2::gentoo >>> Recording dev-libs/xapian in "world" favorites file... >>> Emerging (2 of 3) app-text/xapian-omega-1.3.4::gentoo >>> Emerging (3 of 3) dev-libs/xapian-bindings-1.3.4::gentoo >>> Installing (2 of 3) app-text/xapian-omega-1.3.4::gentoo >>> Installing (3 of 3) dev-libs/xapian-bindings-1.3.4::gentoo >>> Jobs: 3 of 3 complete Load avg: 3.87, 2.72, 1.75 * Messages for package dev-libs/xapian-1.3.4-r2: * * Using sse2 * >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. It might help to deactivate perl USE flags - if you don't need the perl-bindings. We use ONLY the Perl bindings. :-) I have reproduced this in a minimal testing environment with most flags disabled. Building with USE=perl produces this error, and building with USE=-perl produces a different error. (In reply to Sam Jorna (wraeth) from comment #7) > I have reproduced this in a minimal testing environment with most flags > disabled. Building with USE=perl produces this error, and building with > USE=-perl produces a different error. can you give steps to reproduce from a clean stage3. the reason is i can't reproduce this at my end. looking at the error, i agree with Felix that this looks like a parallel build error. but the reporter says its not. (In reply to Anthony Basile from comment #8) > (In reply to Sam Jorna (wraeth) from comment #7) > > I have reproduced this in a minimal testing environment with most flags > > disabled. Building with USE=perl produces this error, and building with > > USE=-perl produces a different error. > > can you give steps to reproduce from a clean stage3. the reason is i can't > reproduce this at my end. looking at the error, i agree with Felix that > this looks like a parallel build error. but the reporter says its not. oh wait, my bad. i see what's going on. sorry for the noise. okay this should be fixed. please reopen if this is still a problem. |