Alsa Error When compiling.
 

Hello all.

When I want to compile "alsa-tools-1.0.28" on debian 7.7 via "./gitcompile" it show me below error :

configure.ac:21: warning: macro `AM_PATH_LD10K1' not found in library
configure.ac:21: error: possibly undefined macro: AM_PATH_LD10K1
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
make: *** [all] Error 1

How can I solve it?

It would help to know why you are compiling a package on Wheezy that is available as a binary in the Sid repo.

You need to install devel package/files of ld10k1.

Source Website

I downloaded "http://sourceforge.net/projects/ld10k1/files/" and install but problem not solved and see same error.

If you are using alsa-tools-1.0.28 stable why not get a tarball and don't use git.

For a tarball you can do regular:

For git download do as readme or install file says.

Mostly steps are:

When you download the Alsa-tools and extract it, its has some directories with a file with the name "gitcompile" and it installed all tools for you automatically.

Please, go back to post #2, and read/answer what widget posted.

There is NO REASON to compile any of this, when you can get packages that are pre-built for your system. WHY are you trying to do this, is the best question??? Shoving in bits of Alsa (and WORSE, the ld10k1 libraries), from source is only going to make things MUCH harder to maintain on your system, and may make things not work AT ALL.

I want to install it myself. Any problem?

Aside from the ones you're having, you mean?? No, feel free. It's just not a good idea, unless you absolutely NEED some particular function that only the bleeding-edge software can provide you, or isn't compiled in to what you've already got as a package. Having software and libraries that are totally mismatched to what is in your repositories can lead to some...'interesting' things happening, and give you bad results.

You would be better off if you want to compile packages to use Slackware.

If that is too much like leaping into the deep end of the pool get the book for Linux From Scratch and build it in a chroot "jail" within your Debian install.

Either one will give you plenty of opportunity to compile packages with in a system that is intended for that purpose.

There is nothing at all wrong with compiling to Debian if you need it. However; your system is designed to use a package manager, dpkg, built to keep track of packages, install packages, remove packages and to resolve dependency problems.

This can become very sticky when you have packages built in the system that dpkg knows nothing about. So while it can be done you should be pretty well expert at dealing with dpkg and problems with it before you start compiling packages to Debian.

You should probably also check this post;
http://www.linuxquestions.org/questi...7/#post5311124

The link in it is excellent.

I would still say grab the release tarball and install it. If it does not then try git. Because git uses all that automake/autoconf stuff whose dependency solving would be nightmare to newbies.

How, exactly, did you come to this conclusion??? The source dependencies are THE SAME, whether you get the source from tar or GIT. The build instructions are the same, along with what is needed to compile/run it.

ALSA from source is ALWAYS to be avoided whenever possible, because it IS a nightmare, and there's typically never a need to do it.

Because I install my whole system by source. Did you overlooked the error he is getting.

His system is lacking a automake macro. The upstream have that in their system but it is not present on most users. So automake/autoconf is not able to produce a working Makefile file. That's why you have to install devel files for macros.

By the way you suggesting always prefer binary versions from distros I anticipate that you don't do much building from source.

You can read info pages of automake, autoconf, libtool.

I find it VERY hard to believe you installed Linux from Scratch. And no, I didn't overlook his error.
...or you simply install the automake package, right? And did you overlook the fact that the source tar.gz file has the SAME THINGS in it as the ones from GIT???
I build quite a bit, thanks, and write LOTS of my own code. AGAIN, since you're missing the point, installing VERY complex things like ALSA, GLIB, or other such libraries:

• Is VERY complicated
• Something that newer users shouldn't really do
• Something that NO ONE should every do, unless they absolutely NEED a cutting edge feature or something that's not in the pre-compiled package

Yes, and so can you. You can also read the release notes on ALSA and how to build it, along with many other things.