Re: JDK10 build problem: "--module-path"?
The temptation to do a “Well, actually…” here is strong. ;-)
Seriously, thanks for taking my incredulity in the spirit it was intended. :-)
Is it becoming more common for Java tools to accept different “styles” of
arguments, or did this become a complete switch/rename? (You can tell how much
I’ve used modules recently, right?)
Ted Neward
Author, Speaker, Mentor
http://www.newardassociates.com
t: @tedneward | m: (425) 647-4526
From: Jonathan Gibbons
Date: Thursday, February 15, 2018 at 7:27 AM
To: Ted Neward ,
Subject: Re: JDK10 build problem: "--module-path"?
Ted,
Yes, I'm sure :-) This is the relevant line from the source code for JDK 9,
listing --module-path and -p as alternatives for this option.
MODULE_PATH("--module-path -p", "opt.arg.path", "opt.modulepath", STANDARD,
FILEMANAGER),
http://hg.openjdk.java.net/jdk9/jdk9/langtools/file/65bfdabaab9c/src/jdk.compiler/share/classes/com/sun/tools/javac/main/Option.java#l183
-- Jon
On 2/14/18 10:32 PM, Ted Neward wrote:
Really?!? I thought the javac -help only listed -modulepath. Not to disbelieve
you *grin*, but are you sure? The reason I ask is (barring some really bizarre
misconfiguration) I should be using the OpenJDK9 as the boot JDK for this, and
I'm getting the error.
Ted Neward
Author, Speaker, Mentor
http://www.newardassociates.com
t: @tedneward | m: (425) 647-4526
On 2/14/18, 6:53 PM, "build-dev on behalf of Jonathan Gibbons"
wrote:
On 2/14/18 4:38 PM, Ted Neward wrote:
> I’m getting a weird error in my OpenJDK 10 (tip) build, where after
pulling source and configure, I get a build error about the Java compiler being
executed with “--module-path” as a parameter, which obviously isn’t a
legitimate javac flag.
>
>
I can't speak to your specific build error, but --module-path is a
legitimate javac option, as of JDK 9.
-- Jon
>
> Is this just me? Is anybody else able to repro this, and is there a fix
coming that isn’t checked into the main trunk yet?
>
>
>
> I am in the process of finalizing some Docker images (both with the
source inside the image and built, so people can just “go”, as well as images
with the prereqs and some shell scripts to do the build with the source and
build artifacts on the host machine), and this is holding up the current “tip”
images from being really ready for public consumption. (JDK8u and JDK9 are up
and ready to go.)
>
>
>
> Ted Neward
>
> Author, Speaker, Mentor
>
> http://www.newardassociates.com
>
> t: @tedneward | m: (425) 647-4526
>
Re: JDK10 build problem: "--module-path"?
So… Hmm. Anybody here know what the blessed way to get OpenJDK9 into a Docker image would be, then? Ted Neward Author, Speaker, Mentor http://www.newardassociates.com t: @tedneward | m: (425) 647-4526 From: Martin Buchholz Date: Thursday, February 15, 2018 at 8:50 AM To: Erik Joelsson Cc: Alan Bateman , Ted Neward , Jonathan Gibbons , "build-dev@openjdk.java.net" Subject: Re: JDK10 build problem: "--module-path"? Looking at https://packages.ubuntu.com/search?suite=all§ion=all&arch=any&keywords=openjdk-9-jdk&searchon=names it seems like Ubuntu ships whatever openjdk-9 is available at time of creation of a specific version, and doesn't update it afterwards, not even for the quarterly security patches. On Thu, Feb 15, 2018 at 7:42 AM, Erik Joelsson wrote: I have hit this same problem once for the same reason Alan describes. Ubuntu provided me with a really old EA build of 9. /Erik On 2018-02-15 00:05, Alan Bateman wrote: On 15/02/2018 06:32, Ted Neward wrote: Really?!? I thought the javac -help only listed -modulepath. Not to disbelieve you *grin*, but are you sure? The reason I ask is (barring some really bizarre misconfiguration) I should be using the OpenJDK9 as the boot JDK for this, and I'm getting the error. What is your boot JDK? Any possibility that you have really old EA build of JDK 9?
Re: JDK10 build problem: "--module-path"?
Looking at https://packages.ubuntu.com/search?suite=all§ion=all&arch=any&keywords=openjdk-9-jdk&searchon=names it seems like Ubuntu ships whatever openjdk-9 is available at time of creation of a specific version, and doesn't update it afterwards, not even for the quarterly security patches. On Thu, Feb 15, 2018 at 7:42 AM, Erik Joelsson wrote: > I have hit this same problem once for the same reason Alan describes. > Ubuntu provided me with a really old EA build of 9. > > /Erik > > > > On 2018-02-15 00:05, Alan Bateman wrote: > >> >> >> On 15/02/2018 06:32, Ted Neward wrote: >> >>> Really?!? I thought the javac -help only listed -modulepath. Not to >>> disbelieve you *grin*, but are you sure? The reason I ask is (barring some >>> really bizarre misconfiguration) I should be using the OpenJDK9 as the boot >>> JDK for this, and I'm getting the error. >>> >>> What is your boot JDK? Any possibility that you have really old EA build >> of JDK 9? >> > >
Re: JDK10 build problem: "--module-path"?
I have hit this same problem once for the same reason Alan describes. Ubuntu provided me with a really old EA build of 9. /Erik On 2018-02-15 00:05, Alan Bateman wrote: On 15/02/2018 06:32, Ted Neward wrote: Really?!? I thought the javac -help only listed -modulepath. Not to disbelieve you *grin*, but are you sure? The reason I ask is (barring some really bizarre misconfiguration) I should be using the OpenJDK9 as the boot JDK for this, and I'm getting the error. What is your boot JDK? Any possibility that you have really old EA build of JDK 9?
Re: JDK10 build problem: "--module-path"?
Ted,
Yes, I'm sure :-) This is the relevant line from the source code for JDK
9, listing --module-path and -p as alternatives for this option.
MODULE_PATH("--module-path -p", "opt.arg.path", "opt.modulepath",
STANDARD, FILEMANAGER),
http://hg.openjdk.java.net/jdk9/jdk9/langtools/file/65bfdabaab9c/src/jdk.compiler/share/classes/com/sun/tools/javac/main/Option.java#l183
-- Jon
On 2/14/18 10:32 PM, Ted Neward wrote:
Really?!? I thought the javac -help only listed -modulepath. Not to disbelieve
you *grin*, but are you sure? The reason I ask is (barring some really bizarre
misconfiguration) I should be using the OpenJDK9 as the boot JDK for this, and
I'm getting the error.
Ted Neward
Author, Speaker, Mentor
http://www.newardassociates.com
t: @tedneward | m: (425) 647-4526
On 2/14/18, 6:53 PM, "build-dev on behalf of Jonathan Gibbons"
wrote:
On 2/14/18 4:38 PM, Ted Neward wrote:
> I’m getting a weird error in my OpenJDK 10 (tip) build, where after
pulling source and configure, I get a build error about the Java compiler being
executed with “--module-path” as a parameter, which obviously isn’t a legitimate
javac flag.
>
>
I can't speak to your specific build error, but --module-path is a
legitimate javac option, as of JDK 9.
-- Jon
>
> Is this just me? Is anybody else able to repro this, and is there a fix
coming that isn’t checked into the main trunk yet?
>
>
>
> I am in the process of finalizing some Docker images (both with the
source inside the image and built, so people can just “go”, as well as images with
the prereqs and some shell scripts to do the build with the source and build
artifacts on the host machine), and this is holding up the current “tip” images
from being really ready for public consumption. (JDK8u and JDK9 are up and ready
to go.)
>
>
>
> Ted Neward
>
> Author, Speaker, Mentor
>
> http://www.newardassociates.com
>
> t: @tedneward | m: (425) 647-4526
>
Re: JDK10 build problem: "--module-path"?
On 15/02/2018 06:32, Ted Neward wrote: Really?!? I thought the javac -help only listed -modulepath. Not to disbelieve you *grin*, but are you sure? The reason I ask is (barring some really bizarre misconfiguration) I should be using the OpenJDK9 as the boot JDK for this, and I'm getting the error. What is your boot JDK? Any possibility that you have really old EA build of JDK 9?
Re: JDK10 build problem: "--module-path"?
Really?!? I thought the javac -help only listed -modulepath. Not to disbelieve you *grin*, but are you sure? The reason I ask is (barring some really bizarre misconfiguration) I should be using the OpenJDK9 as the boot JDK for this, and I'm getting the error. Ted Neward Author, Speaker, Mentor http://www.newardassociates.com t: @tedneward | m: (425) 647-4526 On 2/14/18, 6:53 PM, "build-dev on behalf of Jonathan Gibbons" wrote: On 2/14/18 4:38 PM, Ted Neward wrote: > I’m getting a weird error in my OpenJDK 10 (tip) build, where after pulling source and configure, I get a build error about the Java compiler being executed with “--module-path” as a parameter, which obviously isn’t a legitimate javac flag. > > I can't speak to your specific build error, but --module-path is a legitimate javac option, as of JDK 9. -- Jon > > Is this just me? Is anybody else able to repro this, and is there a fix coming that isn’t checked into the main trunk yet? > > > > I am in the process of finalizing some Docker images (both with the source inside the image and built, so people can just “go”, as well as images with the prereqs and some shell scripts to do the build with the source and build artifacts on the host machine), and this is holding up the current “tip” images from being really ready for public consumption. (JDK8u and JDK9 are up and ready to go.) > > > > Ted Neward > > Author, Speaker, Mentor > > http://www.newardassociates.com > > t: @tedneward | m: (425) 647-4526 >
Re: JDK10 build problem: "--module-path"?
On 2/14/18 4:38 PM, Ted Neward wrote: I’m getting a weird error in my OpenJDK 10 (tip) build, where after pulling source and configure, I get a build error about the Java compiler being executed with “--module-path” as a parameter, which obviously isn’t a legitimate javac flag. I can't speak to your specific build error, but --module-path is a legitimate javac option, as of JDK 9. -- Jon Is this just me? Is anybody else able to repro this, and is there a fix coming that isn’t checked into the main trunk yet? I am in the process of finalizing some Docker images (both with the source inside the image and built, so people can just “go”, as well as images with the prereqs and some shell scripts to do the build with the source and build artifacts on the host machine), and this is holding up the current “tip” images from being really ready for public consumption. (JDK8u and JDK9 are up and ready to go.) Ted Neward Author, Speaker, Mentor http://www.newardassociates.com t: @tedneward | m: (425) 647-4526
Re: JDK10 build problem: "--module-path"?
On 15/02/2018 10:38 AM, Ted Neward wrote: I’m getting a weird error in my OpenJDK 10 (tip) build, where after pulling source and configure, I get a build error about the Java compiler being executed with “--module-path” as a parameter, which obviously isn’t a legitimate javac flag. Is this just me? Is anybody else able to repro this, and is there a fix coming that isn’t checked into the main trunk yet? No issues with our internal builds. What platform are you building? Did the reconfigure work correctly? Does blowing away build directory and starting again fix it? David - I am in the process of finalizing some Docker images (both with the source inside the image and built, so people can just “go”, as well as images with the prereqs and some shell scripts to do the build with the source and build artifacts on the host machine), and this is holding up the current “tip” images from being really ready for public consumption. (JDK8u and JDK9 are up and ready to go.) Ted Neward Author, Speaker, Mentor http://www.newardassociates.com t: @tedneward | m: (425) 647-4526
JDK10 build problem: "--module-path"?
I’m getting a weird error in my OpenJDK 10 (tip) build, where after pulling source and configure, I get a build error about the Java compiler being executed with “--module-path” as a parameter, which obviously isn’t a legitimate javac flag. Is this just me? Is anybody else able to repro this, and is there a fix coming that isn’t checked into the main trunk yet? I am in the process of finalizing some Docker images (both with the source inside the image and built, so people can just “go”, as well as images with the prereqs and some shell scripts to do the build with the source and build artifacts on the host machine), and this is holding up the current “tip” images from being really ready for public consumption. (JDK8u and JDK9 are up and ready to go.) Ted Neward Author, Speaker, Mentor http://www.newardassociates.com t: @tedneward | m: (425) 647-4526
