This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: [Lame-dev] little makefile bug
- To: Alexander Leidinger <Alexander at Leidinger dot net>
- Subject: Re: [Lame-dev] little makefile bug
- From: Tom Tromey <tromey at redhat dot com>
- Date: 27 Aug 2001 23:34:03 -0600
- Cc: glessard at its dot caltech dot edu, lame-dev at lists dot sourceforge dot net, automake at gnu dot org
- List-Id: Discussion list for automake <automake.gnu.org>
- References: <200108272032.f7RKWZC62336@Magelan.Leidinger.net>
- Reply-To: tromey at redhat dot com
>>>>> "Alexander" == Alexander Leidinger <Alexander@Leidinger.net> writes:
Alexander> nasm_ldadd = $(top_builddir)/libmp3lame/@CPUTYPE@/liblameasmroutines.la
>> (cd .libs/libmp3lame.lax/libmpgdecoder.a && ar x /Volumes/White
>> Star/Users/glessard/Codage/lame-dev/libmp3lame/../mpglib/.libs/libmpgdecode
>> r.a)
It looks like libmpgdecoder.la is a libtool convenience library, and
libtool is running this command.
>> The obvious question is: why does it not quote paths?
Automake doesn't because it is much too hard.
`make' is just supremely lame about this. Working around the quoting
problems is possible (I've done it in a different tool), but really it
isn't worth the payoff.
Alexander> Guillaume also asked why absolute paths are used. Can
Alexander> anyone at automake@gnu.org please explain why absolute
Alexander> paths instead of relative paths (this would solve this
Alexander> particular problem) are used (please keep the CC, I didn't
Alexander> think anyone of us is subscribed to automake@gnu.org)?
I'm guessing that this is a libtool problem, and not an automake
problem.
Tom