Skip site navigation (1) Skip section navigation (2)

Re: solaris 10 with gcc 3.3.2

From: "Belbin, Peter" <PBelbin(at)McLeodUSA(dot)com>
To: 'Mike Mascari' <mascarm(at)mascari(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: solaris 10 with gcc 3.3.2
Date: 2004-12-20 15:56:46
Message-ID: DAC7935736BD9F4AAC601EE021D1B23403D4C19F@txhouexch01.mcld.net (view raw or flat)
Thread:
Lists: pgsql-bugs
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't tried executing it yet, but at least it's built without
complaints.

Thank you for your help.

regards,
Peter.




 

-----Original Message-----
From: Mike Mascari [mailto:mascarm(at)mascari(dot)com] 
Sent: Saturday, December 18, 2004 5:03 AM
To: Tom Lane
Cc: Belbin, Peter; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] solaris 10 with gcc 3.3.2

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 depressing.  But if the gcc 
>>> install process generated an invalid "cleanup" file then you need to 
>>> take that up with the gcc boys, not us.
>>>   
>>
>>
>> On rereading this, a nearly-dead neuron fired --- I have seen 
>> problems of this sort arise when someone took a gcc installation 
>> generated on NiftyVendorUnix M.N and copied it verbatim to
NiftyVendorUnix M.N+1,
>> or indeed any release other than M.N.   
>>
> That nearly-dead neuron has value. The problem is that most people are 
> getting the Solaris 10 beta builds whose headers conflict with the gcc
> 3.3.2 package's 'adapted' headers they are acquiring from 
> sunfreeware.com, which, along with distributing other binary packages, 
> is the place referred to by gcc.gnu.org for pre-built Solaris 
> binaries. All the original poster needs to do is rebuild the gcc's 
> 'adapted' headers with:
>
> # cd /usr/local/lib/gcc-lib/i386-pc-solaris2.10/3.3.2/install-tools
> # ./mkheaders
>
> and they should be good to go....

Actually, I see the original poster is on SPARC, so the correct path to the
'mkheaders' utility is probably going to be:

# cd /usr/local/lib/gcc-lib/sparc-sun-solaris2.10/3.3.2/install-tools
# ./mkheaders

Mike Mascari



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.



pgsql-bugs by date

Next:From: Tony CadutoDate: 2004-12-20 16:27:20
Subject: problem with 8.0rc1 not using indexes(solved)
Previous:From: Tom LaneDate: 2004-12-20 15:12:46
Subject: Re: 8.0.0rc1 on hppa2.0w-hp-hpux11.00

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group