Thanks Doug,
I did some more digging, and you and I are doing two different things.
I was compiling without "-m32" but while setting JU_32BIT, not
JU_64BIT set (I'm using my own buildsystem so that judy compiles with
the rest of felix). Looking more closely at the configure.ac though,
it looks like JU_64BIT may always be defined:
dnl Figure out if we are 32-bit or 64-bit (LP64)
AC_CHECK_SIZEOF(void *)
if test "$ac_cv_sizeof_void_p" = 8; then
AC_MSG_RESULT(Detected 64-bit Build Environment)
CFLAGS="-DJU_64BIT $CFLAGS"
else
AC_MSG_RESULT(Detected 32-bit Build Environment)
CFLAGS="-UJU_64BIT $CFLAGS"
fi
AC_ARG_ENABLE(32-bit, [ --enable-32-bit Generate code for a
32-bit environment],
b32="$enableval", b32="no")
if test x"$b32" != "xno"; then
AC_MSG_RESULT(Configured to Build 32-bit)
if test x"$GCC" = xyes; then
CFLAGS="-UJU_64BIT -m32 $CFLAGS"
else
CFLAGS="-UJU_64BIT $CFLAGS"
fi
fi
AC_ARG_ENABLE(64-bit, [ --enable-64-bit Generate code for a
64-bit environment],
b64="$enableval", b64="no")
if test x"$b64" != "xno"; then
AC_MSG_RESULT(Configured to Building 64-bit)
if test x"$GCC" = xyes; then
CFLAGS="-DJU_64BIT -m64 $CFLAGS"
else
CFLAGS="-DJU_64BIT $CFLAGS"
fi
fi
Is it correct for the configure to define JU_64BIT for both 32bit and
64bit environments?
------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been
demonstrated beyond question. Learn why your peers are replacing JEE
containers with lightweight application servers - and what you can gain
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
Judy-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/judy-devel
