Description of problem: The command "apxs -q INCLUDEDIR" returns "/usr/include/httpd" The result should be prefixed with "/opt/rh/httpd24/root" to work properly Version-Release number of selected component (if applicable): 2.4.12-4.el6.x86_64 How reproducible: apxs -q INCLUDEDIR Steps to Reproduce: 1. 2. 3. Actual results: /usr/include/httpd Expected results: /opt/rh/httpd24/root/usr/include/httpd Additional info: Got stuck on this when building Shibboleth from source, took me a couple of hours to nail it down
(In reply to Mattias Borell from comment #0) > Description of problem: > The command "apxs -q INCLUDEDIR" returns "/usr/include/httpd" > The result should be prefixed with "/opt/rh/httpd24/root" to work properly > > Version-Release number of selected component (if applicable): > 2.4.12-4.el6.x86_64 > > How reproducible: > apxs -q INCLUDEDIR > > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > /usr/include/httpd > > Expected results: > /opt/rh/httpd24/root/usr/include/httpd > > Additional info: > Got stuck on this when building Shibboleth from source, took me a couple of > hours to nail it down And before someone asks, I was using the right apxs: /opt/rh/httpd24/root/usr/bin/apxs
I don't see this with the current RHSCL packages for RHEL6 or 7, can you still reproduce? # rpm -q httpd24-httpd-devel httpd24-httpd-devel-2.4.12-4.el6.2.x86_64 # scl enable httpd24 'apxs -q INCLUDEDIR' /opt/rh/httpd24/root/usr/include/httpd
Ah, if you run apxs outside of the SCL environment it will fail like that, so long as RHEL httpd-devel and apr-devel are installed. # /opt/rh/httpd24/root/usr/bin/apxs -q INCLUDEDIR /usr/include/httpd This is actually expected behaviour; if you don't use the scl wrapper, most bets are off.
Yep, I had both the SCL httpd24 and the standard httpd environment installed. I thought calling the binary/script with an absolute path would be enough, but that seems to not be the case... :-) Thanks for the clarification!