libgdal1-1.5.0 can not recompiled

I have the same error in a pbuilbder build:
libtool: link: g++ -Wl,-Bsymbolic-functions -fPIC -DPIC -I/usr/include -Wl,-Bsymbolic-functions -g -O2 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -rdynamic gdal_wrap.o -o .libs/gdal.so -L/usr/lib -lc -L/usr/lib/mysql -lm -L/tmp/buildd/gdal-1.5.2 /tmp/buildd/gdal-1.5.2/.libs/libgdal1.5.0.so /usr/lib/libgeos_c.so /usr/lib/libgeos.so /usr/lib/libsqlite3.so /usr/lib/libodbc.so /usr/lib/libodbcinst.so /usr/lib/libltdl.so /usr/lib/libexpat.so -lxerces-c /usr/lib/libjasper.so /usr/lib/libhdf5.so -lmfhdf -ldf -logdi /usr/lib/libgif.so /usr/lib/libtiff.so /usr/lib/libjpeg.so -lpng -lnetcdf -lpq -ldl /usr/lib/libcurl-gnutls.so /usr/lib/libidn.so -lldap -lrt -lkrb5 -lk5crypto -lcom_err -lgssapi_krb5 /usr/lib/libgnutls.so /usr/lib/libtasn1.so /lib/libgcrypt.so /usr/lib/libmysqlclient.so -lpthread -lcrypt -lnsl -lz -lruby1.8
/usr/lib/gcc/x86_64-linux-gnu/4.3.2/../../../../lib/crt1.o: In function `_start':
(.text+0x20): undefined reference to `main'
collect2: ld returned 1 exit status
make[2]: *** [gdal.so] Error 1
make[2]: Leaving directory `/tmp/buildd/gdal-1.5.2/swig/ruby'

It seems to be an issue with libtool, as the libtool version used to build this package is libtool_1.5.26-4 (from http://launchpadlibrarian.net/15827018/buildlog_ubuntu-intrepid-i386.gdal_1.5.2-2_FULLYBUILT.txt.gz)

In Jaunty, it FTBFS also, and libtool is version 2.2.4-0ubuntu4 (http://launchpadlibrarian.net/19413734/buildlog_ubuntu-jaunty-i386.gdal_1.5.2-3_FAILEDTOBUILD.txt.gz).

Changing package to libtool

See also http://trac.osgeo.org/gdal/ticket/2138

I've got an ugly fix for this libtool problem, but now, because of python2.6 transition, I have another problem.
Should be solved shortly

The ugly fix has been to copy the libtool script from hardy (1.5.26-1ubuntu1) to the package, as the package builds and works fine with this 'old' version of libtool.
Also, because of the transition to python2.6, I've been obliged to patch a makefile to add --install-layout=deb to the setup.py call.

Testing this now, especially since I really need it to test my geodjango code in Jaunty ASAP. If all is well, I will go ahead and upload. Thanks!

This does in fact fix any GDAL issues previously noted and my code now runs and performs as it did in Intrepid. Uploading this fix now. Below you will see the GEOS/GDAL tests for geodjango. Same results as <=Intrepid.

nixternal@KaboWabo:~/pbuilder/jaunty_result$ python
Python 2.6.1+ (r261:67515, Mar 2 2009, 13:11:28)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from django.contrib.gis.gdal import HAS_GDAL
>>> print HAS_GDAL
True
>>> from django.contrib.gis.tests import test_gdal
>>> test_gdal.run()
.....
BEGIN - expecting out of range feature id error; safe to ignore.

ERROR 1: Attempt to read shape with feature id (50000) out of available range.
ERROR 1: Attempt to read shape with feature id (50000) out of available range.

END - expecting out of range feature id error; safe to ignore.
....................
BEGIN - expecting IllegalArgumentException; safe to ignore.

ERROR 1: IllegalArgumentException: points must form a closed linestring

END - expecting IllegalArgumentException; safe to ignore.

......................
----------------------------------------------------------------------
Ran 47 tests in 0.193s

OK
>>> from django.contrib.gis.tests import test_geos
>>> test_geos.run()
Testing WKT output. ... ok
Testing HEX output. ... ok
Testing KML output. ... ok
Testing the Error handlers. ...
BEGIN - expecting GEOS_ERROR; safe to ignore.

GEOS_ERROR: ParseException: Expected number but encountered ','
GEOS_ERROR: ParseException: Unknown WKB type 255

END - expecting GEOS_ERROR; safe to ignore.

GEOS_ERROR: ParseException: Unexpected EOF parsing WKB
ok
Testing WKB output. ... ok
Testing creation from HEX. ... ok
Testing creation from WKB. ... ok
Testing EWKT. ... ok
Testing GeoJSON input/output (via GDAL). ... ok
Testing equivalence. ... ok
Testing Point objects. ... ok
Testing MultiPoint objects. ... ok
Testing LineString objects. ... ok
Testing MultiLineString objects. ... ok
Testing LinearRing objects. ... ok
Testing Polygon objects. ... ok
Testing MultiPolygon objects. ...
BEGIN - expecting GEOS_NOTICE; safe to ignore.

GEOS_NOTICE: Duplicate Rings at or near point 60 300

END - expecting GEOS_NOTICE; safe to ignore.

ok
Testing Geometry __del__() on rings and polygons. ... ok
Testing Coordinate Sequence objects. ... ok
Testing relate() and relate_pattern(). ... ok
Testing intersects() and intersection(). ... ok
Testing union(). ... ok
Testing difference(). ... ok
Testing sym_difference(). ... ok
Testing buffer(). ... ok
Testing the SRID property and keyword. ... ok
Testing the mutability of Polygons and Geometry Collections. ... ok
Testing three-dimensional geometries. ... ok
Testing the distance() function. ... ok
Testing the length property. ... ok
Testing empty geometries and collections. ... ok
Testing `ogr` and `srs` properties. ... ok
Testing use with the Python `copy` module. ... ok
Testing `transform` method. ... ok
Testing `extent` method. ... ok
Testing pickling and unpickling support. ... ok

----------------------------------------------------------------------
Ran 36 tests in 0.250s...

This bug was fixed in the package gdal - 1.5.2-3ubuntu1

---------------
gdal (1.5.2-3ubuntu1) jaunty; urgency=low

  * debian/rules: use local libtool 1.5.2 instead of system one (LP: #284910)
  * debian/libtool: created copying libtool 1.5.2 from plibtool package in Hardy

 -- Fabrice Coutadeur <email address hidden> Thu, 05 Mar 2009 07:15:03 +0000

Not sure if replacing libtool is needed here -- from: http://trac.osgeo.org/gdal/ticket/1994

> One more fix is required to work with libtool 2.2. s/-shared/-Xcompiler -shared/ in LDFLAGS. Note that some systems still use 1.5, but more and more of them are upgrading to series 2.2. Also that flag is back-compatible with 1.5.

Doing this replacement enabled me to build & test fine.