[rfc] Avoid failure when compiler is wrapped.

Jiri Vanek jvanek at redhat.com
Fri Jan 22 12:44:07 UTC 2016


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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-autoconf-do-not-resolve-symbolic-links-in-CC.patch
Type: text/x-patch
Size: 969 bytes
Desc: not available
URL: <http://mail.openjdk.java.net/pipermail/build-dev/attachments/20160122/64cd35cf/0001-autoconf-do-not-resolve-symbolic-links-in-CC.patch>


More information about the build-dev mailing list