check for build tools
checking for autoconf >= 2.52 … found 2.61, ok.
checking for automake >= 1.7 … found 1.8.5, ok.
checking for libtoolize >= 1.5.0 … found 1.5.26, ok.
checking for pkg-config >= 0.8.0 … found 0.21, ok.
running aclocal -I common/m4 …
running libtoolize --copy --force…
Putting files in AC_CONFIG_AUX_DIR, `config’.
running autoheader …
running autoconf …
running automake -a -c…
skipping configure stage for package gst-openmax, as requested.
autogen.sh done.
[sbox-armv7: ~/gst-openmax] > ./configure --prefix=/usr
checking for a BSD-compatible install… /scratchbox/tools/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking whether make sets $(MAKE)… yes
checking whether to enable maintainer-specific portions of Makefiles… no
checking for gcc… gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… configure: error: cannot run C compiled programs.
If you meant to cross compile, use --host'. See config.log’ for more details.
[sbox-armv7: ~/gst-openmax] >
For armv7 scratchbox environment I executed the shell script given in 13986’s gists · GitHub
while compiling gst-openmax in scratch box i got the following error
[snip]
[sbox-armv7: ~/gst-openmax] > ./configure --prefix=/usr
checking for a BSD-compatible install... /scratchbox/tools/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
Could tell us what the details (most likely a compiler error)
mentioned here are?
[sbox-armv7: ~/gst-openmax] >
plese help me regarding this issue
The problem could be any of:
- your compiler producing bad code (unlikely)
- your CPU transparency setup being broken (usually the case with
such errors, but the script you used seemed ok)
- your qemu version not being able to run the binary (possible, but
these days should happen less and less)
Hi all
The following error occured while compiling gst-openmax in scratchbox…
[sbox-armv7: ~/gst-openmax] > ./configure --prefix=/usr
checking for a BSD-compatible install… /scratchbox/tools/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking whether make sets $(MAKE)… yes
checking whether to enable maintainer-specific portions of Makefiles… no
checking for gcc… gcc
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 gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for style of include used by make… GNU
checking dependency style of gcc… gcc3
checking whether gcc and cc understand -c and -o together… yes
checking for a BSD-compatible install… /scratchbox/tools/bin/install -c
checking build system type… arm-unknown-linux-gnueabi
checking host system type… arm-unknown-linux-gnueabi
checking for a sed that does not truncate output… /scratchbox/tools/bin/sed
checking for grep that handles long lines and -e… /scratchbox/tools/bin/grep
checking for egrep… /scratchbox/tools/bin/grep -E
checking for ld used by gcc… /scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld
checking if the linker (/scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld) is GNU ld… yes
checking for /scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld option to reload object files… -r
checking for BSD-compatible nm… /scratchbox/compilers/bin/nm -B
checking whether ln -s works… yes
checking how to recognize dependent libraries… pass_all
checking how to run the C preprocessor… gcc -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 dlfcn.h usability… yes
checking dlfcn.h presence… yes
checking for dlfcn.h… yes
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++… gcc3
checking how to run the C++ preprocessor… g++ -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… 98304
checking command to parse /scratchbox/compilers/bin/nm -B output from gcc object… ok
checking for objdir… .libs
checking for ar… ar
checking for ranlib… ranlib
checking for strip… strip
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC
checking if gcc PIC flag -fPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking whether the gcc linker (/scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
configure: creating libtool
appending configuration tag “CXX” to libtool
checking for ld used by g++… /scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld
checking if the linker (/scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld) is GNU ld… yes
checking whether the g++ linker (/scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld) supports shared libraries… yes
checking for g++ option to produce PIC… -fPIC
checking if g++ PIC flag -fPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking whether the g++ linker (/scratchbox/compilers/cs2007q3-glibc2.5-arm7/arm-none-linux-gnueabi/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs… immediate
appending configuration tag “F77” to libtool
checking for check named check_pic - version >= 0.8.2… no
*** Could not run check test program, checking why…
*** The test program failed to compile or link. See the file config.log for
*** the exact error that occured.
checking for check named check - version >= 0.8.2… no
*** Could not run check test program, checking why…
*** The test program failed to compile or link. See the file config.log for
*** the exact error that occured.
configure: error: check not found
[sbox-armv7: ~/gst-openmax] >
You need all the dependencies, if 'check' is not found, you need to
install 'check'.
It looks a little misleading because of the name of the dependency,
but you can google for 'libcheck'. Alternatively you can edit the
configure script and remove the 'check' stuff.