Re: [squid-users] Squid configure script error

These types of symptoms (segmentation faults/coredumps at different
places when trying to compile programs) is usually a sign of a hardware
error, usually broken memory or overheated CPU.

I would recommend to run a test of your hardware by using Memtest86
<url:http://www.memtest86.com/> and other good hardware test programs.

Regards
Henrik

Eduardo Bejar wrote:
>
> Hi,
>
> I´ve been trying to compile squid to install it on a RedHat 7.1 server to
> work as a transparent proxy, but the configure scripts shows me an error.
> Although it seems not to be an error from the script itself, I don´t know
> how to fix it. I´ve been googleing for a while and haven´t found anything. I
> entered some chat rooms to ask but didn´t got any useful answer. I tryed
> reinstalling gcc, glibc, glibc-dev, cpp but still get the same
> issue.
>
> Please send me any comments or ideas on why does this happens and how should
> I fix it.
>
> Here´s what happens when I run ./configure for the first time:
>
> # ./configure --enable-linux-netfilter
> loading cache ./config.cache
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for mawk... no
> checking for gawk... gawk
> checking whether make sets ${MAKE}... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking whether the C compiler (gcc -g) works... yes
> checking whether the C compiler (gcc -g) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... none
> checking whether gcc and cc understand -c and -o together... no
> checking host system type... cfgaux/config.guess: line 1: 16655 Aborted
> (core dumped) ( $c $dummy.c -c -o $dummy.o ) >/dev/null 2>&1
> cfgaux/config.guess: line 1: 16657 Aborted (core dumped) (
> $c $dummy.c -c -o $dummy.o ) >/dev/null 2>&1
> i686-pc-linux-gnu
> checking for Cygwin environment... no
> checking for mingw32 environment... no
> checking for executable suffix... no
> checking for object suffix... configure: error: installation or
> configuration problem; compiler does not work
>
> If I run again ./configure I get this:
> #./configure --enable-linux-netfilter
> loading cache ./config.cache
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for mawk... no
> checking for gawk... gawk
> checking whether make sets ${MAKE}... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking whether the C compiler (gcc -g) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
>
> config.log shows this:
>
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> configure:782: checking for a BSD compatible install
> configure:835: checking whether build environment is sane
> configure:906: checking for mawk
> configure:906: checking for gawk
> configure:936: checking whether make sets ${MAKE}
> configure:1057: checking whether to enable maintainer-specific portions of
> Makefiles
> configure:1089: checking for gcc
> configure:1202: checking whether the C compiler (gcc -g) works
> configure:1218: gcc -o conftest -g conftest.c 1>&5
> ./configure: line 1: 16933 Aborted (core dumped) ${CC-cc} -o
> conftest${ac_exeext} $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS 1>&5
> configure: failed program was:
>
> #line 1213 "configure"
> #include "confdefs.h"
>
> main(){return(0);}
>
> Please any idea will be very helpful.
>
> Edo
Received on Tue Mar 18 2003 - 15:34:54 MST