Date: Sun, 6 Feb 2005 07:22:48 -0500 From: "Grant Peel" <gpeel@thenetnow.com> To: "Loren M. Lang" <lorenl@alzatex.com> Cc: freebsd-questions@freebsd.org Subject: Re: Broken Comiler Message-ID: <028201c50c46$940840a0$6401a8c0@GRANT> References: <027301c50c43$5851b8a0$6401a8c0@GRANT> <20050206121849.GW8619@alzatex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, I sent the console output and forgot the config.log output....
Here it is...
# more config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:1638: checking host system type
configure:1726: checking for gcc
configure:1839: checking whether the C compiler (gcc ) works
configure:1855: gcc -o conftest conftest.c 1>&5
gcc: Internal compiler error: program cc1 got fatal signal 11
configure: failed program was:
#line 1850 "configure"
#include "confdefs.h"
main(){return(0);}
----- Original Message -----
From: "Loren M. Lang" <lorenl@alzatex.com>
To: "Grant Peel" <gpeel@thenetnow.com>
Cc: <freebsd-questions@freebsd.org>
Sent: Sunday, February 06, 2005 7:18 AM
Subject: Re: Broken Comiler
> On Sun, Feb 06, 2005 at 06:59:40AM -0500, Grant Peel wrote:
>> Hi all,
>>
>> A few weeks back, on of my raid drives cacked.
>>
>> Since then, I have not been able to comple anything. I get messages like:
>>
>> (example while trying to .configure php4.3.10).
>> loading cache ./config.cache
>> checking host system type... i386-unknown-freebsd4.4
>> checking for gcc... gcc
>> checking whether the C compiler (gcc ) works... no
>> configure: error: installation or configuration problem: C compiler
>> cannot
>> create executables.
>>
>> I tried to rebuild the compiler from ports, but it would no make
>> either...keeps telling me to set cc to a working compiler...
>>
>> Is there any way to fix this short of rebuilding the whole os? A bianary
>> compiler perhaps?
>
> I'm assuming that you can run gcc by hand just fine.
>
> There is a file created by configure called config.log showing
> information about what it's doing and any error messages it received.
> If you could look through that or post relavent portions, that might
> help track down the problem.
>
>>
>> -Grant
>>
>>
>>
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe@freebsd.org"
>
> --
> I sense much NT in you.
> NT leads to Bluescreen.
> Bluescreen leads to downtime.
> Downtime leads to suffering.
> NT is the path to the darkside.
> Powerful Unix is.
>
> Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
> Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?028201c50c46$940840a0$6401a8c0>