This repository was archived by the owner on Jan 21, 2019. It is now read-only.
This repository was archived by the owner on Jan 21, 2019. It is now read-only.
New configure script does not take into account compile flags #14
Description
With the new configure script macro, it is only possible to pass specific expat version with configure option:
./configure --with-expat=/custom/lib
If you export LDFLAGS, CPPFLAGS and CFLAGS but do not use --with-expat option, they are ignored and expat is only search searched in standard places: /usr and /usr/local
However, on OSX El Capitan with Homebrew expat is installed in /usr/local/opt/expat. It means the following configure for p1_xml works:
./configure --with-expat=/usr/local/opt/expat
...
checking for Expat XML Parser headers in /usr/local/opt/expat/include... found
checking for Expat XML Parser libraries... found
checking for Expat XML Parser... yes
checking if Expat XML Parser version is >= 2.0.0... yes
configure: creating ./config.status
config.status: creating vars.config
But not:
LDFLAGS="-L/usr/local/opt/expat/lib" CFLAGS="-I/usr/local/opt/expat/include" CPPFLAGS="-I/usr/local/opt/expat/include" ./configure
...
checking for Expat XML Parser... no
configure: error: Expat XML Parser was not found
However, when building xml library from ejabberd build chain, we can only rely on compile flags define in the environment. It means ejabberd cannot be built with OS X El Capitan and Homebrew as is due to this issue.
Relates to: #11