Opened 13 years ago
Closed 12 years ago
#1745 closed enhancement (fixed)
[postgis-users] make generates incorrect PERL variable value on v1.5.2 from Bill Teluk March 9, 2011
Reported by: | ckelloug | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.2 |
Component: | documentation | Version: | 1.5.X |
Keywords: | Cc: |
Description
There was a bug reported in the mailing list: [postgis-users] make generates incorrect PERL variable value on v1.5.2
This was a bug where the postgis 1.5.2 build failed on postgres 9.0.4 due to $(PERL) being replaced with a non existant version of active perl when building postgis_upgrade_15_minor.sql
I finally resorted to running strace on make and I have identified the problem as bogus paths in pgxs, specfically the file listed below: /opt/postgres/9.0/lib/postgresql/pgxs/src/makefiles/../../src/Makefile.global
This file contains numerous hard coded paths to active state products and breaks the 1.5.4 postgis build.
Change History (6)
comment:1 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
I understand. I just created this ticket to provide some kind of documentation to keep others from thinking they were going mad.
comment:3 by , 13 years ago
Component: | build/upgrade/install → documentation |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
Type: | defect → enhancement |
Thanks. I have the same issue too on windows building under old mingw 3.45 and have to resort to hacking the makefile scripts (as I have documented here) http://trac.osgeo.org/postgis/wiki/DevWikiWinMingWSys_14_15
With this hack:
sed 's,$(PERL),perl,g' <postgis/Makefile >postgis/Makefile2 mv postgis/Makefile2 postgis/Makefile
I'll call this a documentation enhancement and put it in under build install when I have the next chance as I presume it's not just a mingw issue.
comment:5 by , 12 years ago
Milestone: | PostGIS 1.5.4 → PostGIS 2.0.2 |
---|
comment:6 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Asuming fixed after 5 months of missing feedback
I don't feel like there's much we can do for builds with bogarted PGXS settings. We depend on a sane PGXS.