Re: configure can't detect proper pthread flags - Mailing list pgsql-hackers

From Robert Haas
Subject Re: configure can't detect proper pthread flags
Date
Msg-id CA+Tgmoaha4Zg94qWR==tV26WDQeuXLCVjWHOuR0+a3XDOnswEA@mail.gmail.com
Whole thread Raw
In response to Re: configure can't detect proper pthread flags  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
On Fri, Mar 20, 2015 at 2:51 PM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
>>>>>> "Robert" == Robert Haas <robertmhaas@gmail.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



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PITR failing to stop before DROP DATABASE
Next
From: Robert Haas
Date:
Subject: Re: Change of pg_ctl's default shutdown method