From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "kanchana" <pkkanchana(at)gmx(dot)net>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Fw: configure error with krb5 |
Date: | 2003-01-23 21:07:28 |
Message-ID: | 87y95bshgv.fsf@stark.dyndns.tv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> "kanchana" <pkkanchana(at)gmx(dot)net> writes:
> > gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/
> > include -I/home/saratha/krb5/include -I/usr/local/ssl/include -c -o float.o
> > float.c
> > float.c: In function `float4out':
> > float.c:233: Internal compiler error in emit_move_insn, at expr.c:2739
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>
> Please observe that gcc's failure message tells you to report it to the
> gcc project. This is not Postgres' problem.
If you see the same bug repeatably it's a gcc bug. but if you see a different
message each time you try to compile it's more likely you have bad memory in
the machine. It's worth running a memory checker like memtest86 anyways, it
can't hurt. Bad memory is really quite common.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | will trillich | 2003-01-23 21:07:49 | Re: three timestamps/table, use of 'now' in table creation statement |
Previous Message | Luke Pascoe | 2003-01-23 20:57:04 | Re: I was spoiled by the MySQL timestamp field |