Summary: | dev-lang/fpc-2.0.4 wont emerge - missing arugument to -exec attempted to emerge three times an dgot the same error each time | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | dandimmitt |
Component: | New packages | Assignee: | Maintainers for Miscelleneous Language Packages [OBSOLETE] <lang-misc+disabled> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | exa.exa, jprofesorek, ondrew, zombi |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
dandimmitt
2006-09-21 12:38:39 UTC
It probably means that your version of findutils is outdated. Could you retry with the current stable version (4.3.0, I believe)? emerged the new findutils and was able to download fpc2.0.4. thanks *** Bug 149411 has been marked as a duplicate of this bug. *** *** Bug 151062 has been marked as a duplicate of this bug. *** *** Bug 157853 has been marked as a duplicate of this bug. *** Probably the ebuild should contains the necessary findutils dependency. This caused some wasted hours, trying to figuring out, what happened in a new gentoo installation. Or the ebuild should be modified to contain the following command instead of the original: find "${S}" -name Makefile -exec sed -i -e 's/ -Xs / /g' \{\} \; || die Generally speaking, system dependencies are to be avoided, and findutils-4.3.0 has been marked stable about five months ago. But if people are still running into this, I suppose it wouldn't really hurt either. Done, although as a blocker against older versions rather than a dependency on newer versions, so that systems using non-GNU find won't get it pulled in unnecessarily. I've runned into in a fresh 2006.1 install on an AMD64 box. Probably i've missed to upgrade that package, because neither X, nor Gnome, nor any other package doesn't depends on findutils 4.3. And from the error message there wasn't obvious, that the solution is to upgrade the system. So I manually modified the ebuild. I think it's the better solution - however, I don't know what the precise difference between find "${S}" -name Makefile -exec sed -i -e 's/ -Xs / /g' \{\} \; || die and find "${S}" -name Makefile -exec sed -i -e 's/ -Xs / /g' {} + || die and why it's preferred. BR, Zsombor Ah, okay, a fresh install should now no longer give confusing error messages. As for the difference, find ... -exec ... {} \; is roughly equivalent to for x in `find ... -print`; do ... $x ; done while find ... -exec ... {} + is roughly equivalent to find ... -print | xargs ... The efficiency advantage of the second form is probably small enough to ignore, but the only advantage the first form has in this case is backwards compatibility, which is not a good reason for me to change it, unless others decide that these older versions will be actively supported for whatever reason. |