An EET configure.in change was introduced between snapshots 0.9.10.007 and 0.9.10.010 which broke cross-compiling.

Two patches attached: the first to go into CVS (patches configure.in), and the second for anyone using the eet-0.9.10.010 snapshot tarball (patches configure).

--
Simon Poole
www.appliancestudio.com




--- eet-0.9.10.010.orig/configure.in    2005-06-10 04:53:40.000000000 +0100
+++ eet-0.9.10.010/configure.in 2005-06-10 10:05:58.637807736 +0100
@@ -62,7 +62,8 @@
 ], AC_MSG_RESULT([\o/]), [
        AC_MSG_RESULT([o_O])
        AC_MSG_WARN([Your system is a bit too funny, eet might not work 
properly])
-])
+], AC_MSG_WARN([Cannot check when cross-compiling -- assuming null is okay])
+)
 
 if test "x${bindir}" = 'x${exec_prefix}/bin'; then
   if test "x${exec_prefix}" = "xNONE"; then
--- eet-0.9.10.010.orig/configure       2005-06-10 04:53:44.000000000 +0100
+++ eet-0.9.10.010/configure    2005-06-10 10:18:52.392179192 +0100
@@ -20513,11 +20574,9 @@
 echo "$as_me:$LINENO: checking value of the null pointer" >&5
 echo $ECHO_N "checking value of the null pointer... $ECHO_C" >&6
 if test "$cross_compiling" = yes; then
-  { { echo "$as_me:$LINENO: error: cannot run test program while cross 
compiling
-See \`config.log' for more details." >&5
-echo "$as_me: error: cannot run test program while cross compiling
-See \`config.log' for more details." >&2;}
-   { (exit 1); exit 1; }; }
+  { echo "$as_me:$LINENO: WARNING: Cannot check when cross-compiling -- 
assuming null is okay" >&5
+echo "$as_me: WARNING: Cannot check when cross-compiling -- assuming null is 
okay" >&2;}
+
 else
   cat >conftest.$ac_ext <<_ACEOF
 /* confdefs.h.  */

Reply via email to