The error of compile gst-plugin-base-0.10.22
 

I need to compile a gst-plugin-base-0.10.22,when I run the configure script,it give a error like the following.I sure I have install the liboil-0.3.14 in my system(my system is mandriva 2009),I also install the gstreamer-0.10.22 .Why it always give this error?

How should I solve this problem,and can I avoid the configure check?

Thanks at first!

checking for a BSD-compatible install... /usr/bin/install -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 nano version... 0 (release)
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
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 dependency style of gcc... gcc3
checking for a sed that does not truncate output... ./configure: line 4483: echo: write error: Broken pipe
/bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/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 for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
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
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for VALGRIND... no
no
configure: Using GStreamer Base Plug-ins source release as package name
configure: Using Unknown package origin as package origin
configure: Using /usr/local/libexec/gst-install-plugins-helper as plugin install helper

configure: *** checking feature: building of plug-ins with external deps ***
configure: building external plug-ins

configure: *** checking feature: building of experimental plug-ins ***
configure: not building experimental plug-ins
checking whether byte ordering is bigendian... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for valgrind... no
checking whether to build gtk-doc documentation... no
checking for gtkdoc-check... no
configure: Looking for Python version >= 2.1
checking for python... /usr/bin/python
checking "/usr/bin/python":... okay
checking local Python configuration... looks good
checking whether to build plugin documentation... no (gtk-doc disabled or not available)
checking for cos in -lm... yes
checking for ANSI C header files... (cached) yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking winsock2.h usability... no
checking winsock2.h presence... no
checking for winsock2.h... no
checking for hstrerror... yes
checking process.h usability... no
checking process.h presence... no
checking for process.h... no
checking for sys/types.h... (cached) yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking for sys/stat.h... (cached) yes
checking for stdint types... stdint.h (shortcircuit)
make use of stdint.h in _stdint.h (assuming C99 compatible system)
checking for localtime_r... yes
checking for gmtime_r... yes
checking for FIONREAD in sys/ioctl.h... yes
checking for inline... inline
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for lrint... yes
checking for lrintf... yes
checking whether gcc implements __PRETTY_FUNCTION__... yes
checking whether gcc implements __FUNCTION__... yes
checking whether gcc implements __func__... yes
checking for GLIB... yes
checking for LIBOIL... no
configure: error: liboil-0.3.14 or later is required

Do you have the liboil development files installed? I don't know how Mandriva names them, but it would be something like liboil-dev or liboil-devel. Also, why don't you use your package manager to install gst-plugins-base?

I have download the liboix-0.3.14 and install it in my system.The question is ,what is the different between liboil-0.3.14 and the liboix development (liboix-devel)?I have made a search for the liboil-devel,but couldn't find any about liboil-devel,only liboix-0.3XX.Could you give me a download links about liboix-devel?

Since I want to cross-compile the gst-plugins-base-0.10.22 and then use in my arm platform,so I didn't used package manager to install it.I compile it in my host just check it.Before doing this,I have successfully cross compile the liboil-0.3.14.But I also couldn't cross compile the gst-plugins !

In my host, I have used the package manager to install the liboil-0.3.15,but when I compile it in my host,it always give this error.

You will probably have to point to the arm version of liboil,
when configuring 'gst-plugin-base', to make sure to use the
right version.
Better use 'arm-linux-gcc', else no cross compile.
.....