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

Re: ./configure



Your missing something. A "sanity" check checks for the tools needed to
build a software package. I'm not sure what it is but your missing
something. Try to look at any deps. you need for it and make sure their
installed. 
	-- Kyle

On Thu, 2005-03-10 at 20:14 -0600, bntly_rhds wrote:
> i'm trying to ./configure imlib2 on my computer, do you guys know (by 
> reading the following), why it is failing?  for some reason i decided to 
> do "yum install gcc" and it automagically installed gcc.  so now i can 
> compile stuff and basically make and make install stuff.  but i can't 
> get this one thing to install ... err ... ./configure.
> 
> 
> [root@localhost DR17.1]# cd imlib*
> [root@localhost imlib2-1.1.2]# ls
> aclocal.m4    config.sub    filters           ltmain.sh      src
> AUTHORS       configure     imlib2-config.in  Makefile.am    stamp-h.in
> ChangeLog     configure.in  imlib2.pc.in      Makefile.in    test
> config.guess  COPYING       imlib2.spec       missing        TODO
> config.h.in   demo          install-sh        mkinstalldirs
> config.log    doc           loaders           README
> [root@localhost imlib2-1.1.2]# ./configure
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-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 ANSI C... none needed
> checking for strerror in -lcposix... no
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets $(MAKE)... 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 whether byte ordering is bigendian... no
> 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 ANSI C... (cached) none needed
> checking for gcc option to accept ANSI C... none needed
> checking how to run the C preprocessor... gcc -E
> checking for egrep... grep -E
> checking for ANSI C header files... yes
> checking for an ANSI C-conforming const... yes
> checking for a sed that does not truncate output... /bin/sed
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> 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++... no
> checking for c++... no
> checking for gpp... no
> checking for aCC... no
> checking for CC... no
> checking for cxx... no
> checking for cc++... no
> checking for cl... no
> checking for FCC... no
> checking for KCC... no
> checking for RCC... no
> checking for xlC_r... no
> checking for xlC... no
> checking whether we are using the GNU C++ compiler... no
> checking whether g++ accepts -g... no
> checking how to run the C++ preprocessor... /lib/cpp
> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details.
> 

-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.