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.
|
|
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: Code:
./configure --prefix=/usr Mostly steps are: Code:
autoreconf -f -i |
Quote:
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. |
Quote:
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?
|
Quote:
|
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.
|
Quote:
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.
Quote:
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. |
Quote:
Quote:
Quote:
Quote:
|
Quote:
|
Quote:
If you had bothered to look, the tarball from alsa-tools has both a makefile, AND a gitcompile option...BOTH come in it. And both come in the version you check out from the GIT repository. |
Quote:
Ok the release tarball has gitcompile and it invokes automake/autoconf scripts. But read the INSTALL file. It supports the simple ./configure && make install. And git clone doesn't has Makefile nor configure file only configure.ac and makefile.am. So you would need automake/autoconf macros of all programs that alsa-utils needs for creating configure and makefile.in. In contrast consider a release tarball it has makefile.in and configure. Run configure with your required options and it produces working Makefile. If you don't want ld10k1 you can just give disable option to configue script. |
Quote:
Quote:
Quote:
The ONLY difference (MAYBE), is if you checkout a different version of the code from GIT, versus tar. You obviously haven't done a git checkout/clone of that, and compared it to the tarball. Because if you had, you'd notice THEY ARE IDENTICAL. |
All times are GMT -5. The time now is 02:23 AM. |