Opened 12 years ago

Closed 12 years ago

#1628 closed defect (fixed)

Can't configure anymore again on mingw

Reported by: robe Owned by: pramsey
Priority: blocker Milestone: PostGIS 2.0.0
Component: postgis Version: master
Keywords: Cc: martin

Description

I thought I had tested this last night but could be a new development. I confirmed with the alpha7 from yesterday I can configure that. On trunk today after deleting my automte folder and regress-install, I noticed things stopped working. It's possible I missed yesterday because it might have been testing against my prior regress-install folder so all tests were passing (I have an auto .sh script to compile everything).

Anyrate now I have configure issues as of r9339

checking for PQserverVersion in -lpq... yes
checking for xml2-config... no
configure: error: could not find xml2-config from libxml2 within the current path. You may need to try re-running configure with a --with-xml2config parameter.
make: *** [GNUmakefile] Error 1
checking build system type... i686-pc-mingw32

:
checking libpq-fe.h usability... yes
checking libpq-fe.h presence... yes
checking for libpq-fe.h... yes
checking for PQserverVersion in -lpq... yes
----------------------------------------------------------------------
  You have set the --prefix to '/c/projects/pg/pg91'. Unfortunately the PostGIS   
  build system can only install into the directories used by the      
  PostgreSQL build you are compiling against, the one that supplied   
  the pg_config we detected: /c/projects/pg/pg91/bin/pg_config 
  Based on that script we will be installing:   
    * postgis shared library in c:/projects/pg/pg91/lib 
    * postgis SQL files in c:/projects/pg/pg91/share/POSTGR~1/contrib/postgis-2.0 
    * postgis executables in c:/projects/pg/pg91/bin 
  Please try again without a --prefix, sorry. 
----------------------------------------------------------------------

works fine if I flip back to alpha7 tar ball from yesterday. I'll redownload a tar and see if the tar works fine.

Change History (9)

comment:1 by robe, 12 years ago

Okay someone has been screwing with the configure scripts. I downloaded the latest tar ball and it gives the same error (but last nights tar ball works fine). So something more than line break changes must be happening here.

comment:2 by robe, 12 years ago

FWIW my script looks something like this

export GEOS_VER=3.3.3SVN_345
export GDAL_VER=1.9.0_345
export XML_VER=2.7.8
export PROJSO="libproj.dll"
export PROJ_LIB=/c/projects/postgis/pg/pg84/share/contrib/postgis/proj
export GDAL_DATA=/c/projects/gdal/rel-${GDAL_VER}/share/gdal
export JSON_VER=0.9_345

./configure  --prefix=/c/projects/pg/pg${PG_VER} --with-gdalconfig=/c/projects/gdal/rel-${GDAL_VER}/bin/gdal-config --with-jsondir=/c/projects/json-c/rel-${JSON_VER} --with-xml2config=/c/projects/libxml/libxml2-${XML_VER}release/bin/xml2-config --with-pgconfig=/c/projects/pg/pg${PG_VER}/bin/pg_config --with-geosconfig=/c/projects/geos/rel-${GEOS_VER}/bin/geos-config --with-projdir=/c/projects/proj/rel-4.6.1 --with-gettext=no  --with-gui --with-topology

comment:3 by robe, 12 years ago

Aha, it's you again, Paul :) Couldn't leave well enough alone could you?

Reverting the configure.ac file to r9332 fixes my configure problem so must be that r9333 —prefix change you introduced.

comment:4 by pramsey, 12 years ago

The error message seems pretty self-explanatory… don't use —prefix. It doesn't do anything, don't use it. If you think that's bad, you can dnl it out of the file.

comment:5 by robe, 12 years ago

The message doesn't seem clear to me. I am compiling against that version and I for each build switch which version I am compiling against so I was thrown off thinking it was complaining about the paths.

If you don't want people to use prefix why can't you just say in plain english

—prefix is obsolete. It doesn't do anything please remove it.

But it does seem to work fine without it as you said. It's just that you gave too much information which is really confusing.

comment:6 by robe, 12 years ago

Resolution: invalid
Status: newclosed

perhaps its too late and I'm reading into things that aren't there but I do think your explanation is too wordy. I'll close this out though.

comment:7 by martin, 12 years ago

Cc: martin added

—prefix is _not_ obsolete, it makes configure read the PREFIX/etc/config.site file - which is pretty relevant on setups which don't feature a compiler- and linker-monoculture

comment:8 by pramsey, 12 years ago

Resolution: invalid
Status: closedreopened

comment:9 by pramsey, 12 years ago

Resolution: fixed
Status: reopenedclosed

OK, less dire warning for the less fortunate. r9375

Note: See TracTickets for help on using tickets.