Hi Jeff,
    thanks for much for the reply. I was able to proceed, but i ran
into another problem. Here is the log, and I hope someone can help me
out since i am pretty new to linux(centos)

[r...@esxi-vm51 iulib]# ./build
which: no automake in (/opt/jdk/bin:/usr/kerberos/sbin:/usr/kerberos/
bin:/usr/
lo
cal/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:)
# running configure
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 for g++... g++
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 g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
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 ranlib... ranlib
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/wait.h that is POSIX.1 compatible... 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 float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for unistd.h... (cached) yes
checking for compress in -lz... yes
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking for png_sig_cmp in -lpng... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking for jpeg_std_error in -ljpeg... yes
checking for TIFFOpen in -ltiff... yes
checking for SDL_Init in -lSDL... no
checking for rotozoomSurface in -lSDL_gfx... no
checking how to run the C++ preprocessor... g++ -E
checking ffmpeg/avcodec.h usability... no
checking ffmpeg/avcodec.h presence... no
checking for ffmpeg/avcodec.h... no
checking ffmpeg/avformat.h usability... no
checking ffmpeg/avformat.h presence... no
checking for ffmpeg/avformat.h... no
checking linux/videodev2.h usability... yes
checking linux/videodev2.h presence... yes
checking for linux/videodev2.h... yes
checking for int64_t... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for dup2... yes
checking for memset... yes
checking for sqrt... yes
checking for strchr... yes
checking for strdup... yes
checking for strrchr... yes
configure: creating ./config.status
config.status: error: cannot find input file: Makefile.in
[r...@esxi-vm51 iulib]#


On Jun 15, 4:15 pm, Jeffrey Ratcliffe <[email protected]>
wrote:
> 2009/6/15 zhi <[email protected]>:
>
> > Package zlib-1.2.3-3.x86_64 already installed and latest version
> > Package zlib-1.2.3-3.i386 already installed and latest version
> > Nothing to do
>
> > Any suggestion?
>
> You probably need the -dev package for zlib as well.
>
> Regards
>
> Jeff
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"ocropus" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/ocropus?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to