Re: configure can't detect proper pthread flags

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: Max Filippov <jcmvbkbc(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Peter Seiderer <ps(dot)report(at)gmx(dot)net>
Subject: Re: configure can't detect proper pthread flags
Date: 2015-03-20 22:44:11
Message-ID: CA+Tgmoaha4Zg94qWR==tV26WDQeuXLCVjWHOuR0+a3XDOnswEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 20, 2015 at 2:51 PM, Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>>>>>> "Robert" == Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> >> Then maybe stderr tests should grep output for a specific option,
> >> the one we're currently testing, not just any noise?
>
> Robert> That sounds awfully fragile to me. It can't really be safe to
> Robert> assume we know precisely what the warning messages will look
> Robert> like.
>
> But how safe is it to assume that a warning message about option '-foo'
> will contain the string '-foo' in it somewhere?
>
> (though the trace output from -x still should be dealt with separately)

I wouldn't like to bet on it. I mean, if the world weren't full of
weird platforms that behave in crazy, messed-up ways, autoconf output
wouldn't look like like noise.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-03-20 23:00:59 Re: Change of pg_ctl's default shutdown method
Previous Message Bruce Momjian 2015-03-20 22:35:49 Re: PITR failing to stop before DROP DATABASE