[Bug 2929] configure: error: "A JDK home directory could not be found."

bugzilla-daemon at icedtea.classpath.org bugzilla-daemon at icedtea.classpath.org
Tue Apr 12 09:53:47 UTC 2016


http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2929

--- Comment #2 from yugiohjcj at 1s.fr ---
Nice, indeed it works:
$ ./configure --prefix=/usr --with-jdk-home=/usr/lib/jvm
checking for a BSD-compatible install... /bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... yes
checking which branch and release of IcedTea is being built... branch 2.6,
release 2.6.4 for OpenJDK 1.7.0
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking for gmake... /usr/bin/gmake
checking for gzip... /bin/gzip
checking for ant...
/home/yugiohjcj/documents/downloads/software/apache-ant-1.9.4/bin/ant
checking for gfind... no
checking for find... /usr/bin/find
checking for gpatch... no
checking for patch... /usr/bin/patch
checking for gtar... no
checking for tar... /bin/tar
checking for chmod... /bin/chmod
checking for gsha256sum... no
checking for sha256sum... /bin/sha256sum
checking for wget... /usr/bin/wget
checking for zip... /usr/bin/zip
checking for unzip... /usr/bin/unzip
checking for cpio... /bin/cpio
checking for file... /usr/bin/file
checking for readlink... /bin/readlink
checking for fastjar... /usr/bin/fastjar
checking for gsed... no
checking for sed... /bin/sed
checking for ldd... ldd
checking for gawk... /bin/gawk
checking for hg... /usr/bin/hg
checking for an OpenJDK source directory... /tmp/build/icedtea-2.6.4/openjdk
checking for IcedTea Mercurial revision ID... none
checking for JDK Mercurial revision ID... none
checking for HotSpot Mercurial revision ID... none
checking for lsb_release... no
checking whether to use CACAO as VM... no
checking whether to use JamVM as VM... no
checking whether to use the Shark JIT... no
checking if a native HotSpot port is available for this architecture... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether to use the zero-assembler port... no
checking whether byte ordering is bigendian... no
checking which HotSpot build to use... default
checking for linux32... /usr/bin/linux32
checking version of GCC... 5.3.0 (major version 5, minor version 3)
checking for getconf... /usr/bin/getconf
checking the number of online processors... 2
checking if cp supports --reflink... yes
checking if we can hard link rather than copy from /tmp/build/icedtea-2.6.4...
yes
checking whether to disable the execution of the JTReg tests... no
checking whether to disable the execution of the HotSpot JTReg tests... no
checking whether to disable the execution of the langtools JTReg tests... no
checking whether to disable the execution of the JDK JTReg tests... no
checking for system library directory... 
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether to enable the PKCS11 crypto provider using NSS... disabled by
default (edit java.security to enable)
checking for NSS... yes
checking whether to enable the Sun elliptic curve crypto provider... no
checking whether to build native code with debugging information... yes
checking whether to build Java bytecode with debugging information... yes
checking where fonts are stored... /usr/share/fonts
checking if /usr/share/fonts is a valid directory... yes
checking for xvfb-run... no
checking whether to build documentation... yes
checking for distribution package version... none
checking build identification... Custom build (Tue Apr 12 11:51:42 CEST 2016)
checking how many parallel build jobs to execute... 2
checking whether to build a bootstrap version first... yes
checking whether to download tarballs... yes
checking for a JDK home directory... /usr/lib/jvm
checking if a java binary was specified... no
checking if /usr/lib/jvm/bin/java is a valid executable file... yes
checking for an ecj JAR file... /usr/share/java/ecj.jar
checking if a javac binary was specified... no
checking if /usr/lib/jvm/bin/javac is a valid executable file... no
checking for javac... no
checking if an ecj binary was specified... no
checking if /usr/bin/ecj is a valid executable file... checking for ecj... no
checking for ecj-3.1... no
checking for ecj-3.2... no
checking for ecj-3.3... no
checking for ecj-3.4... no
checking whether to compile ecj natively... no
checking if we are using ecj as javac... no
checking if a javah executable is specified... no
checking if /usr/lib/jvm/bin/javah is a valid executable file... yes
checking if a jar executable is specified... no
checking if /usr/lib/jvm/bin/jar is a valid executable file... yes
checking whether jar supports @<file> argument... yes
checking whether jar supports stdin file arguments... yes
checking whether jar supports -J options at the end... yes
checking if an rmic executable is specified... no
checking if /usr/lib/jvm/bin/rmic is a valid executable file... yes
checking if a native2ascii binary was specified... no
checking if /usr/lib/jvm/bin/native2ascii is a valid executable file... yes
checking if we are using CACAO as the build VM... no
checking for xsltproc... /usr/bin/xsltproc
checking if the VM and compiler work together... configure: error: Compiler
failed to compile Java code.

Now, I will try to understand this new error.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20160412/9827b35c/attachment.html>


More information about the distro-pkg-dev mailing list