I see that also, What I am testing now, it downgrading gcc to the sarge versions. If it works on testing then I know it's a gcc issue.
Jim ---------- Original Message ----------- From: Kurt Roeckx <[EMAIL PROTECTED]> To: Stefan Kaltenbrunner <[EMAIL PROTECTED]> Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, [EMAIL PROTECTED] Sent: Mon, 9 Jan 2006 16:57:36 +0100 Subject: Re: [HACKERS] Fw: Is anyone interested in getting PostgreSQL working > On Mon, Jan 09, 2006 at 03:03:28PM +0100, Stefan Kaltenbrunner wrote: > > > > > >well that is good news, can you tell me what version of linux you are > > >using and what gcc version also. I will let > > >Martin know. > > > > > > lionfish is a stock Debian/Sarge box (a cobalt cube) with gcc 3.3.5. > > Martin is probably trying this on unstable, which means new > binutils, glibc and gcc-3.3. > > Toolchain looks like this on unstable: > libc6-dev 2.3.5-11 > linux-kernel-headers 2.6.13+0rc3-2 > binutils 2.16.1cvs20051214-1 > gcc-3.3 3.3.6-12 > gcc-3.4 3.4.5-1 > gcc-4.0 4.0.2-6 > > Where stable/sarge has: > libc6-dev 2.3.2.ds1-22 > linux-kernel-headers 2.5.999-test7-bk-17 > binutils 2.15-6 > gcc-3.3 3.3.5-13 > gcc-3.4 3.4.3-13 (which you probably don't use) > > Kurt > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend ------- End of Original Message ------- ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org