Re: Double '/' in source path breaks compilation if done from a directory not where the Makefile.am resides

2008-11-25 Thread Ralf Wildenhues
Hello Roumen, * Roumen Petrov wrote on Wed, Nov 26, 2008 at 12:25:45AM CET: > Ralf Wildenhues wrote: >> >> Not flattening multiple consecutive slashes in prerequisite names for >> VPATH searches is a GNU make limitation, AFAICS undocumented. >> Not coping with this limitation is arguably a bug in

Re: missing help2man

2008-11-25 Thread Werner LEMBERG
> I suggest that in case help2man isn't found, the dummy version > of info.1 gets removed (perhaps by adding `|| rm -f $@ && false' > to the rules using HELP2MAN). > > Although I could change this in Texinfo as you suggest, it seems to > me it affects every package using help2man and t

Re: Double '/' in source path breaks compilation if done from a directory not where the Makefile.am resides

2008-11-25 Thread Roumen Petrov
Ralf Wildenhues wrote: Hello Aleksander, * Aleksander Morgado wrote on Tue, Nov 25, 2008 at 11:16:09AM CET: Not sure if this is a bug in automake, in make itself, or in my code, but anyway I'll explain what happens. Not flattening multiple consecutive slashes in prerequisite names for VPATH s

missing help2man

2008-11-25 Thread Karl Berry
Hi everyone, (Automake folks: Werner sent the following to bug-texinfo.) I've just tried to compile texinfo from the CVS; everything worked fine until info.1 was generated -- no help2man was installed on my system. After fixing this, building succeeded. However, I've observed on

Re: Double '/' in source path breaks compilation if done from a directory not where the Makefile.am resides

2008-11-25 Thread Ralf Wildenhues
Hello Aleksander, * Aleksander Morgado wrote on Tue, Nov 25, 2008 at 11:16:09AM CET: > > Not sure if this is a bug in automake, in make itself, or in my code, > but anyway I'll explain what happens. Not flattening multiple consecutive slashes in prerequisite names for VPATH searches is a GNU mak

Double '/' in source path breaks compilation if done from a directory not where the Makefile.am resides

2008-11-25 Thread Aleksander Morgado
Hi all, Not sure if this is a bug in automake, in make itself, or in my code, but anyway I'll explain what happens. I prepare a simple Makefile.am in my project, a single Makefile.am for the whole project (not multiple Makefile.am in different directories), where I compile one binary with one so