When you don’t have a system wide pkgconfig/aclocal for example because it’s a shared server with a module loadable package system,
then typical symptom during the execution of ./configure
that certain macros are not found or reported to cause syntax error because they are not expanded.
Example for “Command not found”:
# configure script: 3890 as_fn_error $? "Your 'rm' program is bad, sorry." "$LINENO" 5 3891 fi 3892 fi 3893 3894 PKG_PROG_PKG_CONFIG 3895 3896 3897 if test "x$PY_PREFIX" = x; then :
Here the macro PKG_PROG_PKG_CONFIG, should have been resolved at this point to something else.
# execution output: ./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
Example for syntax error because not expanded:
# configure script: 17090 PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 4.3, have_qt=yes, have_qt=no)
This should have been expanded too to something like “… ($PKG_CONFIG –exists –print-errors “QtCore >= 4.3, QtNetwork >= 4.3″) … ”
# execution output: ./configure: line 17090: syntax error near unexpected token `QT,' ./configure: line 17090: ` PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 4.3, have_qt=yes, have_qt=no)'
Solution, as mentioned here:
export ACLOCAL_PATH=/app/vbuild/SLED11-x86_64/pkgconfig/0.25/share/aclocal/ # This is where the pkg.m4 can be found: ls -lah /app/vbuild/SLED11-x86_64/pkgconfig/0.25/share/aclocal/pkg.m4
Alternatively if further macros are missing then consider setting AL_OPTS, as suggested here: