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/openjdk-1.8-linux-x86_64/107/consoleFull) /Magnus > 7 feb 2015 kl. 13:42 skrev Mani Sarkar <sadhak...@gmail.com>: > > Hi all, > > Although we are on OpenJDK9 and the AdoptOpenJDK build farms are already > producing binaries for it, we also have OpenJDK8 jobs that run occasionally > and these have been failing due to the below reasons: > > ## Starting jdk*/usr/bin/ld: cannot find -lasound* > collect2: error: ld returned 1 exit status > gmake[2]: *** > [/scratch/jenkins/workspace/openjdk-1.8-linux-x86_64/build/linux-x86_64-normal-server-release/jdk/lib/amd64/libjsoundalsa.so] > Error 1 > gmake[2]: *** Waiting for unfinished jobs.... > gmake[1]: *** [libs-only] Error 2 > make: *** [jdk-only] Error 2 > Package test output into archives... > /scratch/jenkins/workspace/openjdk-1.8-linux-x86_64 > Removing existing (old) artefact: > openjdk-1.8-linux-x86_64-jcov-testresults.tar.gz > Tarring and zipping the 'testoutput' folder into artefact: > openjdk-1.8-linux-x86_64-jcov-testresults.tar.gz > tar: testoutput: Cannot stat: No such file or directory > tar: Exiting with failure status due to previous errors > Moving artefact openjdk-1.8-linux-x86_64-jcov-testresults.tar.gz into > /scratch/jenkins/workspace/openjdk-1.8-linux-x86_64 > Archiving artifacts > ERROR: No artifacts found that match the file pattern > "openjdk-1.8-linux-x86_64-105.tar.gz". Configuration error?ERROR > <http://stacktrace.jenkins-ci.org/search?query=ERROR>: > ‘openjdk-1.8-linux-x86_64-105.tar.gz’ doesn’t match anything > Build step 'Archive the artifacts' changed build result to FAILURE > > > Even though asound has been installed at the start of the process. > > Here's the logs for more details - > https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/openjdk-1.8-linux-x86_64/ > > I could run the build in debug mode if the logs don't tell us enough. > > Cheers, > Mani > > -- > @theNeomatrix369 <http://twitter.com/theNeomatrix369>* | **Blog > <http://neomatrix369.wordpress.com>** | *LJC Associate & LJC Advocate > (@adoptopenjdk & @adoptajsr programs) > *Meet-a-Project - *MutabilityDetector > <https://github.com/MutabilityDetector>* | **Bitbucket > <https://bitbucket.org/neomatrix369>* * | **Github > <https://github.com/neomatrix369>* * | **LinkedIn > <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>* > *Come to Devoxx UK 2015:* http://www.devoxx.co.uk/ > > *Don't chase success, rather aim for "Excellence", and success will come > chasing after you!*