Show Navigation
Conversation
Notices
-
checking for OpenSSL version >= 0.9.8a... FAILED
configure: WARNING: OpenSSL version is too old
/usr/bin/openssl version
OpenSSL 1.0.2k-fips 26 Jan 2017
well, ok....
-
I always forget when I set up a new machine that I need to configure yum-cron, not just install it
-
instructions I was using didn't have openssl-devel as a dependency.
-
I guess strictly speaking, earlier I was configuring...and now I am compiling. Assuming this works, I will be running 'sudo make install'
-
If you're on Fedora, there used to be something (I think it was called "alien") that could take the installation source and turn it into an rpm, so that it would be updatable / removable with the package manager (yum). If I was going to be installing and removing a lot of things on Fedora, I would look into that or one of the Snap / Flatpack things, to keep from polluting the system hierarchy with odd applications, libraries, and odd versions of things that are already in the system's own package management space.
-
in this case, the issue was needing to install openssl-devel. That just wasn't in the instructions.
I guess the idea is to do all of the apache installs from source and then just change symlinks as necessary.
To me, all of these version changes are a perfect use case for docker containers but Vince is old school.
The reality is, I need to have a good understanding of all three "install" models if I am going to be replicated customer environments.
Strictly speaking, we are platform agnostic, but since my team only has CentOS developers, most of what we see is CentOS.
The AWS image I am using is one we sell to customers, so yeah, I need to know the ins and outs. We also have Azure images, but as far as I am aware, we don't have a testing space for Azure. I could always bring in one of the CentOS guys if I anticipate the issue is on the Azure side.
-
@musicman Oh, wow! I remember learning to install #Apache and #PHP from source 20+ years ago. Can't remember whether we actually compiled #MySQL or just extracted a precompiled tarball. On pre-RHEL #Red_Hat Linux and #FreeBSD.
.
Was fun, but upgrading could be tricky.
-
yeah, I won't be "upgrading". I will just be installing a new version beside the old version. Then, I point the symlink to the new version.
But I won't always be installing the new version. I might be installing really old versions. Officially, we support two versions back, but I have no idea what that means with Apache. We all of these applications going to short release cycles, it's anarchy. Apache HTTPD moves at glacial speed though, which causes its own problems. I'm pretty sure we just support anything in the 2.4.x tree, but I really don't know.