Hi Magnus,
Thanks, I've understood.
I closed JDK-8149466 as "Not an issue" .
Yasumasa
On 2016/02/09 23:33, Magnus Ihse Bursie wrote:
> On 2016-02-09 15:29, Yasumasa Suenaga wrote:
>> Hi Magnus,
>>
>>> If this is not possible, then you can specify your compiler explicitely
>>> using "configure
On 2016-02-09 15:29, Yasumasa Suenaga wrote:
> Hi Magnus,
>
>> If this is not possible, then you can specify your compiler explicitely
>> using "configure CC=/usr/bin/gcc CXX=/usr/bin/g++" or whatever.
> I could avoid it with these options.
>
> Error message says that we can avoid this error with -
Hi Magnus,
> If this is not possible, then you can specify your compiler explicitely
> using "configure CC=/usr/bin/gcc CXX=/usr/bin/g++" or whatever.
I could avoid it with these options.
Error message says that we can avoid this error with --enable-ccache.
However, I could not avoid with it.
T
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
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 providin
