Alan,
There was a recent change to the build such that you need to do a
one-time delete of your build directory, and run configure again. After
that, "make reconfigure" works as expected.
-- Jon
On 8/6/19 9:45 AM, Alan Snyder wrote:
In case this is useful...
I don’t know what
In case this is useful...
I don’t know what the status is of “make reconfigure”, but I suspect it is
unsupported because I see no mention of it in the build doc.
However:
* It still exists
* It is mentioned in the output of make
* It failed when I tried to use it (on macOS 10.15.5
Thanks for clarifying Erik.
Looks good.
David
On 4/04/2019 11:48 pm, Erik Joelsson wrote:
Hello David,
On 2019-04-03 18:49, David Holmes wrote:
Hi Erik,
On 4/04/2019 1:33 am, Erik Joelsson wrote:
Hello Jie,
This issue applies not only to --with-jmh, but to any configure
parameter given
Thanks Erik for fixing this issue.
On 2019年04月04日 21:48, Erik Joelsson wrote:
Hello David,
On 2019-04-03 18:49, David Holmes wrote:
Hi Erik,
On 4/04/2019 1:33 am, Erik Joelsson wrote:
Hello Jie,
This issue applies not only to --with-jmh, but to any configure
parameter given with a
Hello David,
On 2019-04-03 18:49, David Holmes wrote:
Hi Erik,
On 4/04/2019 1:33 am, Erik Joelsson wrote:
Hello Jie,
This issue applies not only to --with-jmh, but to any configure
parameter given with a relative path. I think the proper fix would be
to record the current working directory
Hi Eric and David,
Thank you for your review and suggestions.
Now I think it's not a good practice to assign a configure parameter
with a relative path.
I had assigned "--with-jmh=build/jmh/jars" just because the doc[1] told
me to do so.
Even "make configure" would break with a relative
Hi Erik,
On 4/04/2019 1:33 am, Erik Joelsson wrote:
Hello Jie,
This issue applies not only to --with-jmh, but to any configure
parameter given with a relative path. I think the proper fix would be to
record the current working directory when configure is launched and cd
to that directory
Hello Jie,
This issue applies not only to --with-jmh, but to any configure
parameter given with a relative path. I think the proper fix would be to
record the current working directory when configure is launched and cd
to that directory when running reconfigure. Here is my suggested patch:
Hi all,
JBS: https://bugs.openjdk.java.net/browse/JDK-8221907
For more info (e.g. the symptom & how to reproduce), please see the JBS.
It can be fixed by
-
diff -r 3326be37cd9a make/autoconf/lib-tests.m4
--- a/make/autoconf/lib-tests.m4 Tue Apr 02
; finding autoconf on PATH, but that variable is not remembered, so
> make reconfigure fails.
>
> # Recipe:
> rm -rf build
> AUTOCONF=/usr/bin/autoconf PATH="$MOLDY/bin:$PATH" bash configure ...
> # configure + make succeed
>
> make reconfigure
> # Fails with:
> U
Looks good.
/Erik
On 2019-02-11 03:42, Magnus Ihse Bursie wrote:
From the bug report:
"Suppose PATH points to an out-of date autoconf.
We can use the AUTOCONF environment variable with configure to
override finding autoconf on PATH, but that variable is not
remembered, so
make reconf
From the bug report:
"Suppose PATH points to an out-of date autoconf.
We can use the AUTOCONF environment variable with configure to override
finding autoconf on PATH, but that variable is not remembered, so
make reconfigure fails.
# Recipe:
rm -rf build
AUTOCONF=/usr/bin/autoconf
and see if the
> problem still exists?
>
> /Erik
>
>
> On 2017-10-17 23:08, Lance Andersen wrote:
>> Hi,
>>
>> I just tried to run ‘make reconfigure’ in a JDK 10 workspace which was
>> cloned from an existing workspace it fails:
>>
>>
t; and "hg
pull -u" and see if the problem still exists?
/Erik
On 2017-10-17 23:08, Lance Andersen wrote:
Hi,
I just tried to run ‘make reconfigure’ in a JDK 10 workspace which was cloned
from an existing workspace it fails:
hg paths
default = /Users/ljanders/Documents/hg-worksp
said:
a) I always "cd && make reconfigure", never tried from the top repo
As a reference, here is the output from configure (I ran this after make
reconfigure failed):
——
ls
ASSEMBLY_EXCEPTIONREADMEconfiguremake.out
LICENSEbindocsrc
Makefilebuildmaketest
ljande
clone an existing workspace or copy it? Unclear how this path could
> get in there if you cloned.
This was a clone from:
/Users/ljanders/Documents/hg-workspaces/openjdk10/jdk10-master/open
>
>
> That said:
>
> a) I always "cd && make reconfigure", never tri
mp;& make reconfigure", never tried from the top repo
b) there have been some bugs fixed, but they mainly relate to
open+closed configurations
Cheers,
David
On 18/10/2017 7:08 AM, Lance Andersen wrote:
Hi,
I just tried to run ‘make reconfigure’ in a JDK 10 workspace which was cloned
from an
Hi,
I just tried to run ‘make reconfigure’ in a JDK 10 workspace which was cloned
from an existing workspace it fails:
hg paths
default = /Users/ljanders/Documents/hg-workspaces/openjdk10/jdk10-master/open
make reconfigure
Re-running configure using arguments '--with-freetype-include
Every now and then, running make asks me to reconfigure so I call configure
again. Recently it is showing
ERROR:
/space/repos/jdk9/dev/build/macosx-x86_64-normal-server-fastdebug/spec.gmk is
not up to date.
Please rerun configure! Easiest way to do this is by running
'make reconfigure
it is showing
ERROR:
/space/repos/jdk9/dev/build/macosx-x86_64-normal-server-fastdebug/spec.gmk is
not up to date.
Please rerun configure! Easiest way to do this is by running
'make reconfigure'.
make: ***
[/space/repos/jdk9/dev/build/macosx-x86_64-normal-server-fastdebug/spec.gmk]
Error 1
20 matches
Mail list logo
