On Thu, Jun 30, 2022 at 07:55:00PM -0400, Shawn Webb wrote:
> Hey all,
> It appears the OpenJDK ports have issues on HardenedBSD.
> Here are the two symptoms I'm currently seeing:
> 1. Poudriere on the official 14-CURRENT/amd64 package build server
> thinks that java/openjdk11 depends on itself, causing Poudriere to
> 2. Poudriere on my 14-CURRENT/amd64 development laptop does NOT think
> that java/openjdk11 depends on itself. However, I told Poudriere to
> build java/openjdk11 (and its dependencies only) rather than a full
> package build (the full set of 32,000+ packages.)
> * This means it's possible that one of the other OpenJDK ports
> might cause a recursive dependency?
> * The build still fails with a linker error.
> Since my time is limited, and usually spent on HardenedBSD itself, I'm
> formally requesting help from the HardenedBSD community to get OpenJDK
> working again.
> I'm hoping to hear back from the community by 08 Jul 2022. If I don't
> hear back from the community by then, I'll likely mark the OpenJDK
> ports as BROKEN.
> : http://ci-08.md.hardenedbsd.org/data/hardenedbsd-current_amd64-local/2022-06-20_13h53m28s/logs/errors/openjdk11-11.0.15+10.1.log
It looks like I conflated two issues. It was lang/gcc11 that had the
issue causing Poudriere to halt. An earlier commit caused a circular
dependency on itself. I just fixed that.
So, we're good to go to keep the OpenJDK ports around. I apologize for
the noise here.
I believe, though, that we still have issues to resolve. lang/gcc11
doesn't build. So I'd like help from the HardenedBSD community in
There's a lot of work to be done in HardenedBSD. We can use all the
help we can get--and we are incredibly grateful for the help we