Just saw this in Configure after Cliff's note (which is resolved):
####################################################################
## Add in the Expat library if needed/wanted.
##
# set the default, based on whether expat-lite is bundled. if it is present,
# then we can always include expat.
if [ "x$RULE_EXPAT" = "xdefault" ]; then
if [ -d ./lib/expat-lite/ ]; then
RULE_EXPAT=yes
else
RULE_EXPAT=no
fi
fi
if [ "x$RULE_EXPAT" = "xyes" ]; then
if ./helpers/TestCompile lib expat; then
echo " + using system Expat"
LIBS="$LIBS -lexpat"
else
if [ "$xRULE_EXPAT" = "xyes" ]; then
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
echo "ERROR: RULE_EXPAT set to \"yes\" but is not available."
exit 1
fi
echo " + using builtin Expat"
EXPATLIB="lib/expat-lite/libexpat.a"
APLIBDIRS="expat-lite $APLIBDIRS"
CFLAGS="$CFLAGS -DUSE_EXPAT -I\$(SRCDIR)/lib/expat-lite"
fi
fi
Note the line above the '^^^^'. Luckily, this section still works
as required (lucky typo)... But there's a mismatch of logic here, regarding
what the EXPAT rule really means... Right now, if there's a system
expat lib, it will *always* be chosen, and there's no way to bypass
that. Up to now, I think we've always been using expat-lite... Because
of this, it's pretty important that we test out 1.3.21 as well as
possible, especially with those platforms that provide expat. I
don't think there's a need to hold off on 1.3.21 at present though.
Sorry I didn't notice this sooner... After the dust settles I'll
adjust this section to deal with the new logic.
--
===========================================================================
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
"A society that will trade a little liberty for a little order
will lose both and deserve neither"
