alsa configure problem

[lniskanen]

i downloaded the alsa driver 0.5.9c and tried to install it with the insructions i found here. i've extracted the files to /root/alsa-drive-5.0.9c and when i run ./configure there comes :
loadin cache ./config.cache
checking for gcc... no
checking for cc... no
configure: error : no acceptable cc found in $PATH

have i done something wrong (propably)

:confused:

[mdwatts]

I've just copied and pasted this from another thread I posted in earlier today. The same answer applies to your problem though the distro may be different.

Seems as if you don't have a c compiler installed or it's not in your path. Most likely not installed.

First try

whereis gcc
whereis cc
&
rpm -q gcc

If none are found, then you will need to install gcc though you probably are missing most of the development packages.

I'm not sure how to install the development packages in Redhat. They probably have docs on installing a set of packages after you've already installed Redhat.

The Redhat package manager may have a selection to install the development packages.

[tomass]

Kinda related I think - I am trying to install alsa sound
drivers in Mandrake 8.2 having just upgraded from
8.1 (where I had them working through installing alsa sound
drivers fine). I get the following, though, and have tried
searching for the answer on google.com/linux and in the how-to's.


run ./configure fine (although I had to copy the version.h file into a
new directory (/usr/src/linux/include/linux)
when I run make I get the following

make[1]: Entering directory
'/home/mthaddon/downloads/alsa-driver-x.x.x/kernel'
make[1]: *** No rule to make target '/usr/include/linux/autoconf.h',
needed by 'sound.o'. Stop.
make[1]: Leaving directory
'/home/mthaddon/downloads/alsa-driver-x.x.x/kernel'
make: *** [compile] Error 1

no sign of autoconf.h in a system wide Find either.

Where do I go from here?

Cheers, Tom

[lniskanen]

thanks!!! that solved it, and now it works. :) :)

[mdwatts]

Your quite welcome Iniskanen. Glad you got it to work.

tomass... My autoconf.h's are in

/usr/include/linux/autoconf.h
/usr/src/linux-2.4.13/include/linux/autoconf.h
/usr/src/linux-2.4.18/include/linux/autoconf.h

Try 'locate autoconf.h'

[tomass]

locate autoconf.h - tried it and nothing
came up. can I grab any other autoconf.h from
another machine, or is it specific to mine -
if so, any chance I could get yours? Its a
very recent install, so I don't see any reason
why I wouldn't have that from having accidentally
deleted it or anything.

cheers, tom

[mdwatts]

If you've installed the kernel source and you still don't have autoconf.h, then it could be you need to compile the kernel first for autoconf.h to be created.

[tomass]

okay, you've lost me there. I've never compiled
a kernel before, and I'm not sure how to do
that. If there are any articles you could point
me too, as I assume that its a fairly lengthy
process, that'd be much appreciated.

cheers, tom

[sarah31]

