"Derek R. Price" wrote:
> Akim Demaille wrote:
>
> > VPATH is just set to srcdir? So then, I'm in favor of Derek's patch
> > which seems finer that the current one, and updating the Autoconf
> > documentation to explain exactly what happens.
>
> Here's an even slightly better version. It will r
Akim Demaille wrote:
> So, I think I'm slowly starting to understand this VPATH stuff:
> configure wants to remove it only when useless, right? I.e., when
> VPATH is just set to srcdir? So then, I'm in favor of Derek's patch
> which seems finer that the current one, and updating the Autoconf
>
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> It seems to me that Autoconf's job is not to remove unportable
Akim> code written by the user, so it seems wrong to have it remove
Akim> VPATH definitions from Makefiles. Histori
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> It seems to me that Autoconf's job is not to remove unportable
Akim> code written by the user, so it seems wrong to have it remove
Akim> VPATH definitions from Makefiles. Historically I'm sure it was
Akim> useful, in a previous cent
On Wed, Jan 17, 2001 at 02:02:17PM +0100, Lars J. Aas wrote:
: I'm all for this if the user can silence the warning by doing something
: with a variable setting in the Makefile.am in case he knows what he is
: doing.
The same goes for all the automake warnings. If the warnings could be
enumerate
On Wed, Jan 17, 2001 at 11:17:00AM +0100, Akim Demaille wrote:
: It seems to me that Autoconf's job is not to remove unportable code
: written by the user, so it seems wrong to have it remove VPATH
: definitions from Makefiles. Historically I'm sure it was useful, in a
: previous century, in a pr
