On Thu, 2017-03-02 at 20:06 +0100, Lukas Fleischer wrote: > On Thu, 02 Mar 2017 at 07:05:44, Lukas Fleischer wrote: > > What is the plan for packages where upstream is dead or reluctant > > to > > migrate to OpenSSL 1.1.0 (see e.g. [1])? Are we going to ship a > > legacy > > openssl-compat (or libressl) package for a while? > > It seems like there already is an openssl-1.0 package [1]. This makes > everything much easier. Thanks. > > [1] https://www.archlinux.org/packages/?q=openssl-1.0
To use this package you need to set PKG_CONFIG_PATH=/usr/lib/openssl- 1.0/pkgconfig. If your package doesn't use PKG_CONFIG_PATH to look for openssl you'll have to manually add -I/usr/include/openssl-1.0 to CFLAGS and -L/usr/lib/openssl-1.0 to LDFLAGS. Also, make sure that your resulting package uses the correct library. You don't want to link to two different versions of OpenSSL. An example where this happens is ptlib/opal, Opal will happily compile against OpenSSL 1.1 while ptlib is compiled against 1.0 if no changes are made to opal.
