Peter Eisentraut wrote:
> alex avriette writes:
>
> > Is it worth warning the user that you cannot use gcc as ld on Irix?
>
> You cannot use gcc as ld on any system.
Erm, perhaps not, but you can use it as the link step (both to
generate executables and to generate shared objects) on many system
alex avriette writes:
> Is it worth warning the user that you cannot use gcc as ld on Irix?
You cannot use gcc as ld on any system.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
htt
Disregard previous. Using /bin/ld (with LDREL = -r) works fine as a
linker. Call it force of habit.
Is it worth warning the user that you cannot use gcc as ld on Irix? I
used it because I figured I would need gnu ld (which I of course didn't
have).
Anyhow, 7.3.1 is successfully built.
Alex
When compiled with gcc, it does trap divide by zero.
Alex
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
alex avriette <[EMAIL PROTECTED]> writes:
> I've got a 6-way SGI Challenge L with R4400/200 cpu's in it, and a gig
> of interleaved ram. I am running postgres 7.3.1, which I compiled
> 64-bit with MIPSPro.
> I'm finding that the Sparc 20 is about twice as fast as the Challenge.
I'm betting tha
I have tried, without any luck, to get postgres compiled with gcc 3.2
(from freeware.sgi.com). It keeps adding '-r' when its linking, even
when LDFLAGS is unset, LD is 'gcc' and CC is 'gcc'. I could do the
linking manually, but this is not really a viable option for a >
release.
Looking at thi
I've got a 6-way SGI Challenge L with R4400/200 cpu's in it, and a gig
of interleaved ram. I am running postgres 7.3.1, which I compiled
64-bit with MIPSPro. The database is living on an ultrawide scsi raid.
I am also running postgres on a 2-cpu (85mhz) Sparc 20 with 384mb of
ram, and the datab
