Re: The generated-configure.sh script is dead - autoconf seems to write into the sources in the build process

2018-02-06 Thread Magnus Ihse Bursie
On 2018-02-06 19:01, Volker Simonis wrote: On Tue, Feb 6, 2018 at 6:28 PM, Magnus Ihse Bursie wrote: On 2018-02-06 15:53, Volker Simonis wrote: Hi, as Matthias wrote, we're usually running configure from a newly created build directory which is outside the source tree. Also, the build user w

Re: The generated-configure.sh script is dead - autoconf seems to write into the sources in the build process

2018-02-06 Thread Volker Simonis
On Tue, Feb 6, 2018 at 6:28 PM, Magnus Ihse Bursie wrote: > > > On 2018-02-06 15:53, Volker Simonis wrote: >> >> Hi, >> >> as Matthias wrote, we're usually running configure from a newly >> created build directory which is outside the source tree. Also, the >> build user who calls configure may di

Re: The generated-configure.sh script is dead - autoconf seems to write into the sources in the build process

2018-02-06 Thread Magnus Ihse Bursie
On 2018-02-06 18:22, Erik Joelsson wrote: Hello Volker, I think this is a reasonable idea, but have opinions on the implementation. I think this should apply even if you have a CUSTOM_ROOT defined. Thinking some more on this, isn't it always true that you want it in $PWD/.build? Or if we wan

Re: The generated-configure.sh script is dead - autoconf seems to write into the sources in the build process

2018-02-06 Thread Magnus Ihse Bursie
On 2018-02-06 15:53, Volker Simonis wrote: Hi, as Matthias wrote, we're usually running configure from a newly created build directory which is outside the source tree. Also, the build user who calls configure may differ from the user owning the source tree. I'd therefor like to propose the fo

Re: The generated-configure.sh script is dead - autoconf seems to write into the sources in the build process

2018-02-06 Thread Erik Joelsson
Hello Volker, I think this is a reasonable idea, but have opinions on the implementation. I think this should apply even if you have a CUSTOM_ROOT defined. Thinking some more on this, isn't it always true that you want it in $PWD/.build? Or if we want to get really strict about it, if PWD is

Re: The generated-configure.sh script is dead - autoconf seems to write into the sources in the build process

2018-02-06 Thread Volker Simonis
Hi, as Matthias wrote, we're usually running configure from a newly created build directory which is outside the source tree. Also, the build user who calls configure may differ from the user owning the source tree. I'd therefor like to propose the following small change which checks from where 'c

The generated-configure.sh script is dead - autoconf seems to write into the sources in the build process

2018-02-06 Thread Baesken, Matthias
Hello I noticed that after replacing generated-configure.sh and using autoconf ,the build process writes into the sources . Error looks like this : Runnable configure script is not present Generating runnable configure script mkdir: cannot create directory `/openjdk/linuxppc64/jd