I have 2 side projects I'd like to complete at work:
- Enable wiki users to authenticate against the corporate Active Directory (LDAP) server.
- Setup a code review tool for my dev team.
Here's the problem. The Linux server where the tools will reside has a version of PHP that doesn't have LDAP compiled in and the Apache Server is missing mod_proxy_html for some reason.
If I were running on Windows, I would download the relevant modules, drop them in the ext or modules directory, bounce the server then go on about my business. With Linux, however, it seems like my only option is to recompile PHP (for the LDAP libraries) or to compile the mod_proxy_html module and all of its dependencies myself.
Now, I know what you're probably thinking: "Why don't you just use a package manager to install the modules?" That's a fair question.
- The server can only access the public internet via a proxy with a list of whitelisted
sites. (It's an intranet server after all.)
- The Apache and PHP that are running on the server are from a LAMP package. They aren't controlled by YUM, or RPM, or any other 3-letter acronym.
I was able to compile PHP from scratch, but not without a good bit of Yak Shaving. I had to download and compile 4 or 5 dependencies before I could get PHP compiled with the LDAP libraries, and even then,
make test basically said, "Hey buddy. I know you went through a lot of trouble to compile this, but it's looking kinda janky. Good luck though!"
So my question is, why is this necessary? Why can't I just download a precompiled (statically compiled?) version of the libraries/modules that I want, put them in a place Apache and PHP can see them, restart the Apache server and go on my merry way.