Bug 341511 – dev-util/cmake-2.8.1-r2 misses dependency on openssl:0.9.8

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Alexander Bezrukov 2010-10-17 20:57:32 UTC]

Ebuild for cmake doesn't list dependency for openssl:0.9.8. This leads to a build failure (see the actual results section).


Reproducible: Always

Steps to Reproduce:
1. Make sure openssl:0.9.8 is not installed in the system
2. emerge cmake
Actual Results:  
../bin/ctest: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
make[2]: *** [Docs/ctest.txt] Error 127
make[1]: *** [Utilities/CMakeFiles/documentation.dir/all] Error 2
make: *** [all] Error 2
 * ERROR: dev-util/cmake-2.8.1-r2 failed:
 *   Make failed!
 * 
 * Call stack:
 *     ebuild.sh, line   54:  Called src_compile
 *   environment, line 3340:  Called cmake-utils_src_compile
 *   environment, line  860:  Called _execute_optionaly 'src_compile'
 *   environment, line  326:  Called enable_cmake-utils_src_compile
 *   environment, line 1360:  Called cmake-utils_src_make
 *   environment, line  879:  Called die
 * The specific snippet of code:
 *           emake "$@" || die "Make failed!";
 * 
 * If you need support, post the output of 'emerge --info =dev-util/cmake-2.8.1-r2',
 * the complete build log and the output of 'emerge -pqv =dev-util/cmake-2.8.1-r2'.
 * The complete build log is located at '/tmp/portage/dev-util/cmake-2.8.1-r2/temp/build.log'.
 * The ebuild environment file is located at '/tmp/portage/dev-util/cmake-2.8.1-r2/temp/environment'.
 * S: '/tmp/portage/dev-util/cmake-2.8.1-r2/work/cmake-2.8.1'


Expected Results:  
cmake is built ok.

[Comment 1 Alexander Bezrukov 2010-10-17 21:00:02 UTC]

Created attachment 251063 [details]
emerge --info

[Comment 2 Jeroen Roovers (RETIRED) 2010-10-17 23:32:46 UTC]

Did you run revdep-rebuild after upgrading openssl?

[Comment 3 Alexander Bezrukov 2010-10-17 23:41:32 UTC]

(In reply to comment #2)
> Did you run revdep-rebuild after upgrading openssl?
> 

Jeroen, yes, I did run revdep-rebuild after upgrading openssl. Then I checked that openssl:0.9.8 is not a dependency on my system, according to portage; so I unmerged it. Whence is the problem. But you have no reason to assume that my system has openssl (whatever slot) at all, right?

[Comment 4 Jeroen Roovers (RETIRED) 2010-10-18 22:34:57 UTC]

Please attach the entire build log.

[Comment 5 Alexander Bezrukov 2010-10-19 12:39:52 UTC]

(In reply to comment #4)
> Please attach the entire build log.

Jeroen, sorry, I couldn't reproduce this anymore: now the package is being built with no problem and is linking against openssl-1.0.0a-r3 (indirectly, through libcurl). I didn't have time to really look into what is happening when reported the bug and now I am trying to understand how this could happen and the only my idea is that somehow revdep-rebuild missed the broken linking.

Interestignly, that I hit this problem on 2 completely different machines: x86 and amd64, with very different sets of installed packages. And now I can't reproduce this on neither one. I have a 'emerge --sync' cronjob on both but I am not going to claim that the reason is some change in the portage tree (in particular, the ebuild for cmake doesn't seem changed).

I am going to close this bug, at least until a moment when I can provide more information.