Re: failing to build preproc.c on solaris with sun studio

From: Andres Freund <andres(at)anarazel(dot)de>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: failing to build preproc.c on solaris with sun studio
Date: 2022-08-07 00:43:50
Message-ID: 20220807004350.j5t2dplpy2ew2i4h@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-08-06 17:25:52 -0700, Noah Misch wrote:
> On Sat, Aug 06, 2022 at 08:05:14PM -0400, Tom Lane wrote:
> > Andres Freund <andres(at)anarazel(dot)de> writes:
> > > Yikes. And it's not like newer compiler versions are likely to be forthcoming
> > > (12.6 is newest and is from 2017...). Wonder if we should just require gcc on
> > > solaris... There's a decent amount of stuff we could rip out in that case.
> >
> > Seems like it's only a matter of time before we add enough stuff to
> > the grammar that the build fails, period.
>
> I wouldn't worry about that enough to work hard in advance. The RAM usage can
> grow by about 55% before that's a problem. (The 14G ulimit can tolerate a
> raise.) By then, the machine may be gone or have more RAM. Perhaps even
> Bison will have changed its code generation. If none of those happen, I could
> switch to gcc, hack things to use gcc for just preproc.o, etc.

Sure, we can hack around it in some way. But if we need such hackery to
compile postgres with a compiler, what's the point of supporting that
compiler? It's not like sunpro provides with awesome static analysis or such.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2022-08-07 00:59:54 Re: failing to build preproc.c on solaris with sun studio
Previous Message Andres Freund 2022-08-07 00:42:19 Re: failing to build preproc.c on solaris with sun studio