Skip to main content.
home | support | download

Back to List Archive

SORRY-Resend (now in plaintext) "/lib/cpp" fails sanity check

From: Jeffrey Isherwood <ish(at)>
Date: Thu Aug 14 2003 - 14:04:32 GMT
I'm trying to build and install swish-e on a testbed webserver for later
deployment, and am not all that experienced with some of this stuff.  I =
downloaded the swish-e-2.2.3 and swish-e-2.4.0-pr1 but can get neither =

The platform is a redhat 8.0 with apache running on it.  Below is what I =
when I type ./configure, and attached is the 'config.log' file, has =
anyone seen
the cpp fails sanity check error before?  and if so, how do I fix it?  =
never seen a sanity check failure...


[root@testbed swish-e-2.4.0-pr1]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i586-pc-linux-gnu
checking host system type... i586-pc-linux-gnu
checking for style of include used by make... GNU
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...=20
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 dependency style of gcc... gcc3
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 for a sed that does not truncate output... /bin/sed
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
Received on Thu Aug 14 14:04:43 2003