From alsa-user-owner@alsa.jcu.cz  Sun Jul 19 19:19:53 1998
Received: from brick.physics.sunysb.edu (root@brick.physics.sunysb.edu [129.49.30.176])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id TAA10885
	for <alsa-user@jcu.cz>; Sun, 19 Jul 1998 19:17:02 +0200
Received: by brick.physics.sunysb.edu
	via sendmail from stdin
	id <m0yxx4x-000xcCC@brick.physics.sunysb.edu> (Debian Smail3.2.0.101)
	for alsa-user@jcu.cz; Sun, 19 Jul 1998 13:16:55 -0400 (EWT) 
From: Brett Viren <bviren@ale.physics.sunysb.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sun, 19 Jul 1998 13:16:54 -0400 (EDT)
To: Robin Davis <rdavis@zetnet.co.uk>
cc: alsa-user@jcu.cz
Subject: Re: The configure script?
In-Reply-To: <Pine.LNX.3.96.980718222304.1010A-100000@anrltd.zetnet.co.uk>
References: <Pine.LNX.3.96.980625194629.1867A-100000@anrltd.zetnet.co.uk>
	<Pine.LNX.3.96.980718222304.1010A-100000@anrltd.zetnet.co.uk>
Message-ID: <13746.9498.305419.950628@brick.physics.sunysb.edu>
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

Robin,

I too have Debian 2.0 running and the alsa-driver 0.1.4 compiles just
fine.  So it is something pecular with some detail of your Debian
installation.

Here are some things to try:

Robin Davis writes:

 > [root@anrltd alsadriver]# ./configure
 > loading cache ./config.cache

1) Try removing ./config.cache and do a make clean and then another
./configure

2) Check gcc installation: `dpkg -l | grep gcc'. You should see
something like:

ii  gcc             2.7.2.3-4.7    The GNU C compiler.

If you don't have the `ii' this could signify problems.  Also, if you
have an older gcc (probably only the Debian version number will
differ, mine above is the `4.7') you may want to upgrade.

3) Try a `dpkg --audit' to see if anything on your system is broken.

4) Re-install the gcc package from your CD or from the net.  I guess
there is a non-zero probability that your gcc executable got corrupted
or something (unfortunately Debian still doesn't have md5sums on all
installed files, and in particular for gcc, so you can't just check).
It is also conceivable that the error is on the CD, so try compiling
something by hand (as suggested by another responder).

5) You can also try the prebuilt Debian alsa packages.  They are in
the new unstable (slink) directory:

ftp://ftp.debian.org/debian/dists/slink/main/binary-i386/sound/alsa*

The drivers appear to be built for Linux 2.0.34, so you will need to
run this kernel if you want the pre-built modules to work.

6) Finally, do you happen to have more than one gcc installed, perhaps
one in /usr/local as well as Debian's in /usr?  It is best to have
only one on a system otherwise there is bound to be confusion (I know
from personal experience <g>).  For example, if you are using egcs
which is somehow getting at gcc's includes and libs there could be
problems.

Hope one of these things helps,
-Brett.

