SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I really don't mess with ?.SlackBuild files but I was curious, did two changes to line 85 in RED
Code:
sed -i "s/#define OPENSSL_VERSION_NUMBER.*/\/* Use 0x1000205fL (1.1.0) below to avoid pointlessly breaking the ABI *\/\n#define OPENSSL_VERSION_NUMBER 0x1000205fL/g" /usr/include/openssl/opensslv.h || exit 1
I had done that, via ssh on a virtual 14.2 box. building the package the slackbuild installed libcrypto to /usr/lib64 instead of the tmp/pkg directory. This killed mc and ssh. I had a heck of a time recovering my virtual machine.
If you want to pursue this further, you can start at https://repology.org/metapackage/openssl/versions and look in the distros' build repositories (to the extent you can find them) to see what changes they applied versus 1.0.2l (to the extent you can understand them).
However, the likely conclusion is that you need to rebuild whatever applications you need that link to openssl, for the reasons mentioned in Patrick's SlackBuild. (You need to ponder the comment above the unconvincing change you tried -- the ABI very likely *has* changed. Just remove Patrick's fixup.) But many of those applications will need version bumps or patches to build (see e.g. Gentoo's note).
I did get this to build. In the end I removed the line that sets the version number because everything is broken. openssh libssh2, bind, httpd, sendmail, use your imagination.
I changed the config a little, I suppose it could be right.
The only other thing I changed was the make install line, it now is:
make install DESTDIR=$PKG1 || exit 1
openssh needs to be patched to work, I found a long patch on the arch linux site that worked.
Everything else is recompiling OK so far as long as I use the versions in current.
I'm running 14.2, but a lot of those won't accept the new openssl where the current versions do.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.