Description of problem:
There is a problem in the file /usr/include/httpd/apr_uri.h in Red Hat Linux 8/9
that causes a simple autoconf test for httpd/httpd.h not to work. The problem
is that the header file contains the line
which causes autoconf to die when testing for httpd.h There seem to be two fixes..
one change it to read like all other header files.
or put link /usr/include/httpd -> /etc/httpd/include
The second one is probably due to some hack in our configure.ac files.
Version-Release number of selected component (if applicable):
[smoogen@smoogen1 lama-2.0]$ rpm -qa | grep httpd | sort
# Process this file with autoconf to produce a configure script.
AC_INIT(mod_xxx, 1.0, firstname.lastname@example.org)
# Checks for header files.
AC_CHECK_HEADERS([arpa/inet.h fcntl.h netdb.h netinet/in.h stdlib.h string.h
sys/socket.h sys/time.h syslog.h unistd.h lber.h ldap.h httpd/httpd.h])
The supported interface for building modules is using:
apxs -c mod_foo.c
this will ensure that -I/usr/include/httpd and whatever else is used, as
necessary. If you don't want to use apxs -c, you should add:
-I`apxs -q INCLUDEDIR`
to CPPFLAGS before running the header checks, but this is not future-proof (and
will fail with the packages in Raw Hide).
If possible, is the <> link in that header file to force only the use of apxs?
It looks like there are several parts that need to be made ready for the project
and we had hoped to use autoconf to get those other parts going. It looked like
using a standard test on httpd/httpd.h would show that the proper items were
installed. however that test fails because of the <> entry on the header file.
No, it's not deliberately to force use of apxs. Your test will work if you add:
CPPFLAGS="$CPPFLAGS -I`$APXS -q INCLUDEDIR`"
before the AC_CHECK_HEADERS test, as I eluded to above, still with caveat.