From alsa-devel-owner@alsa.jcu.cz  Tue Feb 16 22:30:38 1999
Received: from umr.edu (hermes.cc.umr.edu [131.151.1.68])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id WAA26261
	for <alsa-devel@alsa.jcu.cz>; Tue, 16 Feb 1999 22:30:29 +0100
Received: from frb.student.umr.edu (frb.student.umr.edu [131.151.147.50]) via ESMTP by hermes.cc.umr.edu (8.8.7/R.4.20) id PAA17044; Tue, 16 Feb 1999 15:30:13 -0600 (CST)
Received: (from frb@localhost)
	by frb.student.umr.edu (8.9.3/8.9.3/Debian/GNU) id PAA27320;
	Tue, 16 Feb 1999 15:30:12 -0600
Date: Tue, 16 Feb 1999 15:30:12 -0600
From: Franklin Belew <frb@umr.edu>
To: Tuomas Heino <iheino@cc.hut.fi>
Cc: Franklin Belew <frb@umr.edu>, alsa-devel@alsa.jcu.cz
Subject: Re: alsa-util: configure version check incorrect? (aclocal?)
Message-ID: <19990216153012.A27066@asylum.umr.edu>
References: <19990216112459.A622@asylum.umr.edu> <Pine.OSF.3.96.990216213717.25287B-100000@alpha.hut.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.OSF.3.96.990216213717.25287B-100000@alpha.hut.fi>; from Tuomas Heino on Tue, Feb 16, 1999 at 09:43:00PM +0200
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Tue, Feb 16, 1999 at 09:43:00PM +0200, Tuomas Heino wrote:
> > > Thanks... "aclocal -I /usr/local/share/aclocal" did it for me ;)
> > > [hmm should alsa-lib's configure --prefix=/usr/local do something to this situation?]
> > configure can't do anything about this, since it isn't created until after aclocal and autoconf are run.
> [snip]
> I guess you didn't read it carefully enough to realize we're talking about
> multiple "packages" and dependancies between them...
> installation of alsa-lib generates alsa.m4 in $(prefix)/share/aclocal/
> alsa-utils' aclocal depends on the location of the file...
> so I guess we need a script (cvscompile or ../build ?) to handle the
> parameters... (yes some people want to use --prefix and --with-cards;)
If you didn't notice, the script that you snipped does exactly that
all $ACLOCAL_FLAGS does is allow people to specify extra directories that m4 
files are in.
so if you install it in /usr/local/sound/alsa/lib/ the m4 files would be in 
/usr/local/sound/alsa/lib/share/aclocal
your ACLOCAL_FLAGS would contain "-I /usr/local/sound/alsa/lib/share/aclocal"
this is an extreme case, but that is exactly how that works

the next part you seem to have missed is that at the end of the build script it
had
configure $@
$@ in sh is all the arguments to the running program
hence when you run cvsbuild --prefix=/usr/local it would go on about its 
business and then run "configure --prefix=/usr/local" since the flags get 
passed on.

(script snippet that was cut from previous post)
#!/bin/sh
aclocal $ACLOCAL_FLAGS      # get ACLOCAL_FLAGS from environment
automake                    # I haven't checked if this is needed
autoconf                    # create ./configure
./configure $@              # run configure with all the arguments given to
                            # this script


Frank Belew


