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

2008-11-27 Thread Ralf Wildenhues
* Mike Frysinger wrote on Thu, Nov 27, 2008 at 08:52:32PM CET: > On Thursday 27 November 2008 14:33:44 Aleksander Morgado wrote: > > >> test_SOURCES = config.h \ > > >>$(srcdir)/src/module//test.c > sorry, i missed that part. as Ralf stated, i imagine that's a bug with how > GNU

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

2008-11-27 Thread Mike Frysinger
On Thursday 27 November 2008 14:33:44 Aleksander Morgado wrote: > >> Also, if I use $(srcdir) to mark the top level path of the sources, it > >> won't crash. But not sure if this is the best way to have it: > >> > >> test_SOURCES = config.h \ > >>$(srcdir)/src/module//test.c > > > >

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

2008-11-27 Thread Aleksander Morgado
Also, if I use $(srcdir) to mark the top level path of the sources, it won't crash. But not sure if this is the best way to have it: test_SOURCES = config.h \ $(srcdir)/src/module//test.c afaik, this is correct. the issue has nothing to do with multiple slashes, but your Makefi

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

2008-11-27 Thread Mike Frysinger
On Tuesday 25 November 2008 05:16:09 Aleksander Morgado wrote: > Also, if I use $(srcdir) to mark the top level path of the sources, it > won't crash. But not sure if this is the best way to have it: > > test_SOURCES = config.h \ >$(srcdir)/src/module//test.c afaik, this is correct

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

2008-11-26 Thread Aleksander Morgado
Hi all, >>> 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 your code. > >> The reported issue is unexpected since: >> $ echo 'int main() { return(0);}'

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

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