#2710 closed defect (fixed)
pg_config detection in configure - should abort if not found
| Reported by: | dmorissette | Owned by: | dmorissette |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.4 release |
| Component: | Build Problems | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: | gsueur |
Description
Guillaume Sueur reported the following issue on mapserver-users:
playing around with the new mapserver source, I've found something annoying into the configure : when you ask for with-postgis=/some/dir/pg_config, the configure script finishes ok even if it had warned you that it couldn't find pg_config. Worse, the final sum up indicates :
PostGIS support: -DUSE_POSTGIS
making people think it went well.
Actually, there is a message in the middle of configure output, but if you don't scroll up to check it, you can't know you misconfigured your path.
Couldn't it stop on this warning, like it does for GD for instance ?
Note:
See TracTickets
for help on using tickets.
Fixed in r7827 in SVN trunk (5.3-dev). The configure script will now stop execution if the pg_config, or any of the -config scripts is not found.
The same problem was also present with the detection of the mysql_config, curl-config, xml2-config and fribidi-config scripts. This revision fixes them all.