automake-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -recursive


From: Alexandre Duret-Lutz
Subject: Re: -recursive
Date: Mon, 07 Jul 2003 01:59:37 +0200
User-agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux)

>>> "Akim" == Akim Demaille <address@hidden> writes:

[...]

 Akim> Actually, I don't really understand the implementation in
 Akim> multilib, do you?

 Akim> if %?SUBDIRS%
 Akim> all-recursive: all-multi
 Akim> install-recursive: install-multi
 Akim> else !%?SUBDIRS%
 Akim> all-am: all-multi
 Akim> install-am: install-multi
 Akim> endif !%?SUBDIRS%

 Akim> (and similarly for other targets).  

The duplicate definition of *clean-recursive looks like a bug.

 Akim> Why not just bind it to -am?  It's coming from

 Akim> 2001-05-27  Tom Tromey  <address@hidden>

 Akim> * automake.in (handle_multilib): Only add multilib support
 Akim> code at
 Akim> top level.
 Akim> * lib/am/multilib.am: Handle invocation of *-multi
 Akim> targets
 Akim> differently for SUBDIRS and non-SUBDIRS Makefiles.
 Akim> * m4/multi.m4 (AM_ENABLE_MULTILIB): Removed erroneous
 Akim> comment.
 Akim> Only add multilib code when the Makefile in question is
 Akim> actually
 Akim> rebuilt.

 Akim> But there is not much information in there :(

Oh, if there is no test case it probably isn't important... <wink>

Interestingly only the *-recursive rules existed before that
change.  So adding -am rules for the non-SUBDIRS case seems
correct.  However I agree adding *-multi only as dependencies of
*-am rules sounds more correct, I see no point in using
*-recursive rules for something which is not recursive.  (I'm
not familiar with the multilib stuff though.)

[...]

-- 
Alexandre Duret-Lutz





reply via email to

[Prev in Thread] Current Thread [Next in Thread]