From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Testing for failures in configure.in |
Date: | 2002-09-07 22:09:34 |
Message-ID: | 200209072209.g87M9Ya15974@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[ Discussion moved to hackers.]
I recently added a test for JAVA_HOME to configure.in to issue a more
helpful message when Ant can't be run rather than throwing a more
generic Ant failure message and expecting people to look in config.log.
My question is should we be doing such checks to try and help people who
get configure failures, should we be pointing people to config.log more
often. and are there other common failure cases in configure.in that
should be improved.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-09-07 22:39:46 | Re: [JDBC] problem with new autocommit config parameter |
Previous Message | Steve Howe | 2002-09-07 21:28:09 | Re: Rule updates and PQcmdstatus() issue |