strange error when running jtreg tests

[Maurizio Cimadamore]

On 16/08/16 14:19, David Simms wrote:
>
> Another work-around is to use a "sanctioned dev kit" 
> ("--with-devkit=") and avoid problems with "new fangled distros and 
> tools", see:
>
> https://wiki.se.oracle.com/display/JPG/Devkit+build+instructions+for+JDK+9 
>
Sure - or running jtreg manually (which is what I'm doing).

But the question is: is this a bug?

Maurizio
>
>
> On 16/08/16 11:39, Maurizio Cimadamore wrote:
>> Using Ubuntu 14.04 on x64.
>>
>> Maurizio
>>
>>
>> On 15/08/16 23:41, Gustavo Romero wrote:
>>> Hi,
>>>
>>> I observed the same issue on Ubuntu 16.04 but not on RHEL 7.2.
>>>
>>> RHEL 7.2:
>>> https://paste.fedoraproject.org/409005/raw/
>>>
>>> Ubuntu 16.04:
>>> https://paste.fedoraproject.org/409004/raw/
>>>
>>> I checked on PPC64 LE arch (Ubuntu 16.04 and RHEL 7.2, logs above). 
>>> It fails also
>>> on Ubuntu 16.04 x64 (but I could not check if it succeeds on RHEL 
>>> 7.2 x64).
>>>
>>> On Ubuntu 16.04 PPC64 LE replacing -lpthread by -pthread in
>>> ./hotspot/make/test/JtregNative.gmk:82 solves the issue on pthread_* 
>>> symbols and
>>> placing -ljvm (for instance) in front of ".../exeinvoke.o" solves 
>>> the issue on
>>> JNI_CreateJavaVM reference, however I'm really not sure what's the 
>>> root cause.
>>>
>>> Maurizio, what distro/arch are you using?
>>>
>>> Regards,
>>> Gustavo
>>>
>>
>