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+TgmobR6d9q_gdggTbBOpMwkJyhm+iYK+Ws8b7cVmGM=nzKvw@mail.gmail.com
Whole thread Raw
In response to Re: configure can't detect proper pthread flags  (Max Filippov <jcmvbkbc@gmail.com>)
Responses Re: configure can't detect proper pthread flags
Re: configure can't detect proper pthread flags
Re: configure can't detect proper pthread flags
List pgsql-hackers
On Fri, Mar 20, 2015 at 7:01 AM, Max Filippov <jcmvbkbc@gmail.com> wrote:
> On Fri, Mar 20, 2015 at 6:08 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> We don't want every link step producing a useless warning.
>> Ideally, "make -s" would print nothing whatsoever; to the extent that
>> tools produce unsuppressable routine chatter, that's evil because it
>> makes it harder to notice actually-useful warnings.
>
> Then maybe stderr tests should grep output for a specific option, the
> one we're currently testing, not just any noise?

That sounds awfully fragile to me.  It can't really be safe to assume
we know precisely what the warning messages will look like.  But it
seems to me that  compiling every test program with every library we
might need is not a great plan.

(I don't know enough about autoconf to know whether changing that is realistic.)

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Superuser connect during smart shutdown
Next
From: Amit Kapila
Date:
Subject: Re: Parallel Seq Scan