Hello!

When compiler is wrapped, the configure phase of build fails:

[...]
checking for gcc... /usr/lib64/cscppc/gcc
configure: Resolving CC (as /usr/lib64/cscppc/gcc) failed, using 
/usr/lib64/cscppc/gcc directly.
checking resolved symbolic links for CC... /usr/bin/cscppc
checking if CC is disguised ccache... no, keeping CC
configure: The C compiler (located as /usr/bin/cscppc) does not seem to be the 
required GCC compiler.
configure: The result from running with --version was: "Usage:"
configure: error: GCC compiler is required. Try setting --with-tools-dir.
configure exiting with result code 1


From time to time I'm building RPMS for fedora with wrapped compiler to be able to investigate C code changes. Added is patch, which is allowing to walk around the issue.

I'm wondering if this is still desired behaviour. or if it can be better iff-ed out to be by default on, but eg only disablef on AIX.

CCed is Andrew, who is facing similar issue on Gentoo.


  Thanx!
  J.
diff --git a/openjdk/common/autoconf/toolchain.m4 b/openjdk/common/autoconf/toolchain.m4
index c664e09..833de1c 100644
--- a/openjdk/common/autoconf/toolchain.m4
+++ b/openjdk/common/autoconf/toolchain.m4
@@ -149,11 +149,11 @@ AC_DEFUN([TOOLCHAIN_FIND_COMPILER],
   TEST_COMPILER="[$]$1"
   # Don't remove symbolic links on AIX because 'xlc_r' and 'xlC_r' may all be links
   # to 'xlc' but it is crucial that we invoke the compiler with the right name!
-  if test "x$OPENJDK_BUILD_OS" != xaix; then
-    AC_MSG_CHECKING([resolved symbolic links for $1])
-    BASIC_REMOVE_SYMBOLIC_LINKS(TEST_COMPILER)
-    AC_MSG_RESULT([$TEST_COMPILER])
-  fi
+  dnl if test "x$OPENJDK_BUILD_OS" != xaix; then
+  dnl   AC_MSG_CHECKING([resolved symbolic links for $1])
+  dnl   BASIC_REMOVE_SYMBOLIC_LINKS(TEST_COMPILER)
+  dnl   AC_MSG_RESULT([$TEST_COMPILER])
+  dnl fi
   AC_MSG_CHECKING([if $1 is disguised ccache])
 
   COMPILER_BASENAME=`$BASENAME "$TEST_COMPILER"`
-- 
2.4.6

Reply via email to