[emboss-dev] CVS checkout generates broken configure script...
James Abbott
j.abbott at imperial.ac.uk
Wed Dec 8 12:05:58 UTC 2010
Hello,
I'm trying to build a clean CVS checkout of the emboss code, but the
configure script generated by autoconf contains a syntax error:
checking for HPDF_New in -lhpdf... yes
PDF support found
checking whether to look for gsoap support... no
checking whether to look for axis2c support... ./configure: line 13496:
syntax error near unexpected token `AXIS2C,axis2c,'
./configure: line 13496: ` PKG_CHECK_MODULES(AXIS2C,axis2c,'
The relevent section of configure looks like:
======================================================================
if test "x$with_axis2c" != xno; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
if test "x$with_axis2c" != "xyes" ; then
ALT_HOME=$with_axis2c
if test ! -d "${ALT_HOME}" ; then
as_fn_error $? "No such axis2c directory (${ALT_HOME})"
"$LINENO" 5
fi
export
PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$ALT_HOME/lib/pkgconfig"
else
ALT_HOME="/usr"
fi
PKG_CHECK_MODULES(AXIS2C,axis2c,
AXIS2C_CPPFLAGS=${AXIS2C_CFLAGS}
AXIS2C_LDFLAGS=${AXIS2C_LIBS}
,
echo pkg-config axis2c detection failed
)
======================================================================
I'm using the following versions on a CentOS5.5 machine:
autoconf (GNU Autoconf) 2.68
ltmain.sh (GNU libtool) 2.2
automake (GNU automake) 1.9.6
and after checking out the code ran:
autoreconf -fiv
./configure --enable-warnings --disable-shared --enable-debug
Does anyone have any idea if the current CVS version is sick, or if this
is a problem with my environment/versions etc.?
Best Regards,
James
--
Dr. James Abbott
Bioinformatics Software Developer
Imperial College, London
More information about the emboss-dev
mailing list