Re: openjdk build failures on "nm"
- Reply: Ronald Klop : "Re: openjdk build failures on "nm""
- In reply to: Harald Eilertsen : "Re: openjdk build failures on "nm""
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 11 Sep 2025 09:26:16 UTC
I committed the change. Looking through https://portsfallout.com/fallout?port=java/openjdk again, I noticed that it does not fail on main, only on 13.5 and 14.2. I don't know if that is a coincidence, a difference in the pkg cluster on main or some difference in clang/llvm or other build tooling. But I thought it is worth mentioning. Regards, Ronald. Van: Harald Eilertsen <haraldei@anduin.net> Datum: donderdag, 11 september 2025 10:15 Aan: Ronald Klop <ronald-lists@klop.ws> CC: java@freebsd.org Onderwerp: Re: openjdk build failures on "nm" > > On Thu, Sep 11, 2025 at 09:32:08AM +0200, Ronald Klop wrote: > > As it seems hard to debug, what do the java@ maintainers think of this experiment? > > > > diff --git a/java/openjdk17/Makefile b/java/openjdk17/Makefile > > index 5cb25e6aee72..ba7001ff2bd0 100644 > > --- a/java/openjdk17/Makefile > > +++ b/java/openjdk17/Makefile > > @@ -38,7 +38,7 @@ GH_PROJECT= jdk17u > > > > NO_CCACHE= yes > > > > -_MAKE_JOBS= # > > +MAKE_JOBS_UNSAFE= yes > > MAKE_ENV= LANG="C" \ > > LC_ALL="C" \ > > CLASSPATH="" \ > > That's well spotted! I think this is definitely worth trying. I'm no > expert on the ports Makefiles myself, but was told to use > MAKE_JOBS_UNSAFE instead in the review for openjdk24. Haven't gone > through all the ancient version yet, as my focus is mainly on mainline, > and these days on openjdk25. > > > I can commit this today to openjdk17 and if builds start to succeed to other openjdk* ports. > > I'm in favour! > > H! > > >