pgsql: Code the unknown options check without using m4 diversions. - Mailing list pgsql-committers

From petere@postgresql.org (Peter Eisentraut)
Subject pgsql: Code the unknown options check without using m4 diversions.
Date
Msg-id 20061030221504.8F8F39FB2C4@postgresql.org
Whole thread Raw
Responses Re: pgsql: Code the unknown options check without using m4 diversions.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Log Message:
-----------
Code the unknown options check without using m4 diversions.  Otherwise this
code relies on the checking macro actually being called at the end, or the
automatic undiversion will produce garbage.  These sort of implicit
side-effects undermine the modularity of the macros and happen to break the
ODBC driver which makes use of them.

Also put the warnings at the very end of configure, so there is an even
better chance of seeing them.

Modified Files:
--------------
    pgsql:
        configure (r1.515 -> r1.516)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.515&r2=1.516)
        configure.in (r1.484 -> r1.485)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.in.diff?r1=1.484&r2=1.485)
    pgsql/config:
        general.m4 (r1.6 -> r1.7)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/config/general.m4.diff?r1=1.6&r2=1.7)

pgsql-committers by date:

Previous
From: petere@pgfoundry.org (User Petere)
Date:
Subject: psqlodbc - psqlodbc: Don't pull in libraries and cflags from pg_config;
Next
From: neilc@postgresql.org (Neil Conway)
Date:
Subject: pgsql: Add text to the VACUUM, REINDEX, DROP TABLESPACE and CREATE