Summary: | dev-perl/Crypt-SMIME-0.190.0 with dev-libs/libressl-2.5.0 : SMIME.xs:12:25: fatal error: openssl/cms.h: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | kentnl, libressl |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://rt.cpan.org/Ticket/Display.html?id=119142 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 561854 | ||
Attachments: |
dev-perl:Crypt-SMIME-0.190.0:20161205-232505.log
emerge-history.txt environment etc.portage.tbz2 |
Description
Toralf Förster
![]() Created attachment 455194 [details]
dev-perl:Crypt-SMIME-0.190.0:20161205-232505.log
Created attachment 455196 [details]
emerge-history.txt
Created attachment 455198 [details]
environment
Created attachment 455200 [details]
etc.portage.tbz2
Sat Dec 3 19:40:25 2016 <<< dev-libs/openssl-1.0.2j Sat Dec 3 19:44:43 2016 >>> dev-libs/libressl-2.5.0 I'd say this is a libressl issue, I can't tell though. Upstream says they "need" libcrypto > 0.9.9 https://metacpan.org/source/MIKAGE/Crypt-SMIME-0.19/Makefile.PL#L66 And that cms.h is a new hard requirement: https://metacpan.org/diff/file?target=MIKAGE%2FCrypt-SMIME-0.19%2F&source=MIKAGE%2FCrypt-SMIME-0.18#SMIME.xs https://metacpan.org/source/MIKAGE/Crypt-SMIME-0.19//Changes#L4-9 libressl says it has libcrypto 2.5.0 > checking for libcrypto... 2.5.0 > checking for LIBCRYPTO_CFLAGS... > checking for LIBCRYPTO_LIBS... -lcrypto Going to need libressl's teams advice on how to proceed here. Though at present I think the only solution is: 1. Tell upstream they've broken libressl compat 2. Remove libressl fallback from the ebuild Which I doubt libressl team want. Could you try with a lower version of libressl? Looks like CMS support was removed in 2.5, so any version before 2.5 *should* work. If you can confirm that, I'll update the ebuild with a <= dep. (In reply to Kent Fredric (IRC: kent\n) from comment #6) confirmed @libressl team, this is now in your court really. Upstream say they can't function with libressl What are we supposed to do here? Please indicate that this bug blocks https://bugs.gentoo.org/561854 Considering CMS, this patch may be a clue: https://github.com/sbabic/swupdate/commit/fc99715609c593cd6e395a42c684a5ca610d9c78 but it needs further investigation. LibreSSL now supports CMS (since 3.1.0). Builds successfully for me. |