Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#57648 - [libmcrypt] Add pkg-config support

Attached to Project: Arch Linux
Opened by Mark (neolith2099) - Monday, 26 February 2018, 16:08 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 27 February 2018, 01:35 GMT
Task Type Feature Request
Category Packages: Extra
Status Assigned
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Package libmcrypt version 2.5.8 is missing a pkg-config file. Adding the attached file as part of the package will add support for it and make cmake find the library much easier using the pkg-config module.

Additional info:
The attached document needs to be installed in /usr/lib/pkgconfig

Steps to reproduce:
Building programs using cmake offers no trivial way of finding this library. Adding this pkg-config file makes using cmake much simpler.
This task depends upon

Comment by Mark (neolith2099) - Monday, 26 February 2018, 16:11 GMT

Name: mcrypt
Description: A library which provides a uniform interface to several symmetric encryption algorithms
Version: 2.5.8
Libs: -L${libdir} -lmcrypt
Cflags: -I${includedir}
Comment by Jan de Groot (JGC) - Monday, 26 February 2018, 19:56 GMT
I don't see use for this. Yes it makes detection easier on Arch, but when you move your code to Fedora or Debian there's no libmcrypt.pc and detection will fail.

These things should be filed upstream.
Comment by Doug Newgard (Scimmia) - Tuesday, 27 February 2018, 01:31 GMT
This appears to be old, dead software that's only used by other old, dead software. Doesn't seem worth it.
Comment by Eli Schwartz (eschwartz) - Thursday, 01 March 2018, 15:40 GMT
e.g. mcrypt support was finally dropped from PHP, for reasons along the line of

General consensus regarding mcrypt is that if you use it in new code, you're doing it extremely, horribly wrong. If you're maintaining old code, your build system already added whatever workarounds you need to find it, but you should really, really, really consider migrating to some actually safe crypto library (of which there are many far better ones).

If you want pkg-config files added to to mcrypt in a way that offers any guarantee whatsoever of finding it on two or more distros, you are welcome to fork the project and start updating it for the first time in a decade.