This can be reproduced by: - Build dev-libs/openssl w/ USE=sslv3 - Build net-misc/curl - Rebuild dev-libs/openssl w/o USE=sslv3 From LibreOffice: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libcurl.so.4: undefined reference to `SSLv3_client_method@OPENSSL_1_1_0' collect2: error: ld returned 1 exit status make[1]: *** [/usr/src/portage/app-office/libreoffice-6.4.6.2-r2/work/libreoffice-6.4.6.2/svx/Executable_gengal.mk:20: /usr/src/portage/app-office/libreoffice-6.4.6.2-r2/work/libreoffice-6.4.6.2/instdir/program/gengal.bin] Error 1 /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libcurl.so.4: undefined reference to `SSLv3_client_method@OPENSSL_1_1_0' collect2: error: ld returned 1 exit status make[1]: *** [/usr/src/portage/app-office/libreoffice-6.4.6.2-r2/work/libreoffice-6.4.6.2/solenv/gbuild/LinkTarget.mk:639: /usr/src/portage/app-office/libreoffice-6.4.6.2-r2/work/libreoffice-6.4.6.2/workdir/LinkTarget/Executable/canvasdemo] Error 1 From CMake: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libcurl.so: undefined reference to `SSLv3_client_method@OPENSSL_1_1_0' collect2: error: ld returned 1 exit status make[2]: *** [Source/CursesDialog/CMakeFiles/ccmake.dir/build.make:311: bin/ccmake] Error 1
This should be fixed in curl-7.74.0-r3.ebuild. Can you please check and close this bug if it works.
So your fix does this: -dev-libs/openssl:0=[static-libs?,${MULTILIB_USEDEP}] +dev-libs/openssl:0=[sslv3,static-libs?,${MULTILIB_USEDEP}] But the right thing to do would be either: a) > IUSE=sslv3 > dev-libs/openssl:0=[sslv3=,static-libs?,${MULTILIB_USEDEP}] b) hard-disable sslv3 in the build system with b) probably the preferable solution.
(see also use flag description: sslv3: Support for the old/insecure SSLv3 protocol)
I'm going to revert this commit as it is the exact opposite of a fix -- it turns a fringe problem into a problem affecting all Gentoo users who will get the stupid Portage autounmask to enable sslv3 for them.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e357e57cc8971a965204eb97eef59518958c8d3 commit 0e357e57cc8971a965204eb97eef59518958c8d3 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2021-01-29 23:22:27 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2021-01-29 23:24:03 +0000 net-misc/curl: [QA] Revert "remove libressl, fix bugs #744934..." This does not fix the problem, this forcibly exposes all Gentoo users to it in the future. Reverts: 8b6375b9b783eb0d412f78bb45a50675591729fe Bug: https://bugs.gentoo.org/744934 Signed-off-by: Michał Górny <mgorny@gentoo.org> net-misc/curl/curl-7.74.0-r3.ebuild | 285 ------------------------------------ 1 file changed, 285 deletions(-)
> b) hard-disable sslv3 in the build system > > with b) probably the preferable solution. I'm not sure what you mean here.
(In reply to Anthony Basile from comment #6) > > > b) hard-disable sslv3 in the build system > > > > with b) probably the preferable solution. > > I'm not sure what you mean here. In speaking with mgorny, the idea is to disable sslv3 in configure.
I went with the USE flag to keep consistency across a persons system. Reopen if you feel there is still a problem.