Re: configure can't detect proper pthread flags

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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 18:51:25
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

>>>>> "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)

Andrew (irc:RhodiumToad)

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-03-20 19:15:07 Order of enforcement of CHECK constraints?
Previous Message Tom Lane 2015-03-20 18:50:19 Re: inherit support for foreign tables