| Summary: | dev-perl/PerlQt-3.009_beta1 : endless loop | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Wegner <gentoo-bugs> |
| Component: | Current packages | Assignee: | Caleb Tennis (RETIRED) <caleb> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | perl |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Emerge log of last try | ||
|
Description
Martin Wegner
2005-07-25 05:07:14 UTC
*shrug*. Can you rm -rf /var/tmp/portage/PerlQt-3.009_beta1 and try again? Did not help unfortunately. Isn't this directory auto-cleaned when remerging the package? I just remembered that portage does store log files of merges: -rw-r--r-- 1 root portage 83M Jul 25 13:45 /var/log/portage/6499-PerlQt-3.009_beta1.log -rw-r--r-- 1 root portage 113M Jul 25 14:03 /var/log/portage/6503-PerlQt-3.009_beta1.log This proves the infinite loop. Now I was able to find the entry point: It's within configure. See next attachment. Created attachment 64295 [details]
Emerge log of last try
This is the log file of portage during the last try to emerge this package.
caleb - is that output related to kde-config? On my system: checking if smoke should be compiled... yes checking if PerlQt should be compiled... yes checking if PerlKDE should be compiled... no checking if puic should be compiled... yes configure: creating ./config.status config.status: creating PerlQt/Makefile.PL Make that: hecking for KDE or an Install directory... configure: WARNING: in the prefix, you've chosen, are no KDE headers installed. configure: WARNING: in the prefix, you've chosen, are no KDE libraries installed. will use /var/tmp/portage/PerlQt-3.009_beta1/image/usr checking for SmokeQt... no checking for SmokeKDE... no checking for X... libraries /usr/lib, headers . checking for gethostbyname... yes checking for connect... (cached) yes ch My 'hunch' here is that we should make this ebuild depend on kde-base/smoke and use that particular smoke library, which will also make it dependant on kde 3.4. Anyone have any objections to this? I haven't had any responses at the kde-bindings email list on making this build against Qt only. alternatively, we can do some trickery in ebuild to use the internal libsmoke, but would have to put some blockers on kde-base/smoke. no objections here. hard imaginging qt without kde :) I commited a beta2 ebuild with some changes. This should work better, but it may force you to upgrade some packages in the the process. Let's keep our fingers crossed that it works. I can confirm the bug, and that after installing smoke and removing --enable-smoke from the ebuild (btw this is to build smoke, even if it is there), I can install it successfully. Probably it is simply a bug in the makefile, because even after that there is a line showing after checking for SmokeQt... yes checking for SmokeKDE... no ./configure: line 31326: no: command not found the beta2 is still not in the portage so i could not tell if it works. Just for information the bug is not x86 specific, I have the same on AMD64 I think this is fixed in beta2, please reopen if not. |
