This is the mail archive of the automake@gnu.org mailing list for the automake project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [Lame-dev] little makefile bug


On 27 Aug, Tom Tromey wrote:

> 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.

Yes.

> 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.

Does this mean this particular problem is avoidable?

The automake 1.5 README says "The mailing list automake@gnu.org is for
discussion of Automake, Autoconf, and other configuration/portability
tools (e.g., libtool).", therefore I haven't looked for another
libtool related mailinglist.

Bye,
Alexander.

-- 
      ...and that is how we know the Earth to be banana-shaped.

http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]