This is the mail archive of the
java-patches@sourceware.cygnus.com
mailing list for the Java project.
Patch: zlib -vs- target compiles
- To: Java Patch List <java-patches at sourceware dot cygnus dot com>
- Subject: Patch: zlib -vs- target compiles
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 04 Oct 1999 16:10:55 -0600
- Reply-To: tromey at cygnus dot com
I'm committing the appended patch. It changes zlib to correctly build
when the compiler can't build an executable. This happens when
cross-compiling zlib in some situations.
1999-10-04 Tom Tromey <tromey@cygnus.com>
* configure: Rebuilt.
* configure.in: Call AC_EXEEXT after LIB_AC_PROG_CC, but don't
actually let AC_EXEEXT run.
Tom
Index: configure.in
===================================================================
RCS file: /cvs/java/libgcj/zlib/configure.in,v
retrieving revision 1.4
diff -u -r1.4 configure.in
--- configure.in 1999/08/10 05:30:10 1.4
+++ configure.in 1999/10/04 22:07:31
@@ -5,7 +5,6 @@
AM_INIT_AUTOMAKE(zlib, 1.1.3)
AM_MAINTAINER_MODE
-AC_EXEEXT
AC_CONFIG_AUX_DIR(..)
@@ -43,6 +42,16 @@
[ --with-system-zlib use installed libz])
LIB_AC_PROG_CC
+# We need AC_EXEEXT to keep automake happy in cygnus mode. However,
+# at least currently, we never actually build a program, so we never
+# need to use $(EXEEXT). Moreover, the test for EXEEXT normally
+# fails, because we are probably configuring with a cross compiler
+# which cant create executables. So we include AC_EXEEXT to keep
+# automake happy, but we dont execute it, since we dont care about
+# the result.
+if false; then
+ AC_EXEEXT
+fi
AM_PROG_LIBTOOL
if test -z "$with_target_subdir" || test "$with_target_subdir" = "."; then