On Mon, Feb 12, 2018 at 4:38 PM, Magnus Ihse Bursie <
magnus.ihse.bur...@oracle.com> wrote:
>
> On 2018-02-12 14:57, Thomas Stüfe wrote:
>
>
>
> On Mon, Feb 12, 2018 at 2:53 PM, Magnus Ihse Bursie <
> magnus.ihse.bur...@oracle.com> wrote:
>
>> On 2018-02-12 14:47, Thomas Stüfe wrote:
>>
>> Hi Magn
On 2018-02-12 14:57, Thomas Stüfe wrote:
On Mon, Feb 12, 2018 at 2:53 PM, Magnus Ihse Bursie
mailto:magnus.ihse.bur...@oracle.com>>
wrote:
On 2018-02-12 14:47, Thomas Stüfe wrote:
Hi Magnus,
Thanks a lot for fixing this! I tried my configuration as
described in earlier ma
Magnus:
Looks good to me as well.
/Tim
On 02/12/18 06:31, Volker Simonis wrote:
Hi Magnus,
thanks for doing this change. It was actually on my TODO list but I
somehow forgot about it :)
The change looks good. Thumb up from me,
Volker
On Mon, Feb 12, 2018 at 2:09 PM, Magnus Ihse Bursie
wrot
Hi Magnus,
thanks for doing this change. It was actually on my TODO list but I
somehow forgot about it :)
The change looks good. Thumb up from me,
Volker
On Mon, Feb 12, 2018 at 2:09 PM, Magnus Ihse Bursie
wrote:
> In JDK-8195689, the generated-configure.sh was no longer checked in, but
> local
On Mon, Feb 12, 2018 at 2:53 PM, Magnus Ihse Bursie <
magnus.ihse.bur...@oracle.com> wrote:
> On 2018-02-12 14:47, Thomas Stüfe wrote:
>
> Hi Magnus,
>
> Thanks a lot for fixing this! I tried my configuration as described in
> earlier mails, and the configure scripts gets now created in the output
On 2018-02-12 14:47, Thomas Stüfe wrote:
Hi Magnus,
Thanks a lot for fixing this! I tried my configuration as described in
earlier mails, and the configure scripts gets now created in the
output directory as expected.
Some notes:
- would it be possible to write out the path name of the gene
Hi Magnus,
Thanks a lot for fixing this! I tried my configuration as described in
earlier mails, and the configure scripts gets now created in the output
directory as expected.
Some notes:
- would it be possible to write out the path name of the generated
configure shell script?
- No concern of
In JDK-8195689, the generated-configure.sh was no longer checked in, but
locally generated. The selected location for generation ($TOPDIR/.build)
was not unproblematic for some use cases. This patch attempts remedy this.
The new behaviour will be this:
* If run from $TOPDIR, the storage direct
