gdal-1.2.1_1 not building on Rel. 4.11p10
Benjamin Thelen
bt at ccgis.de
Sun Jun 19 11:32:58 GMT 2005
Hi List,
I have two 4.11p10 boxes on which upgrading gdal-1.2.1 to gdal-1.2.1_1
fails. On a 5.4-box, gdal compiles successfully. So I assume, that there
is a difference between 4.11 and 5.4, which now causes gdal stop building.
gdal-1.2.1 < needs updating (port has 1.2.1_1)
FreeBSD bender.ccgis-net.int 4.11-RELEASE-p10 FreeBSD 4.11-RELEASE-p10
#8: Sun Jun 19 11:48:35 CEST 2005
ben at bender.ccgis-net.int:/usr/obj/usr/src/sys/MyKern i386
I found out that all starts with the error-message:
.
.
.
EHapi.c:11: mfhdf.h: No such file or directory
.
.
.
But the port for hdf4 is installed and mfhdf.h is in /usr/local/include/.
I then copied mfhdf.h to
/usr/ports/graphics/gdal/work/gdal-1.2.1/frmts/hdf4/hdf-eos and started
"make" again. I'm told the following:
.
.
.
mfhdf.h:24: hdf.h: No such file or directory
mfhdf.h:25: netcdf.h: No such file or directory
.
.
.
Of course, I copied both to .../hdf-eos, but again files are missing:
.
.
.
In file included from mfhdf.h:24,
from EHapi.c:11:
hdf.h:19: h4config.h: No such file or directory
hdf.h:20: hdfi.h: No such file or directory
hdf.h:21: hlimits.h: No such file or directory
hdf.h:121: hntdefs.h: No such file or directory
hdf.h:124: htags.h: No such file or directory
hdf.h:143: hbitio.h: No such file or directory
hdf.h:144: hcomp.h: No such file or directory
hdf.h:145: herr.h: No such file or directory
hdf.h:146: hproto.h: No such file or directory
hdf.h:147: vg.h: No such file or directory
hdf.h:148: mfgr.h: No such file or directory
In file included from mfhdf.h:25,
from EHapi.c:11:
netcdf.h:248: hlimits.h: No such file or directory
netcdf.h:346: hdf2netcdf.h: No such file or directory
In file included from mfhdf.h:24,
from EHapi.c:11:
.
.
.
But there ist still a file missing:
.
.
.
ogr_srs_api.h: No such file or directory
.
.
.
And again, another is missing: ogr_core.h
Then gdal-1.2.1_1 builds successfully! What has happend? The former
version gdal-1.2.1 built successfully and just a "_1" is enough to break
this port for FreeBSD 4.11?
I couldn't find a hint neither in "changes" nor UPDATING and nothing
useful (at least for me) in google.
What can I do? Any idea?
Thank your very much!
Benjamin
More information about the freebsd-ports
mailing list