gdal @1.9.0 +python27 fails to install

[titusjan@…]

I am trying to install gdal 1.9.0 but I get the following error:

~> sudo port install gdal +python27
--->  Computing dependencies for gdal
--->  Fetching archive for gdal
--->  Attempting to fetch gdal-1.9.0_3+expat+python27.darwin_10.x86_64.tbz2 from http://packages.macports.org/gdal
--->  Fetching distfiles for gdal
--->  Verifying checksum(s) for gdal
--->  Extracting gdal
--->  Applying patches to gdal
--->  Configuring gdal
--->  Building gdal
Error: org.macports.build for port gdal returned: command execution failed
Please see the log file for port gdal for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_gdal/gdal/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port gdal failed

I've attached the logs.

I also tried to use the llvm-gcc-4.2 compiler as below but I got the same error.

sudo port clean gdal +python27
sudo port install gdal +python27 configure.compiler=llvm-gcc-4.2

Idem for the apple-gcc42 port

sudo port clean gdal +python27
sudo port install apple-gcc42
sudo port install gdal +python27 configure.compiler=apple-gcc-4.2 configure.cxx=g++-apple-4.2

Please let me know if I should include the logs for those last two cases as well.

I am using XCode 4.2 on OS-X 10.6.8.

Thanks, Pepijn.

[titusjan@…]

gdal install with CLANG

[ryandesign (Ryan Carsten Schmidt)]

The log says:

unable to execute /usr/bin/gcc-4.2: No such file or directory

So one of gdal's dependencies, in this case probably python27, has remembered the location of the compiler that was used when you originally compiled it when you had Xcode 3.2 (or, you got a pre-built binary from our server, which builds things using Xcode 3.2) and now you have Xcode 4.2 which no longer has that compiler. This is the same problem we mention in wiki:ProblemHotlist#xcode-select.

The solution is to rebuild python27:

sudo port -ns upgrade --force python27

Beware that any future upgrade of python27 that gets a binary from our server will likely reintroduce this problem, so either remember to use the -s flag when upgrading ports like python27 that hardcode the compiler location, or edit macports.conf and turn off the use of binaries entirely.