Opened 16 years ago
Closed 9 years ago
#2127 closed defect (fixed)
MSYS build lnkscript file path problem
Reported by: | rsbivand | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
Second on MSYS/MinGW building GDAL - up to and including 1.4.4, my installation of MSYS (1.0.10) just worked with ./configure, as suggested on:
http://trac.osgeo.org/gdal/wiki/BuildingWithMinGW
But 1.5.0 does not build without editing libtool at line 6114 to sed out the MSYS-anchored absolute path and replace it by a relative path (or possibly a Windows drive-based absolute path. Once the lnkscript only has relative path names, make runs to completion, and the resulting binaries, used with the R bindings in the rgdal package, check through without error.
Fix is to change line 5657 in ./ltmain.sh (or the correct line in the file it originates from) from:
$ECHO "$obj" >> $output
to
$ECHO "$obj" | ${SED} -e 's/.*gdal-[0-9].[0-9].[0-9]/\./' >> $output
(checked on MSYS and Linux RHEL4). Probably there is a better way of getting the build directory name - I am building in the source tree rather than outside.
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Waited 8 months for feedback, closing now.
http://trac.osgeo.org/gdal/wiki/BuildingWithMinGW mentions, as describer above, the need to edit "libtool at line 6114 to sed out the MSYS-anchored absolute path and replace it by a relative path". Perhaps that is enough as a fix for this 6 years old ticket?