Help with using jtreg to verify build needed

Jonathan Gibbons jonathan.gibbons at oracle.com
Thu Jul 18 14:26:32 UTC 2013


Matthew,

I would strongly recommend taking the trouble to build jtreg from the
latest source.

-- Jon

On 07/17/2013 10:28 PM, Matthew Butner wrote:
> Thanks for that, and I did have to get a newer version of jtreg. I was able
> to find a binary here http://download.java.net/openjdk/jtreg/ which saved
> me the trouble of having to build it from source.
>
>
> On Wed, Jul 17, 2013 at 5:13 PM, Mike Duigou <mike.duigou at oracle.com> wrote:
>
>> I have created JDK-8019481 to improve detection of jtreg located on the
>> path.
>>
>> Jon's advice about getting a more recent version of jtreg than what ubuntu
>> provides almost certainly applies as well.
>>
>> Mike
>>
>> On Jul 8 2013, at 22:59 , Matthew Butner wrote:
>>
>>> Not sure if this is the right place to ask or not, and if it isn't,
>> please
>>> direct me to the correct forum but I have been trying all day to use
>> jtreg
>>> to test my jdk 1.8 build with no success.
>>>
>>> Here is my problem:
>>> I am running ubuntu and have used the apt center to install jtreg. This
>>> means that jtreg and jtdiff are installed under /usr/bin. When I run the
>>> configure script it does not automatically detect jtreg and when I try
>>> running it with the --with-jtreg=/usr/bin/jtreg or /usr/bin it fails
>>> because it is trying to find the executable inside subdirectories that do
>>> not exist because I did not install jtreg from source.
>>>
>>> I tried to work around this by modifying line 16463
>>> JTREGEXE="$JT_HOME/win32/bin/jtreg"
>>> to
>>> JTREGEXE="$JT_HOME/jtreg"
>>>
>>> which made it detect jtreg but the command in the readme
>>> *cd test && make PRODUCT_HOME=`pwd`/../build/*/images/j2sdk-image all
>>>
>>> *still fails because it is still trying to look in
>>> /usr/bin/win32/bin/jtreg
>>>
>>> and win32/bin/jtreg does not exist.
>>>
>>> Any help would be greatly welcome but if possible I don't want to have to
>>> install jtreg from source as that is a whole other can of worms.
>>>
>>> Thank you,
>>> Matthew
>>




More information about the build-dev mailing list