| Summary: | x11-libs/qt-core: pkg-config reports moc path as "/usr/.var/tmp/portage/x11-libs/qt-core-4.4.2/work/qt-x11-opensource-src-4.4.2/bin/moc" (breaks x11-misc/google-gadgets compilation) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | DarkNRG <DarkNRG> |
| Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | voyageur |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info --verbose
Log of "emerge -1 qt-core" |
||
Could you post the output of emerge --info --verbose please? Created attachment 167003 [details]
emerge --info --verbose
New maintainer, reassigning. What's the output of `pkg-config --variable=moc_location QtCore` ? This will be the path used to find moc, and should return /usr/bin Also, I've just added google-gadgets-0.10.3 to portage, it has many bug fixes from upstream changelog. Can be worth a shot The problem stays the same with the new version 0.10.3, but the output of pkg-config is "/usr/.var/tmp/portage/x11-libs/qt-core-4.4.2/work/qt-x11-opensource-src-4.4.2/bin/moc" so I think there may be a problem with qt-core (however this is the only application which could not find moc). CC'in qt as this looks like a problem in qt-core, have you already tried to remerge that package by the way? Created attachment 174985 [details]
Log of "emerge -1 qt-core"
Yes, I've remerged it already, but the problem stays the same, I've appended a log of the emerge process.
Reassigning I dont see how this is related to qt-core package.I cant reproduce this issue with the latest google-gadgets in portage ( I am using qt-core-4.4.2 ). Maybe there is something wrong with your path? --------------- google-gadgets-for-linux-0.10.5 # pkg-config --variable=moc_location QtCore /usr/bin/moc ------------- This is what I get from my system. So I dont think it is a common issue but a user specific :) (In reply to comment #10) > --------------- > google-gadgets-for-linux-0.10.5 # pkg-config --variable=moc_location QtCore > /usr/bin/moc > ------------- > > This is what I get from my system. So I dont think it is a common issue but a > user specific :) > It's the same path for me now: /usr/bin/moc I still don't know what went wrong, but I guess it was a user-specific configuration issue. Thanks for your help, I think this can be closed now :) Yep :). Lets close it as invalid :) |
x11-misc/google-gadgets searches for moc in the portage temp dir instead /usr/bin: /usr/.var/tmp/portage/x11-libs/qt-core-4.4.2/work/qt-x11-opensource-src-4.4.2/bin/moc: Command not found After creating a symlink to the correct location google-gadgets could be compiled successfully. Reproducible: Always Steps to Reproduce: 1. emerge google-gadgets # fails 2. mkdir -p /usr/.var/tmp/portage/x11-libs/qt-core-4.4.2/work/qt-x11-opensource-src-4.4.2/bin 3. ln -s /usr/bin/moc /usr/.var/tmp/portage/x11-libs/qt-core-4.4.2/work/qt-x11-opensource-src-4.4.2/bin/moc 4. emerge google-gadgets # works now Actual Results: ... make[5]: Leaving directory `/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/work/google-gadgets-for-linux-0.10.2/ggadget/gtk/tests' make[4]: Leaving directory `/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/work/google-gadgets-for-linux-0.10.2/ggadget/gtk' Making all in qt make[4]: Entering directory `/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/work/google-gadgets-for-linux-0.10.2/ggadget/qt' /usr/.var/tmp/portage/x11-libs/qt-core-4.4.2/work/qt-x11-opensource-src-4.4.2/bin/moc qt_main_loop.h -o qt_main_loop.moc make[4]: /usr/.var/tmp/portage/x11-libs/qt-core-4.4.2/work/qt-x11-opensource-src-4.4.2/bin/moc: Command not found make[4]: *** [qt_main_loop.moc] Error 127 make[4]: Leaving directory `/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/work/google-gadgets-for-linux-0.10.2/ggadget/qt' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/work/google-gadgets-for-linux-0.10.2/ggadget' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/work/google-gadgets-for-linux-0.10.2/ggadget' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/work/google-gadgets-for-linux-0.10.2' make: *** [all] Error 2 * * ERROR: x11-misc/google-gadgets-0.10.2-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2724: Called default_src_compile * ebuild.sh, line 1479: Called _eapi2_src_compile * ebuild.sh, line 641: Called die * The specific snippet of code: * emake || die "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/temp/build.log'. * The ebuild environment file is located at '/usr/.var/tmp/portage/x11-misc/google-gadgets-0.10.2-r2/temp/environment'. * >>> Failed to emerge x11-misc/google-gadgets-0.10.2-r2, Log file: Expected Results: x11-misc/google-gadgets-0.10.2-r2 merged