View previous topic :: View next topic |
Author |
Message |
cmodyssey
Joined: 28 Mar 2008 Posts: 63
|
Posted: Mon Jul 19, 2010 12:33 pm Post subject: Problem building ezstream on Linux |
|
|
Hi,
I have downloaded ezstream from http://downloads.xiph.org/releases/ezstream/ezstream-0.5.6.tar.gz
When I run the configure script, I get the following:
Code: |
checking for a BSD-compatible install... /usr/bin/install -c
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
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 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 AIX... no
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 minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking for fgrep... /bin/grep -F
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking whether to enable debugging... no
checking if gcc -std=gnu99 understands -fstack-protector... yes
checking if gcc -std=gnu99 understands -fstrict-aliasing... yes
checking if gcc -std=gnu99 understands -Wall... yes
checking if gcc -std=gnu99 understands -W... yes
checking if gcc -std=gnu99 understands -Wstrict-aliasing... yes
checking if gcc -std=gnu99 understands -Wwrite-strings... yes
checking if gcc -std=gnu99 understands -Wpointer-arith... yes
checking if gcc -std=gnu99 understands -Wshadow... yes
checking if gcc -std=gnu99 understands -Wconversion... yes
checking if gcc -std=gnu99 understands -Wcast-qual... yes
checking if gcc -std=gnu99 understands -Wcast-align... yes
checking if gcc -std=gnu99 understands -Wbounded... no
checking if gcc -std=gnu99 understands -Wmissing-declarations... yes
checking if gcc -std=gnu99 understands -Wmissing-prototypes... yes
checking if gcc -std=gnu99 understands -Wstrict-prototypes... yes
checking if gcc -std=gnu99 understands -Wformat=2... yes
checking for an ANSI C-conforming const... yes
checking for working volatile... yes
checking for sys/time.h... yes
checking for signal.h... yes
checking for langinfo.h... yes
checking for libgen.h... yes
checking for locale.h... yes
checking for paths.h... yes
checking for size_t... yes
checking for ssize_t... yes
checking for basename in -lgen... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking shout/shout.h usability... yes
checking shout/shout.h presence... yes
checking for shout/shout.h... yes
checking if libshout works... no
checking for libshout ... no
configure: error: libshout 2.2.x is required.
|
I do have libshout 2.2 installed, as the rpm query command shows:
Code: |
[root@richt02 ezstream-0.5.6]# rpm -qa | grep shout
libshout-2.2.2-2.el5.rf
libshout-devel-2.2.2-2.el5.rf
|
Does anybody have any ideas why I have this problem please.
Thanks,
Richard. |
|
Back to top |
|
|
cmodyssey
Joined: 28 Mar 2008 Posts: 63
|
Posted: Sat Jul 24, 2010 8:38 pm Post subject: |
|
|
I've been in touch with the author and he's kindly helped me out and I've built this successfully now.
It turns out that there is some important information in a log file that the configure script produces, which is called "config.log"
The critical section of the config.log was showing as follows:
Code: |
configure:5902: $PKG_CONFIG --exists --print-errors "shout"
Package theora was not found in the pkg-config search path.
Perhaps you should add the directory containing `theora.pc'
to the PKG_CONFIG_PATH environment variable
Package 'theora', required by 'Shout', not found
|
What the above is suggesting is that my libshout was built with Theora support and consequently has additional dependencies. These being libtheora and libtheora-devel.
So I installed libtheora-devel and then the configure script worked with no errors, so did make and make install
I figured that updating this thread with the solution would be good in case there is someone else out there that ends up with the same problem. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2002 phpBB Group subRebel style by ktauber
|