protux-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Protux-devel] how to compile libmustux-0.15.5.tar.gz ?


From: Luciano Giordana
Subject: Re: [Protux-devel] how to compile libmustux-0.15.5.tar.gz ?
Date: Mon, 21 Oct 2002 15:25:31 -0200
User-agent: KMail/1.4.3

> > because the libmustux-0.15.5.tar.gz file containing no admin dir.

libmustux 0.15.5 is deprecated
try 0.15.51

> Furhter, when I tried to compile protux-0.15.5 without libmustux 

this is impossible

(what
> libmustux must do for protux, BTW?)

it is everything ! :-) the JMB is in libmustux, for example
the MustuxDrawable class, that is the super class for all graphic component in 
protux is also in libmustux
The hardware level dsp calls is in libmustux,

in few words, almost 50% of protux is inside libmustux 

[]s



> I got error when executing ./configure
>
> loading cache ./config.cache
> checking for Cygwin environment... (cached) no
> checking for mingw32 environment... (cached) no
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
> checking build system type... i686-pc-linux-gnu
> checking for a BSD compatible install... (cached) /usr/bin/install -c
> checking for -p flag to install... yes
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... (cached) yes
> checking for working aclocal-1.4... missing
> checking for working autoconf... missing
> checking for working automake-1.4... missing
> checking for working autoheader... missing
> checking for working makeinfo... missing
> checking for gcc... (cached) gcc
> checking whether the C compiler (gcc   ) works... yes
> checking whether the C compiler (gcc   ) is a cross-compiler... no
> checking whether we are using GNU C... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking how to run the C preprocessor... (cached) gcc -E
> checking for c++... (cached) c++
> checking whether the C++ compiler (c++   ) works... yes
> checking whether the C++ compiler (c++   ) is a cross-compiler... no
> checking whether we are using GNU C++... (cached) yes
> checking whether c++ accepts -g... (cached) yes
> checking whether c++ supports -fno-exceptions... (cached) yes
> checking whether c++ supports -fno-check-new... (cached) yes
> checking whether c++ supports -fexceptions... (cached) yes
> checking how to run the C++ preprocessor... (cached) c++ -E
> checking whether c++ supports -frepo... (cached) yes
> checking for ld used by GCC... (cached) /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
> checking for /usr/bin/ld option to reload object files... (cached) -r
> checking for BSD-compatible nm... (cached) /usr/bin/nm -B
> checking whether ln -s works... (cached) yes
> checking how to recognise dependant libraries... (cached) pass_all
> checking for object suffix... (cached) o
> checking for executable suffix... (cached) no
> checking for ranlib... (cached) ranlib
> checking for strip... (cached) strip
> loading cache ./config.cache within ltconfig
> checking whether -lc should be explicitly linked in... (cached) yes
> checking for objdir... .libs
> checking for gcc option to produce PIC...  -fPIC -DPIC
> checking if gcc PIC flag  -fPIC -DPIC works... (cached) yes
> checking if gcc static flag -static works... (cached) yes
> finding the maximum length of command line arguments... (cached) 73729
> checking if gcc supports -c -o file.o... (cached) yes
> checking if gcc supports -fno-rtti -fno-exceptions ... yes
> checking whether the linker (/usr/bin/ld) supports shared libraries... yes
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking command to parse /usr/bin/nm -B output... ok
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> creating libtool
> loading cache ./config.cache
> loading cache ./config.cache within ltconfig
> checking host system type... i686-pc-linux-gnu
> checking build system type... i686-pc-linux-gnu
> ltcf-cxx: with_gcc=yes ; with_gnu_ld=yes
> checking for objdir... .libs
> checking for c++ option to produce PIC... -fPIC -DPIC
> checking if c++ PIC flag -fPIC -DPIC works... yes
> checking if c++ static flag -static works... yes
> finding the maximum length of command line arguments... (cached) 73729
> checking if c++ supports -c -o file.o... (cached) yes
> checking if c++ supports -fno-rtti -fno-exceptions ... yes
> checking whether the linker (/usr/bin/ld) supports shared libraries... yes
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking command to parse /usr/bin/nm -B output... ok
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> appending configuration tag "CXX" to libtool
> checking for msgfmt... msgfmt
> checking for gmsgfmt... msgfmt
> found msgfmt program is not GNU msgfmt; ignore it
> checking for xgettext... :
> checking for main in -lutil... yes
> checking for main in -lcompat... no
> checking for crypt in -lcrypt... yes
> checking for socklen_t... socklen_t
> checking for dnet_ntoa in -ldnet... no
> checking for dnet_ntoa in -ldnet_stub... no
> checking for inet_ntoa... yes
> checking for connect... yes
> checking for remove... yes
> checking for shmat... yes
> checking for res_init... no
> checking for killpg in -lucb... no
> checking size of int... 4
> checking size of long... 4
> checking size of char *... 4
> checking size of char... 1
> checking for dlopen in -ldl... yes
> checking for shl_unload in -ldld... no
> checking for extra includes... no
> checking for extra libs... no
> checking for libz...
> configure: error: not found. Check your installation and look into
> config.log.
>
> What should I do now?





reply via email to

[Prev in Thread] Current Thread [Next in Thread]