|Summary:||evp.h not found after upgrading to dev-libs/openssl-0.9.8o-r1|
|Product:||Gentoo Linux||Reporter:||Ronny Perinke <brainkiller_01>|
|Component:||New packages||Assignee:||Gentoo Linux bug wranglers <bug-wranglers>|
|Package list:||Runtime testing required:||---|
Description Ronny Perinke 2010-07-26 22:31:20 UTC
I upgraded from openssl-0.9.8o to dev-libs/openssl-0.9.8o-r1 today along with php-5.3.3. Emerging of php-5.3.3 failed because usr/include/openssl/evp.h was not found. Uninstalling openssl-0.9.8o-1 and reinstalling openssl-0.9.8o resolved the problem. Reproducible: Always Steps to Reproduce: 1. install dev-libs/openssl-0.9.8o-r1 2. emerge php-5.3.3 3. Actual Results: emerge failes with configure: error: Cannot find OpenSSL's <evp.h> openssl was unmasked using <dev-libs/openssl-1.0.0 ~amd64 emerged using sephiroth-pc ~ # emerge -uvpDN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS ] dev-libs/openssl-0.9.8o-r1 [0.9.8o] USE="(sse2) zlib -bindist -gmp -kerberos -test" 0 kB [uninstall ] dev-libs/openssl-0.9.8o USE="(sse2) zlib -bindist -gmp -kerberos -test" [blocks b ] =dev-libs/openssl-0.9.8*:0 ("=dev-libs/openssl-0.9.8*:0" is blocking dev-libs/openssl-0.9.8o-r1)
Comment 1 Samuli Suominen (RETIRED) 2010-07-26 22:59:59 UTC
dont unmask openssl-0.9.8o-r1 then, it's only for binary packages... supposed to be co-installed with openssl-1.0.0a.
Comment 2 Ronny Perinke 2010-07-26 23:52:48 UTC
(In reply to comment #1) > dont unmask openssl-0.9.8o-r1 then, it's only for binary packages... supposed > to be co-installed with openssl-1.0.0a. > how about masking it with something else than ~arch so that it won't get pulled in by accident?
Comment 3 Samuli Suominen (RETIRED) 2010-07-27 08:01:04 UTC
(In reply to comment #2) > (In reply to comment #1) > > dont unmask openssl-0.9.8o-r1 then, it's only for binary packages... supposed > > to be co-installed with openssl-1.0.0a. > > > > how about masking it with something else than ~arch so that it won't get pulled > in by accident? > nxclient and some other binary-only ebuilds need it in ~arch, so it has to be masked by ~arch for them. there's really no problem unless making the mistake of unmasking it in /etc/portage/package.keywords without getting 1.0.0a too.