mod_ssl and pkg-config on AIX (Re: [Vote] httpd 2.2.23 release)

[Kaspar Brand]

On 27.08.2012 15:42, Michael Felt wrote:
> FYI: I get an error message from configure that I do not understand.
> 
> + ./configure
>                 --enable-layout=AIX
>                 --with-apr=/opt/bin/apr-1-config
>                 --with-apr-util=/opt/bin/apu-1-config
>                 --with-mpm=worker
>                 --enable-ssl
>                 --enable-mods-shared=all > build/aix/configure.out
> Package openssl was not found in the pkg-config search path.
> Perhaps you should add the directory containing `openssl.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'openssl' found

Does AIX come with a bundled version of OpenSSL (under /usr or similar)?

How does the configure output look like after the "checking whether to enable
mod_ssl..." line (up to "checking whether to enable 
mod_optional_hook_export...")?

With 2.2.x, configure will try pkg-config for figuring out the -l, -I and
-L flags - and fall back to "-lssl -lcrypto" if pkg-config fails for some
reason:

  if test "$ap_ssltk_type" = "openssl"; then
    if test "x$ap_ssltk_base" != "x" -a \
            -f "${ap_ssltk_base}/lib/pkgconfig/openssl.pc"; then
      dnl Ensure that the given path is used by pkg-config too, otherwise
      dnl the system openssl.pc might be picked up instead.
      
PKG_CONFIG_PATH="${ap_ssltk_base}/lib/pkgconfig${PKG_CONFIG_PATH+:}${PKG_CONFIG_PATH}"
      export PKG_CONFIG_PATH
    fi
    if test -n "$PKGCONFIG"; then
      ap_ssltk_libs="`$PKGCONFIG --libs-only-l openssl`"
      if test $? -eq 0; then
        pkglookup="`$PKGCONFIG --cflags-only-I openssl`"
        APR_ADDTO(CPPFLAGS, [$pkglookup])
        APR_ADDTO(INCLUDES, [$pkglookup])
        pkglookup="`$PKGCONFIG --libs-only-L --libs-only-other openssl`"
        APR_ADDTO(LDFLAGS, [$pkglookup])
      else
        ap_ssltk_libs="-lssl -lcrypto `$apr_config --libs`"
      fi
    else
      ap_ssltk_libs="-lssl -lcrypto `$apr_config --libs`"
    fi
  fi

> However, the packaging proceeds fine.

It's kind of expected behavior, yes. Replacing

      ap_ssltk_libs="`$PKGCONFIG --libs-only-l openssl`"

by

      ap_ssltk_libs="`$PKGCONFIG --libs-only-l openssl 2>/dev/null`"

would suppress the (perhaps confusing) message.

Kaspar