RFR: AARCH64: Top-level JDK changes

Christian Thalinger christian.thalinger at oracle.com
Tue Nov 18 18:09:07 UTC 2014


> On Nov 18, 2014, at 7:36 AM, Magnus Ihse Bursie <magnus.ihse.bursie at oracle.com> wrote:
> 
> On 2014-11-18 01:59, Christian Thalinger wrote:
>>> On Nov 17, 2014, at 4:11 AM, Magnus Ihse Bursie <magnus.ihse.bursie at oracle.com> wrote:
>>> 
>>> On 2014-11-14 21:44, Dean Long wrote:
>>>>> The distribution exception is there exactly since anyone should be able to distribute the files with their configure script. That does not mean that you are allowed to edit it, though.
>>>> What if we require Autoconf to be installed on the host?  Does that solve any problems?
>>> No, unfortunately not.
>> Why not?
> 
> Autoconf picks up these files automatically from the build-aux directory. That's also the reason we need to rename the original files and provide wrappers with the same name, since we can't even redirect that functionality to a file with another name.

So do I understand you correctly that the files we need are automatically copied into the workspace but since we want to use our own, old versions we renamed them and use these instead?

> 
> /Magnus



More information about the jdk9-dev mailing list