I take it you successfully installed gcc, judging by the output you posted. Do not type:
./configure --with-cards=intel8x0 --with-sequencer=yes;make;make install
as one line. The semi-colons ( ; ) separate the three commands, whenever we install software from source (often referred to as a tarball due to it being in files ending tar.gz or tar.bz2 or tgz) we go through three stages(usually done separately).
./configure
make
make install
Unless we are compiling as root or doing our compilation in a directory which requires root access (This is what we are doing as /usr/src requires root access privileges) we will probably have to become the Super User (root) to perform the third step.
THIS IS NOT THE PROBLEM.
The first step will produce a configuration script which tells the make program where everything is and makes sure that everything you need to compile the program is present.
Typing:
./configure --with-cards=intel8x0 --with-sequencer=yes
should give you the same ouput as above up to the point where it asks you to install the kernel sources. This is giving you an error because the alsa driver package requires information that is in the kernel sources.
The parts which read:
--with-cards=intel8x0 --with-sequencer=yes
are options you are passing to the configure script in order that it can then pass them to the make program.
Assuming you followed my previous advice about installing gcc using the package manager, reopen that program, find the package which contains the kernel sources (this is the source code of the linux kernel), and install it. It will almost certainly install in the /usr/src directory probably giving you a directory called linux-2.4.xx-mdkyy, where xx and yy are numbers which identify the versions which are installed. There may also be a link in the /usr/src directory called linux which points to the new directory.
Try just running:
./configure --with-cards=intel8x0 --with-sequencer=yes
in the alsa-driver-0.9.8 directory again.
If it appears to work then type
make
sit back while it compiles don't expect it to be too quick, depending on the version of gcc you installed, what cpu you have, how much ram you have or whether you were born under the sign of Capricorn etc, it could take anywhere from a few minutes to a few hours. Watch a film, cook a meal etc. If it returns you to the command prompt without giving you any obvious errors then its probably worked. Now type:
make install
which will install your programs in the place they're supposed to be (Normally we would have to become the Super User before performing this step).
If this works then see if you can follow the rest of the steps for installing the alsa-utils and lib packages, and then try to change /etc/modules.conf.
Didn't I tell you that you'd learn loads doing this.
The:
./configure
make
make install
dance is applicable almost every time you install software from source. I usually keep a directory in my home directory called downloads for compiling etc, so I'd usually do something like get a tarball called:
foo-1.2.3-tar.gz
copy it to
/home/amos/downloads
probably using konqueror to do this part, then open up a shell, which would be as a normal user and type:
cd downloads
(Your shell normally opens with its present directory set to your home directory)
ls
(This lists the contents of the present directory)
tar zxvf foo-1.2.3-tar.gz
(This extracts the file and unpacks it probably into a directory called foo-1.2.3)
In konqueror I'd probably then move or delete the tarball, and change into the foo-1.2.3 directory to check any README's or INSTALL files. Then shifting the focus back to the shell I'd type:
ls
(To check what exactly the directory was called)
cd foo-1.2.3
(To change into that directory)
./configure
(Assuming that the README and the INSTALL files suggested that the default configuration was fine, otherwise I'd have to add things like: --with-cards=intel8x0 --with-sequencer=yes, if you want a list of options for configure you can type ./configure --help if everything goes fine then I'd go on to the next step.)
make
(When this exits normally the next step is usually to install the programs we've just compiled. These will 9 times out of 10 need to go into directories which require root privileges to access, so at this point we become the Super User.)
make install
(If everything goes well, and we need to run our newly installed program from the command line then typing exit will return us to normal user status before we proceed.)
I hope this hasn't been too long winded for you and has cleared up some things. A useful resource for you will probably be RUTE which apparently stands for Rute User's Tutorial and Exposition. You can find it here:
http://www.linuxman.com.cy/rute/rute.html
Cheers
Amos
