From alsa-devel-owner@alsa.jcu.cz  Fri Jan 29 14:11:22 1999
Received: from alfa.intrak.tuke.sk (ondrejj@ns.intrak.tuke.sk [147.232.14.22])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id OAA30582
	for <alsa-devel@alsa.jcu.cz>; Fri, 29 Jan 1999 14:06:31 +0100
Received: from localhost (ondrejj@localhost)
	by alfa.intrak.tuke.sk (8.9.1a/8.9.1/Debian/GNU) with SMTP id OAA08800
	for <alsa-devel@alsa.jcu.cz>; Fri, 29 Jan 1999 14:06:20 +0100
Date: Fri, 29 Jan 1999 14:06:19 +0100 (CET)
From: Jan ONDREJ <ondrejj@intrak.tuke.sk>
To: alsa-devel@alsa.jcu.cz
Subject: Re: configure script doesn't like ac1 patch
In-Reply-To: <19990129022354.A18544@casema.net>
Message-ID: <Pine.LNX.3.96.990129140532.8777B-100000@alfa.intrak.tuke.sk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Hello,

On Fri, 29 Jan 1999 smoke@casema.net wrote:

> someone pointed out to me that the ./configure script from
> the latest alsa-driver uses a wrong way to check for the correct
> kernel-version. The test fails with non-numeric versions like '2.2.0ac1'.

Try this patch:

--- configure.in.orig   Fri Jan  1 13:58:18 1999
+++ configure.in        Thu Jan 28 21:15:52 1999
@@ -56,6 +56,10 @@
 else
   kextraversion=`echo -$kextraversion`
 fi
+if echo $ksublevel | grep ac > /dev/null; then
+  kextraversion=a`echo $ksublevel | cut -d a -f 2`
+  ksublevel=`echo $ksublevel | cut -d a -f 1`
+fi
 kversion=`expr $kversion + 0`
 kpatchlevel=`expr $kpatchlevel + 0`
 ksublevel=`expr $ksublevel + 0`

			Bye.
						SAL



