From alsa-user-owner@alsa.jcu.cz  Tue Dec 22 19:06:03 1998
Received: from ale.physics.sunysb.edu (root@ale.physics.sunysb.edu [129.49.30.117])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id TAA27287
	for <alsa-user@alsa.JCU.CZ>; Tue, 22 Dec 1998 19:04:41 +0100
Received: from ale.physics.sunysb.edu (really [127.0.0.1]) by superk.physics.sunysb.edu
	via in.smtpd with esmtp (ident sharkey using rfc1413)
	id <m0zsWAf-000PpeC@ale.physics.sunysb.edu> (Debian Smail3.2.0.101)
	for <alsa-user@alsa.jcu.cz>; Tue, 22 Dec 1998 13:04:37 -0500 (EST) 
Message-Id: <m0zsWAf-000PpeC@ale.physics.sunysb.edu>
Cc: golinvaux@benjamin.net
To: alsa-user@alsa.JCU.CZ
From: sharkey@ale.physics.sunysb.edu
Subject: Re: newbie : error in configure script 
In-reply-to: Your message of "Sun, 20 Dec 1998 23:25:53 +0100."
             <004d01be2c68$514bdde0$28934ac1@w98bg> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 22 Dec 1998 13:04:36 -0500
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

> Don't flame me for this very newbie-like question... I've been moving from
> Windoze NT with Visual C++ to Linux Debian with gcc this week...

You will not be flamed.  Newbies are welcome.  But this probably belongs on
alsa-user, not alsa-devel.  I'm switching lists to continue this thread.

> 1) the INSTALL file says : be sure to remove OSS/Lite from your kernel
> before installing alsa : could someone explain me in two words what means
> 'removing a module from kernel' :

I'm afraid I can't.  At least, not in two words.

> is it a source code operation (removing a
> c file from kernel) or just a binary operation in some .O loading script ?)

Don't remove anything from the kernel source.  You don't need to remove any
C files or anything like that from the source.  When you compile a Linux
kernel, you have many options which can be set in the .config file.  These
options decide which parts of the kernel actually get compiled into the
binary.  You shouldn't edit this file directly.  You can use "make menuconfig"
to set kernel options before you compile a kernel.  Most options can be
set to one of three states: in the kernel, not in the kernel, or in a kernel
module.

You see, it's not really possible to "remove OSS/Lite from your kernel".  You
have to replace the kernel with a new one that doesn't have it to begin with.

In other words, cd to the directory with your copy of the kernel source,
run "make menuconfig", and use the menu to turn off all sound support,
save the configuration, compile and install a new kernel.

This is necessary if your kernel was compiled with sound "in the kernel".

If your kernel was compiled with sound "in a kernel module", then you can
probably get away with simply removing the module.  Modules are usually
stored in /lib/modules/<kernel version number>.  The sound module is called
"sound.o" and is usually in the "misc" subdirectory.  If you remove that file,
the kernel won't be able to load it, and you won't have any ALSA/OSS conflicts.
 
> 2) the configure script tells me : 'error... compiler can't produce
> executables'. However, I'm using egcs g++ which compiles .c and .cc well...
> And gcc is installed also (I believe g++ and gcc must be links to a common
> compiler cc...).. How to check gcc install is correct ?

I've never seen that one before.  Anyone else on alsa-user able to answer
this one?

Eric


