Good observations and thanks.
There is a check to see if the binaries are present don't download - I
noticed, the workspace gets cleared at each build.
Which could be the reason behind the re-downloads, and the issues you
mentioned. As I said it was the same script for OpenJDK9 and worked without
I also noted that you download the source for external dependencies directly
from the upstream website for each build, and rebuild it from scratch.
I would recommend that you build it once locally and then use that pre-built
binary. Apart from putting an extra load on often underfunded open sou
Hi Magnus,
Thanks for getting back to me so quickly.
Its strange on two counts
- --with-alsa-lib wasn;t needed for OpenJDK9 since ever, it builds find
there
- after I sent out the mail and triggered the build, it ran successfully
which you just pointed out.
But for sanity reasons, I have added t
It seems your configure script only gets sent a --with-alsa-include and not an
--with-alsa-lib. I'm not sure this is the problem but it looks wrong.
I couldn't find any issues with the log I looked at. It seemed to compile
normally.
(https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/open
