FC3 & irssi install probs

[Paul Howarth]

On Fri, 2005-01-28 at 12:19 -0700, Mike Hoy wrote:
> > What instructions don't say, because it is assumed, is that if you 
> > want to compile anything, you need to have compiler install.  Install 
> > gcc package(s) *and* development libraries (if you don't have compiler 
> > installed, chances are you don't have devel packages installed either).
> 
> i did #yum install gcc
> 
> and it completed.
> 
> it had dep's:
> Performing the following to resolve dependencies:
>   Install: glibc-devel.i386 0:2.3.4-2.fc3
>   Install: glibc-headers.i386 0:2.3.4-2.fc3
> 
> and i allowed them to be installed.
> 
> #./configure in the irrssi** directory still doesn't work.
> here's the output from ./configure:
> 
> 
> [root at localhost irssi-0.8.9]# ./configure
> 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 to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking for C compiler default output... 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 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 how to run the C preprocessor... gcc -E
> checking for egrep... grep -E
> checking for ANSI C header files... yes
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> 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.
> 
> what am i missing?

You're trying to build a C++ program it seems.

# yum install gcc-c++

You should also check the build instructions for the package you're
trying to build as it may mention further dependencies.

Paul.
-- 
Paul Howarth <paul at city-fan.org>