Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-20 Thread Belbin, Peter
Title: RE: [BUGS] solaris 10 with gcc 3.3.2 Tom, Yeah, I've already fired off a query about this gcc build to the source. In my case, I downloaded it from www.sunfreeware.com, and, for good measure, I also tried gcc 3.4.2 for solaris 9, on a solaris 10 box, and, indeed, it looks lik

Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-20 Thread Belbin, Peter
Title: RE: [BUGS] solaris 10 with gcc 3.3.2 I got a response from Steve (of SunFreeware) and he also has put some info up on the site about regenerating the cleaned-up files. I've done this with the gcc 3.3.2 for solaris 10, and have now successfully built postgresql rc1. I haven&#x

Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-18 Thread Mike Mascari
Mike Mascari wrote: Tom Lane wrote: I wrote: This is standard practice for gcc: it tries to use "cleaned up" versions of system headers that will not elicit useless warnings from gcc. It's a good idea, actually, because the degree of insanity in vendor-supplied system headers is pretty depres

Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-18 Thread Mike Mascari
Tom Lane wrote: I wrote: This is standard practice for gcc: it tries to use "cleaned up" versions of system headers that will not elicit useless warnings from gcc. It's a good idea, actually, because the degree of insanity in vendor-supplied system headers is pretty depressing. But if the gcc

Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-17 Thread Tom Lane
I wrote: > This is standard practice for gcc: it tries to use "cleaned up" versions > of system headers that will not elicit useless warnings from gcc. It's > a good idea, actually, because the degree of insanity in vendor-supplied > system headers is pretty depressing. But if the gcc install pro

Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-17 Thread Tom Lane
"Belbin, Peter" <[EMAIL PROTECTED]> writes: > It seems that rather than using the /usr/include/sys/types.h, gcc 3.3.2 is > instead, using a version of the same file, located at > /usr/local/lib/gcc-lib/sparc-sun-solaris2.10/3.3.2/include/sys, which does > not have a definition for ctid_t This is s

Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-17 Thread Belbin, Peter
Title: RE: [BUGS] solaris 10 with gcc 3.3.2 It seems that rather than using the /usr/include/sys/types.h, gcc 3.3.2 is instead, using a version of the same file, located at /usr/local/lib/gcc-lib/sparc-sun-solaris2.10/3.3.2/include/sys, which does not have a definition for ctid_t Presumedly

Re: [BUGS] solaris 10 with gcc 3.3.2

2004-12-11 Thread Tom Lane
"Belbin, Peter" <[EMAIL PROTECTED]> writes: > Should I be able to compile with gcc 3.3.2 (from sunfreeware) on solaris 10? Yes ... > gcc -DPOSIX -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels > -fno-strict-aliasing -I../../src/port -DFRONTEND -I../../src/include -c -o > exec.o exec.c

[BUGS] solaris 10 with gcc 3.3.2

2004-12-06 Thread Belbin, Peter
Should I be able to compile with gcc 3.3.2 (from sunfreeware) on solaris 10?   I'm using sparc, and am getting some strange looking compiler errors when trying to do the make.   I'm getting some compiler parse errors when compiling exec.c.       make -C doc allmake[1]: Entering directory `