Re: [gentoo-user] Re: fdm fails during ./configure: libssl not found
On Thu, 27 Jun 2019 00:47:20 + (UTC), Bryant Morrow wrote: > Aha! Thank you for that, I didn't see those bug reports in my Google > searches. Now I know to check the bugtracking projects directly. > > I've set up a local portage repo with a modified fdm-1.9 ebuild using > the patch given in that link, and fdm builds without issue. Thank you! If all you need to do is apply a patch between unpack and configure, you can drop the patch file into /etc/portage/patches/$CAT/$PKG/ and emerge will apply it with no need for a modified ebuild. You can add the version to $PKG to apply it to that version only. -- Neil Bothwick Obscenity is the crutch of inarticulate motherfuckers. pgpUFSyHbCCqk.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: fdm fails during ./configure: libssl not found
Aha! Thank you for that, I didn't see those bug reports in my Google searches. Now I know to check the bugtracking projects directly. I've set up a local portage repo with a modified fdm-1.9 ebuild using the patch given in that link, and fdm builds without issue. Thank you! On Tue, 25 Jun 2019 10:04:19 +0100, (Nuno Silva) wrote: > On 2019-06-24, Bryant Morrow wrote: > > > --- > > > > fdm-1.9 consistently fails to build, with configure citing a lack of > > libssl as the reason. I have openssl installed, and > > /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists. > > I've looked for similar problems online, with no luck. It originally > > seemed to be related to a broken version of openssl being unmasked > > along with the use of ~amd64 in ACCEPT_KEYWORDS, but resolving that > > made no difference. It seems to me that fdm's config scripts simply > > can't find libssl, but they appear to be looking in all of the correct > > places. I had it installed and working in the past, but it was removed > > due to a stupid (on my part) accident with emerge --depclean and now > > fails to reinstall. > > > > Output of emerge -pqv 'net-mail/fdm-1.9::gentoo': > > http://dpaste.com/2B1YBPZ //emerge -pqv > > > > Output of emerge --info 'net-mail/fdm-1.9::gentoo': > > http://dpaste.com/0D1PK0E //emerge --info > > > > Contents of build.log: http://dpaste.com/1CFZF87 //build.log > > > > Contents of portage environment file: http://dpaste.com/2XJD461 > > //environment > > This looks like bug 677484 - the problem would indeed be the way this > config script tries to detect libssl. > > I don't use fdm, but from what I read in the bug report, I suppose you > could try downgrading openssl to 1.0.*, or change the fdm ebuild to > apply the patch from comment 9. > > https://bugs.gentoo.org/show_bug.cgi?id=677484 > > -- > Nuno Silva
[gentoo-user] Re: fdm fails during ./configure: libssl not found
On 2019-06-24, Bryant Morrow wrote: > --- > > fdm-1.9 consistently fails to build, with configure citing a lack of > libssl as the reason. I have openssl installed, and > /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists. > I've looked for similar problems online, with no luck. It originally > seemed to be related to a broken version of openssl being unmasked > along with the use of ~amd64 in ACCEPT_KEYWORDS, but resolving that > made no difference. It seems to me that fdm's config scripts simply > can't find libssl, but they appear to be looking in all of the correct > places. I had it installed and working in the past, but it was removed > due to a stupid (on my part) accident with emerge --depclean and now > fails to reinstall. > > Output of emerge -pqv 'net-mail/fdm-1.9::gentoo': > http://dpaste.com/2B1YBPZ //emerge -pqv > > Output of emerge --info 'net-mail/fdm-1.9::gentoo': > http://dpaste.com/0D1PK0E //emerge --info > > Contents of build.log: http://dpaste.com/1CFZF87 //build.log > > Contents of portage environment file: http://dpaste.com/2XJD461 > //environment This looks like bug 677484 - the problem would indeed be the way this config script tries to detect libssl. I don't use fdm, but from what I read in the bug report, I suppose you could try downgrading openssl to 1.0.*, or change the fdm ebuild to apply the patch from comment 9. https://bugs.gentoo.org/show_bug.cgi?id=677484 -- Nuno Silva
