Summary: | app-text/fbreader build fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tot-to <bugs.gentoo.org.list> |
Component: | Current packages | Assignee: | Alexey Shvetsov <alexxy> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kde |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
tot-to
2013-01-03 23:58:14 UTC
Created attachment 334270 [details]
build.log
Uh...wait, what? Why on earth is it trying to use the qt-core bin directory for moc instead of system moc? Please try removing /usr/tmp/portage/x11-libs/qt-core-4.8.4, then rebuild and see if that fixes things. (In reply to comment #2) > Uh...wait, what? Why on earth is it trying to use the qt-core bin directory > for moc instead of system moc? Please try removing > /usr/tmp/portage/x11-libs/qt-core-4.8.4, then rebuild and see if that fixes > things. after rm -fr /usr/tmp/portage do not resolve this issue. What's that /usr/tmp/portage ? Any chance it's a symlink to /var/tmp/portage (or the other way around) ? If so, this will likely effectively be a dupe of bug 401025. /usr/tmp is symbolik link to /var/tmp. It is just by default (was in stage3 tarball) Yes, but why is it using that by default instead of /var/tmp? (In reply to comment #6) > Yes, but why is it using that by default instead of /var/tmp? I don't know. At least I didn't do anything to reach such result. Indeed a dupe *** This bug has been marked as a duplicate of bug 401025 *** |