On 2016-02-09 14:43, Yasumasa Suenaga wrote: > Hi all, > > After JDK-8148351, configure script failed as below: > > ---- > configure: Using default toolchain gcc (GNU Compiler Collection) > checking for gcc... /usr/lib64/ccache/gcc > checking resolved symbolic links for CC... /usr/bin/ccache > configure: Please use --enable-ccache instead of providing a wrapped > compiler. > configure: error: /usr/lib64/ccache/gcc is a symbolic link to ccache. This > is not supported. > configure exiting with result code 1 > ---- > > I added --enable-ccache to configure option, but I cannot avoid this error. This is since the requirements for running configure has slightly changed.
As the error message says: Please use --enable-ccache instead of providing a wrapped compiler. You have a /usr/lib64/ccache on your PATH, ahead of where your real gcc lies. This has never been a supported configuration. Prior to JDK-8148351, we tried to be "clever" and just override this configuration. Now we stop and alert the user, and asks them to handle the situation themselves. I recommend that you remove /usr/lib64/ccache from your PATH. If this is not possible, then you can specify your compiler explicitely using "configure CC=/usr/bin/gcc CXX=/usr/bin/g++" or whatever. /Magnus
