| 1 |
--- |
| 2 |
|
| 3 |
fdm-1.9 consistently fails to build, with configure citing a lack of libssl as the reason. I have |
| 4 |
openssl installed, and /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists. |
| 5 |
I've looked for similar problems online, with no luck. It originally seemed to be related to a |
| 6 |
broken version of openssl being unmasked along with the use of ~amd64 in ACCEPT_KEYWORDS, but |
| 7 |
resolving that made no difference. It seems to me that fdm's config scripts simply can't find |
| 8 |
libssl, but they appear to be looking in all of the correct places. I had it installed and working |
| 9 |
in the past, but it was removed due to a stupid (on my part) accident with emerge --depclean and now |
| 10 |
fails to reinstall. |
| 11 |
|
| 12 |
Output of emerge -pqv 'net-mail/fdm-1.9::gentoo': |
| 13 |
http://dpaste.com/2B1YBPZ //emerge -pqv |
| 14 |
|
| 15 |
Output of emerge --info 'net-mail/fdm-1.9::gentoo': |
| 16 |
http://dpaste.com/0D1PK0E //emerge --info |
| 17 |
|
| 18 |
Contents of build.log: |
| 19 |
http://dpaste.com/1CFZF87 //build.log |
| 20 |
|
| 21 |
Contents of portage environment file: |
| 22 |
http://dpaste.com/2XJD461 //environment |
Archives