What distrobution are you using? Here (http://www.linuxhelp.net/guides/joey/kernel.shtml)is a guide that cna help you. In your case to make matters simple where it says to "make menuconfig" or "make xconfig" you can type "make oldconfig". This will keep all the option fron=m the current kernel. Then proceed as they direct. Once you aredone all this you should have no troubles getting ALSA installed and running.

I think there are also kernel compiling help files in the NHF section of this site.

[tomass]

I'm using Mandrake 8.2. I'm not sure why I
need to upgrade the kernel - I'm new to all this
but as far as I can work out, installing the
new version of Mandrake 8.2 over the old of 8.1
was what caused the problem, so how is installing
something else going to help me here. I know this
is likely a lack of understanding on my part,
but I'd appreciate if someone could clear that
up for me. Is there some particular way that I
need to upgrade the kernel that is going to do this
or am I simply supposed to do a generic upgrade?

Thanks, Tom

[camelrider]

You may be able to get *.h the files you need by installing the kernel source rpm (SRPM) from your install CD without having to recompile your kernel. With some packages the easiest thing is to boot from install CD, choose upgrade and "developer" package set in order for these files as well as shared libraries to be installed.

[sarah31]

perhaps you should reinstall 8.2 but this time do a clean install. That means wipe out your 8.1 and and install 8.2 fresh. Unless there is something you really don't want to erase. You can make copies of your configuration files and save them to your /home and when you install don't even touch that partition. Wipe out your root(/) partition and install 8.2. When you reboot after install you should have a fresh 8.2 and and all of you old files on your /home partition.


To answer your question as to why you would need to install additional stuff or recompile your kernel, quite simply because of the way certain applications are developed it is required to add or remove certain things. ALSA for one can be very difficult to get installed and working it took me a few days to figure everything out that I needed to. In the end I had to do 3 recompiles alone enabling or disabling certain things in my kernel until I found the right combination to get ALSA running. Other people can do it right away with out any additional tinkering. It is all dependant on how you have set up your computer, its hardware, installed packages, and experience.

Working with mandrake you will very quickly learn that inorder to get certain things running you will have to install or remove others. This is annoying but it is also an important feature of Linux and other *nix systems. The system is designed in such a manner that you don't corrupt the data in it and have to spend hours and days recovering from a mistake that should not have been permitted in the first place. Windows lacks this feature and it is vey easy for a user to do something silly which results in the loss of data or the entire system. I know folks who have even ruined there computer hardware making mistakes in Windows. Keeping the system up and running is the aim of a *nix system and this requires that such protections mentioned above are implimented.

[ 26 March 2002: Message edited by: sarah31 ]

[tomass]

thanks very much for your comments and patience. I'll be trying both of the methods mentioned, although I'll try the install from CD rather than reinstall entirely first! I really appreciate the explanation as well. Gives me a better understanding of the whole thing.

cheers, Tom

[sarah31]

Trust me many people here understand what you are saying and how you are feeling. Linux can be difficult to learn. I know alot more than when I started a year ago but I doubt i will ever be able to say I am much more than a simple user.

The most important thing for you to do is just take things slow and step back if thing are getting frustrating. We will eventually get you running happily and I think that you will enjoy Linux. Your perseverance will pay off and you will feel great because it was you who did it all we can do is tell you how we did it, but in the end it is you who will have pulled it off.

Keep up the hard work it will pay dividends in the end :)

[tomass]

Well, I tried to take the easy way out. I disabled
the onboard sound card in CMOS (it was a Yamaha
DS-XG), and then installed an ISA Creative Labs
Awe-16 Audio Card. It shows up in the hardware
list, but when I run the configuration tool, it
says:

"modprobe: Can't locate module isa-pnp"

What's my next move?

Thanks, Tom

[mdwatts]

Do a locate isa-pnp to see if the module exists. Mine is in /lib/modules/<kernel version>/kernel/drivers/pnp/isa-pnp.o

Now if that module is not there, then you may need to recompile the kernel to include isa-pnp module support. A bit much for someone new to Linux though.

You may be able to disable the PnP on the ISA soundcard and change the irq and i/o to whatever is free on your system. Some isa cards come with dos configuration utilities on the driver diskettes (or available via download) to change the resources and PnP on the card.

cat /proc/interrupts
cat /proc/ioports
cat /proc/pci

will tell you what resources are being used.

Also try some Google searches for the ISA Creative Labs AWE-16 to see if you can find other information/suggestions.

Did you read the NHF on the Yamaha DS-XG? I believe there is a NHF for that soundcard.

[tomass]

Thanks. I'll take a look at possibly configuring it manually.

I did try the NHF for the Yamaha one, but was having problems with "make". I had used that NHF to get it working under Mandrake 8.1, but when I upgraded to 8.2 it no longer worked for me.

Cheers, Tom

[tomass]

Well, just in case anyone's following this thread
still, there's a happy ending. I found out that
Mandrake 8.2 configures the start up with the
default option of "quiet" in lilo. Which is nice
if you're into the whole brevity thing, but
unfortunately means that what can be useful messages
such as kudzu asking you to remove the old sound
card from the configuration and configure the new
sound card (as above - old: onboard Yamaha DS-XG,
new: Creative AWE). So, kudzu took care of everything,
and now I'm back to listening to my mp3s. Thank god.

Although, I have to say, it made me realise that
if I prefer booting into a quiet Mandrake 8.2 than
a musically-enabled Win2k, then that must say
something.

Cheers, Tom

[strychninesoul]

tomass i had a prob like that with my net work you might want to try going into your BIOS and setting the irq to legacy mode i bet it will work if not it wont hurt to try you can always switch it back:confused: :confused: :confused: