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

Re: solaris build problem with Sun compilers

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: stange(at)rentec(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-ports(at)postgresql(dot)org
Subject: Re: solaris build problem with Sun compilers
Date: 2006-05-18 16:02:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-ports
Alan Stange wrote:
> > Uh, are you saying our Solaris Sparc "cas" ASM is only going to work for
> > Solaris 11 tools?  That doesn't sound good.  We must have people using
> > earlier Solaris tools.
> No, I'm not saying that at all.
> I think I'm saying that cas is OK for any reasonable Solaris+Sparc+Sun 
> compiler combination.  It'll fail on any SuperSparc based hardware and 
> older compilers (more than ~5 years), but that's too bad.

Well, when you look at the cost/benefit of using cas vs. ldstub, it
seems logical to keep ldstub for those older platforms.

> I'm also saying that cas in not OK for any gcc+binutils combination.  As 
> far as I can tell, gcc is still building code for the v7 platform by 
> default.  It's possible to override this, but I don't think it's 
> something you can test for in the preprocessor.

OK, I added a comment that gcc generates sparcv7 binaries.

  Bruce Momjian

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-ports by date

Next:From: Eric MontagueDate: 2006-05-28 20:05:33
Subject: psql: krb5_sendauth: Bad application version was sent (via sendauth) - Windows 2000, MIT Kerberos, PG v 8.1.1
Previous:From: Alan StangeDate: 2006-05-18 13:09:24
Subject: Re: solaris build problem with Sun compilers

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