| Summary: | dev-util/gambas-2.8.2 lock-up my computer... | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jiri Tyr <jiri.tyr> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | bberberov+gentoo, darkside |
| Priority: | High | ||
| Version: | 2008.0 | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jiri Tyr
2008-09-23 15:11:46 UTC
odd. Boian, have you seen anything like this? Thanks for CCing me. No I have not seen this at all. gambas is slot-fixed (if that is the correct term) to qt-3. Upgrading to QT 4.4.2 should not affect anything at all. Upgrading to KDE 3.5.10 might have affected something in this component, gb.qt.kde.html. Try un-setting the kde USE flag for this package and re-emerge to make sure everything else works. I still have 3.5.9 so I cannot test this myself if that is the case. Sorry. I will look at the emerge --info in more detail and try to test-build gambas again. Maybe it is something with the KDE, because I have upgraded to KDE 4.1.1 from the kde-testing overlay. It probably is a KDE issue. kdelibs is not slot-fixed in the ebuild like qt is. Are you running both kde-3 and kde-4, or just kde-4? I'm running KDE4, but I have also installed the kdelibs-3.5.9-r4 for backwards compatibility. Could you grep the build.log after an emerge/ebuild and post the results of: # grep -n5 KDE\ 3 /var/tmp/portage/dev-util/gambas-2.8.2/temp/build.log You can interrupt before the compiling starts so it does not lock up. I am only interested in the configure results. (In reply to comment #6) > Could you grep the build.log after an emerge/ebuild and post the results of: > > # grep -n5 KDE\ 3 /var/tmp/portage/dev-util/gambas-2.8.2/temp/build.log > > You can interrupt before the compiling starts so it does not lock up. I am > only interested in the configure results. I tried to compile gambas-2.8.2 again and now, it went through all the compilation and installation process! The reason could be, that I added USE="kdeprefix" to the KDE-4 installation. So it looks like something is wrong when I want to install KDE-4 into /usr/ and not into /usr/kde/4.1/. I hope it helps to solve the problem. It may be a PATH issue related to slotting of KDE. I will try to make a patch and post it here. OK, a newer ebuild is posted here: http://bazaar.launchpad.net/%7Ebberberov/%2Bjunk/dev-overlay/files/2?file_id=gambas-20081001162032-mij414teo0yk8yb0-15 This should work with USE="kdeprefix" or without it, but I cannot test it since I do not have KDE-4. By the way, I think the ebuild in the tree is broken now since it was bumped to EAPI-2 without a src_configure function. (In reply to comment #9) > > This should work with USE="kdeprefix" or without it, but I cannot test it since > I do not have KDE-4. By the way, I think the ebuild in the tree is broken now > since it was bumped to EAPI-2 without a src_configure function. > Switched to src_configure. I just realized that my link is revision-specific. :( http://bazaar.launchpad.net/%7Ebberberov/%2Bjunk/dev-overlay/files/3?file_id=gambas-20081001162032-mij414teo0yk8yb0-15 Are there any problems with the new ebuild? (In reply to comment #12) > Are there any problems with the new ebuild? It seems to be fixed now. Thank you for your help! |
