Date: Mon, 14 Jan 2013 18:50:50 GMT From: William Dizon <wdchromium@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: java/175300: Jamvm fails to compile on ARM6 (raspberry-pi) Message-ID: <201301141850.r0EIooit029206@red.freebsd.org> Resent-Message-ID: <201301141900.r0EJ00u7075528@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 175300 >Category: java >Synopsis: Jamvm fails to compile on ARM6 (raspberry-pi) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-java >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 14 19:00:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: William Dizon >Release: 10.0-CURRENT >Organization: >Environment: FreeBSD raspberry-pi.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r244906M: Sat Jan 5 01:10:27 JST 2013 aoyama@fbs.local:/usr/obj-rpi-clang/arm.armv6/usr/src/sys/RPI-B-test12 arm >Description: Building jamvm-1.5.4 from ports fails on libffi. This is installed on an SD-card made specifically for use on the Raspberry Pi: http://www.peach.ne.jp/archives/rpi/ http://www.peach.ne.jp/archives/rpi/freebsd-pi-clang-20130105.img.gz `make` Output: root@raspberry-pi:/usr/ports/java/jamvm # make ===> jamvm-1.5.4 depends on executable: zip - found ===> jamvm-1.5.4 depends on executable: gmake - found ===> jamvm-1.5.4 depends on executable: pkgconf - found ===> jamvm-1.5.4 depends on shared library: ffi - found ===> Configuring for jamvm-1.5.4 ===> FreeBSD 10 autotools fix applied to /usr/ports/java/jamvm/work/jamvm-1.5.4/aclocal.m4 ===> FreeBSD 10 autotools fix applied to /usr/ports/java/jamvm/work/jamvm-1.5.4/configure ===> FreeBSD 10 autotools fix applied to /usr/ports/java/jamvm/work/jamvm-1.5.4/acinclude.m4 ===> FreeBSD 10 autotools fix applied to /usr/ports/java/jamvm/work/jamvm-1.5.4/libtool checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether gmake sets $(MAKE)... yes checking build system type... arm-portbld-freebsd10.0 checking host system type... arm-portbld-freebsd10.0 checking for style of include used by gmake... GNU checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking dependency style of cc... gcc3 checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... unknown checking how to run the C preprocessor... cpp 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 dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking dependency style of c++... gcc3 checking how to run the C++ preprocessor... c++ -E checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... (cached) 262144 checking command to parse /usr/bin/nm -B output from cc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if cc supports -fno-rtti -fno-exceptions... yes checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... no checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by c++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the c++ linker (/usr/bin/ld) supports shared libraries... no checking for c++ option to produce PIC... -fPIC checking if c++ PIC flag -fPIC works... yes checking if c++ static flag -static works... yes checking if c++ supports -c -o file.o... yes checking whether the c++ linker (/usr/bin/ld) supports shared libraries... no checking dynamic linker characteristics... no (cached) (cached) checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking dependency style of cc... (cached) gcc3 checking dependency style of cc... gcc3 checking for ecj... no checking for jikes... no checking for gcj... no checking for javac... no checking for pthread_self in -lthr... yes checking for fmod in -lm... yes checking for inflate in -lz... yes checking for ffi_call in -lffi... no ===> Script "configure" failed unexpectedly. Please report the problem to java@FreeBSD.org [maintainer] and attach the "/usr/ports/java/jamvm/work/jamvm-1.5.4/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg info -g -Ea). *** [do-configure] Error code 1 Stop in /usr/ports/java/jamvm. *** [build] Error code 1 Stop in /usr/ports/java/jamvm. `pkg info -g -Ea` output: root@raspberry-pi:/usr/ports/java/jamvm # /usr/local/sbin/pkg info -g -Ea gettext-0.18.1.1 gmake-3.82_1 libffi-3.0.9 libiconv-1.14 libtool-2.4.2 pkg-1.0.4_1 pkgconf-0.8.9 zip-3.0 `find /usr | grep libffi` output: /usr/local/info/libffi.info /usr/local/lib/libffi-3.0.9 /usr/local/lib/libffi-3.0.9/include /usr/local/lib/libffi-3.0.9/include/ffi.h /usr/local/lib/libffi-3.0.9/include/ffitarget.h /usr/local/lib/libffi.so.5 /usr/local/lib/libffi.so /usr/local/lib/libffi.la /usr/local/lib/libffi.a /usr/local/libdata/pkgconfig/libffi.pc [omitted all /usr/ports matches] >How-To-Repeat: from a newly dd'ed image: portsnap fetch portsnap extract portsnap update cd /usr/ports/java/jamvm make config-recursive make >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301141850.r0EIooit029206>