[sane-devel] problems on OS/2

Olaf Meeuwissen olaf.meeuwissen at avasys.jp
Fri Feb 6 04:31:53 UTC 2009


Chris Bagwell <chris at cnpbagwell.com> writes:

> Olaf Meeuwissen wrote:
>> Oops!  I just realised that the code I was looking at was **after**
>> `autoreconf --force --install`.  The code in CVS is 11 months old and
>> does NOT have a wildcard that would match 'os2'.
>>
>> The CVS version has:
>>   VERSION=1.5.22
>>   TIMESTAMP=" (1.1220.2.365 2005/12/18 22:14:06)"
>>
>> After autoreconf, mine has:
>>   VERSION="1.5.26 Debian 1.5.26-4"
>>   TIMESTAMP=" (1.1220.2.493 2008/02/01 16:58:18)"
>
> On that front, yesterday I upgraded ltmain.sh to 1.5.26 (with patch)
> and I'm planning on submitting it today (I hope).  But I *still* don't
> see that wildcard your talking about.  Surely, its gotta be there
> though.

Doh!  Debian specific patch ... debian/patches/version_type.patch

Index: libtool-1.5.26/ltmain.in
===================================================================
--- libtool-1.5.26.orig/ltmain.in	2008-04-05 15:32:04.000000000 +0000
+++ libtool-1.5.26/ltmain.in	2008-04-05 15:32:08.000000000 +0000
@@ -3272,6 +3272,11 @@
 	    revision="$number_minor"
 	    lt_irix_increment=no
 	    ;;
+	  *)
+	    $echo "$modename: unknown library version type \`$version_type'" 1>&2
+	    $echo "Fatal configuration error.  See the $PACKAGE docs for more information." 1>&2
+	    exit $EXIT_FAILURE
+	    ;;
 	  esac
 	  ;;
 	no)

>> If OS/2 was happy with the ltmain.sh in the SANE CVS repository, I
>> suggest we add in a case for whatever version_type is appropriate
>> for OS/2.  May want to ping libtool upstream about this as well.
>
> Well, based on my last email, its a fluke that it was working with old
> ltmain.sh.  I'd prefer that it worked with libtool as-is.

ACK.

> I'm no OS/2 expert but I think OS/2 requires "-no-undefined" and that
> *may* be why current ltmain.sh will ignore the buggy options.
> Hopefully, an expert is lurking out there.



More information about the sane-devel mailing list