My first attempt at this was a major change to how --with-pcre= now works on trunk, it is now a path to .../pcre[2]-config, .../bin/pcre[2]-config, (first it tries the {target}-pcre[2]-config for cross-compilation, and then the undecorated flavor.)
I did hack around providing either a full path including the script name, or only the config script name (e.g. --with-pcre=pcre-config to revert to a legacy pcre-8.x). That causes some extra hassle but seems like a good idea for these edge cases. In these cases, or where --with-pcre is simply not given, we actually walk the $PATH, and --with-pcre=PATH can actual be a traditional path list in place of default $PATH. So it seems --with-pcre=PATH is the right textual description for this specific case, and changing these without potentially providing a list of paths would be erroneous. I'd welcome any feedback and review of trunk's --with-pcre= detection. Bill On Wed, Nov 16, 2016 at 6:40 AM, William A Rowe Jr <wr...@rowe-clan.net> wrote: > Can we agree on a keyword/wording convention here for httpd-2.5-dev? > > --with-apr=PATH prefix for installed APR or the full path to > --with-pcre=PATH Use external PCRE library > --with-valgrind[=DIR] Enable code to reduce valgrind false positives > (optionally: set path to valgrind headers) > --with-distcache=PATH Distcache installation directory > --with-z=PATH use a specific zlib library > --with-libxml2=DIR Specify location of libxml2 > --with-brotli=PATH Brotli installation directory > --with-lua=PATH Path to the Lua 5.2/5.1 prefix > --with-serf=PATH Serf client library > --with-ssl=PATH OpenSSL installation directory > --with-nghttp2=PATH nghttp2 installation directory > directory. > > Contrast to apr-2.0 and the autoconf keywords and text; > > Installation directories: > --prefix=PREFIX install architecture-independent files in PREFIX > [/usr/local/apr] > --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX > [PREFIX] > > By default, `make install' will install all the files in > `/usr/local/apr/bin', `/usr/local/apr/lib' etc. You can specify > an installation prefix other than `/usr/local/apr' using `--prefix', > for instance `--prefix=$HOME'. > > For better control, use the options below. > > Fine tuning of the installation directories: > --bindir=DIR user executables [EPREFIX/bin] > --sbindir=DIR system admin executables [EPREFIX/sbin] > --libexecdir=DIR program executables [EPREFIX/libexec] > --sysconfdir=DIR read-only single-machine data [PREFIX/etc] > --sharedstatedir=DIR modifiable architecture-independent data > [PREFIX/com] > --localstatedir=DIR modifiable single-machine data [PREFIX/var] > --libdir=DIR object code libraries [EPREFIX/lib] > --includedir=DIR C header files [PREFIX/include] > --oldincludedir=DIR C header files for non-gcc [/usr/include] > --datarootdir=DIR read-only arch.-independent data root > [PREFIX/share] > --datadir=DIR read-only architecture-independent data > [DATAROOTDIR] > --infodir=DIR info documentation [DATAROOTDIR/info] > --localedir=DIR locale-dependent data [DATAROOTDIR/locale] > --mandir=DIR man documentation [DATAROOTDIR/man] > --docdir=DIR documentation root [DATAROOTDIR/doc/PACKAGE] > --htmldir=DIR html documentation [DOCDIR] > --dvidir=DIR dvi documentation [DOCDIR] > --pdfdir=DIR pdf documentation [DOCDIR] > --psdir=DIR ps documentation [DOCDIR] > --with-sysroot=DIR Search for dependent libraries within DIR > --with-installbuilddir=DIR location to store APR build files (defaults > to '${datadir}/build') > --with-efence[=DIR] path to Electric Fence installation > --with-valgrind[=DIR] Enable code to teach valgrind about apr pools > (optionally: set path to valgrind headers) > --with-egd[=DIR] use EGD-compatible socket > --with-openssl=DIR specify location of OpenSSL > --with-nss=DIR specify location of NSS > --with-commoncrypto=DIR specify location of CommonCrypto > --with-gdbm=DIR enable GDBM support > --with-ndbm=PATH Find the NDBM header and library in > `PATH/include' > and `PATH/lib'. If PATH is of the form > `HEADER:LIB', > library in LIB. If you omit the `=PATH' part > --with-berkeley-db=PATH Find the Berkeley DB header and library in > `PATH/include' and `PATH/lib'. If PATH is of the > `=PATH' part completely, the configure script > will > --with-pgsql=DIR specify PostgreSQL location > --with-mysql=DIR enable MySQL DBD driver > --with-sqlite3=DIR enable sqlite3 DBD driver > --with-sqlite2=DIR enable sqlite2 DBD driver > --with-oracle-include=DIR > path to Oracle include files > --with-oracle=DIR enable Oracle DBD driver; giving ORACLE_HOME as > DIR > --with-odbc=DIR specify ODBC location > --with-libxml2=DIR specify libxml2 location > --with-expat=DIR specify Expat location > --with-iconv=DIR path to iconv installation > >