| Summary: | kde-base/kdelibs-4.6.1-r1 fails to merge because 'giflib is missing'. but giflib actually exists [upgrading gcc to >=4.4.3 solves issue] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | shimi <gentoo-bugzilla> |
| Component: | New packages | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Full build log /var/tmp/portage/kde-base/kdelibs-4.6.1-r1/temp/build.log
/var/tmp/portage/kde-base/kdelibs-4.6.1-r1/work/kdelibs-4.6.1_build/CMakeFiles/CMakeError.log /var/tmp/portage/kde-base/kdelibs-4.6.1-r1/work/kdelibs-4.6.1_build/CMakeFiles/CMakeOutput.log |
||
|
Description
shimi
2011-03-07 15:27:00 UTC
Please run: "equery uses giflib" shimi@tux ~ $ equery uses giflib [ Searching for packages matching giflib... ] [ Colour Code : set unset ] [ Legend : Left column (U) - USE flags from make.conf ] [ : Right column (I) - USE flags packages was installed with ] [ Found these USE variables for media-libs/giflib-4.1.6-r1 ] U I + + X : Adds support for X11 - - rle : Build converters for RLE format (utah raster toolkit) Could you attach full build log ? Check also build dir for cmake log files. Created attachment 265091 [details]
Full build log /var/tmp/portage/kde-base/kdelibs-4.6.1-r1/temp/build.log
Created attachment 265093 [details]
/var/tmp/portage/kde-base/kdelibs-4.6.1-r1/work/kdelibs-4.6.1_build/CMakeFiles/CMakeError.log
Created attachment 265095 [details]
/var/tmp/portage/kde-base/kdelibs-4.6.1-r1/work/kdelibs-4.6.1_build/CMakeFiles/CMakeOutput.log
Well,as one of the errors is: cc1plus: error: unrecognized command line option "-Werror=return-type" and this doesn't seem to come from your C(XX)FLAGS, you probably need to switch to a more recent gcc than 4.1.2. I hope you're aware what this will mean for C++ apps ? And on that note: your glibc is quite old too, is this one of "I didn't update for awhile" bugs ? 9999 for libtool is an odd choice too. Actually I did have a newer gcc already installed... I was just not switched to it, it seems. # gcc-config 3 * Switching native-compiler to x86_64-pc-linux-gnu-4.4.3... Yes, I guess this is "another case" of using an old software. I guess they wouldn't be happening if the configure script (or better yet, Portage itself) - would check for the required version of one of its dependencies prior to the compile stage, and warn if it's not adequate... Granted, this may require another variable in ebuild files (i.e. MINIMAL_GCC_VERSION) or a patch to configure (or CMake equivalent...), but I think it's worth it. Anyways, it continued past the outlined problem, now that I've switched gcc. Leaving it open should you decide to have the ebuild check for active gcc version to help others in situations like that... Thanks! (In reply to comment #8) > Actually I did have a newer gcc already installed... I was just not switched to > it, it seems. > > # gcc-config 3 > * Switching native-compiler to x86_64-pc-linux-gnu-4.4.3... > > Yes, I guess this is "another case" of using an old software. I guess they > wouldn't be happening if the configure script (or better yet, Portage itself) - > would check for the required version of one of its dependencies prior to the > compile stage, and warn if it's not adequate... > > Granted, this may require another variable in ebuild files (i.e. > MINIMAL_GCC_VERSION) or a patch to configure (or CMake equivalent...), but I > think it's worth it. That's not quite how we do things around here. You really need to keep the system "moderately" recent to avoid building problems. At this point, I think we've concluded on another bug that we don't support anything older than GCC-4.3*. > Anyways, it continued past the outlined problem, now that I've switched gcc. Before you return reporting issues, you should know you need to build Qt and KDE using the same GCC version. So rebuild all of Qt and KDE. As you have such an old GCC, be warned that you may need to rebuild your kernel with the new GCC and reboot to it or things may start to fail in strange ways. > Leaving it open should you decide to have the ebuild check for active gcc > version to help others in situations like that... > > Thanks! The eclass now prohibits building >=kde-4.6 with gcc <=4.3. |
