Don't use the --no-undefined linker option yet, it doesn't build on OpenBSD and BeOS.

The OpenBSD case is puzzling - it's complaining about symbols in the C library.  Do we need to explicitly link with -lc for shared libraries on OpenBSD?

The BeOS case is legitimate, it's calling back into the application code to initialize BeApp if it isn't already initialized.
This commit is contained in:
Sam Lantinga 2012-10-12 02:33:34 -07:00
parent 015f8a0971
commit ea15505815
2 changed files with 203 additions and 211 deletions

View file

@ -180,18 +180,19 @@ if test x$enable_dependency_tracking = xyes; then
fi
fi
AC_MSG_CHECKING(for linker option --no-undefined)
have_no_undefined=no
save_LDFLAGS="$LDFLAGS"
LDFLAGS="$LDFLAGS -Wl,--no-undefined"
AC_TRY_LINK([
],[
],[
have_no_undefined=yes
EXTRA_LDFLAGS="$EXTRA_LDFLAGS -Wl,--no-undefined"
])
LDFLAGS="$save_LDFLAGS"
AC_MSG_RESULT($have_no_undefined)
# Actually this doesn't work on OpenBSD and BeOS
#AC_MSG_CHECKING(for linker option --no-undefined)
#have_no_undefined=no
#save_LDFLAGS="$LDFLAGS"
#LDFLAGS="$LDFLAGS -Wl,--no-undefined"
#AC_TRY_LINK([
#],[
#],[
#have_no_undefined=yes
#EXTRA_LDFLAGS="$EXTRA_LDFLAGS -Wl,--no-undefined"
#])
#LDFLAGS="$save_LDFLAGS"
#AC_MSG_RESULT($have_no_undefined)
dnl See whether we are allowed to use the system C library
AC_ARG_ENABLE(libc,