Re: Circular dependency dropped warning from make in relating to CUDA code

2009-06-29 Thread Adam Mercer
On Mon, Jun 29, 2009 at 20:29, Ralf Wildenhues wrote: > Using $< in inference rules, as in my example, is portable. > In target rules, you can spell out the input file name > (including an eventual vpath prefix). Thanks for the clarification. Cheers Adam

Re: Circular dependency dropped warning from make in relating to CUDA code

2009-06-29 Thread Ralf Wildenhues
* Adam Mercer wrote on Mon, Jun 29, 2009 at 10:19:59PM CEST: > On Sat, Jun 27, 2009 at 05:33, Ralf Wildenhues wrote: > > > (Note also that using $< in target rules is not portable to non-GNU > > make). > > Is there a more portable version? Using $< in inference rules, as in my example, is portab

Re: Circular dependency dropped warning from make in relating to CUDA code

2009-06-29 Thread Adam Mercer
On Sat, Jun 27, 2009 at 05:33, Ralf Wildenhues wrote: Ralf > Why not name the product file CudaChisq.c rather than CudaChisq.cu.c? > The problem here is that the other half of the circle comes from the > make-internal rule `%: %.c' for compiling single-source programs. > I guess you can also avoi

Re: Circular dependency dropped warning from make in relating to CUDA code

2009-06-27 Thread Ralf Wildenhues
Hello Adam, * Adam Mercer wrote on Fri, Jun 26, 2009 at 09:23:03PM CEST: > make: Circular CudaChisq.cu <- CudaChisq.cu.c dependency dropped. > > The following rule is used to generate the .c file from the .cu source: > > CudaChisq.cu.c: CudaChisq.cu > nvcc -cuda --host-compilation=c $(INCL

Re: Circular dependency

2006-11-30 Thread Stepan Kasal
Hello, On Thu, Nov 30, 2006 at 10:24:19AM +0100, Guillaume Rousse wrote: > So, to get back at my original question, what's the proper way of > expressing dependencies for a generated source file through > configure-time substitution: > foo: foo.in config.status > > or, as in autoconf documentat

Re: Circular dependency

2006-11-30 Thread Guillaume Rousse
Stepan Kasal wrote: Hello, On Thu, Nov 30, 2006 at 09:31:19AM +0100, Guillaume Rousse wrote: Stepan Kasal wrote: You specified the dependency: corelib/camlimages.ml <-- Makefile This is not correct. You should specify the ultimate primary sources instead of `Makefile'. Prehaps `Makefile.

Re: Circular dependency

2006-11-30 Thread Stepan Kasal
Hello, On Thu, Nov 30, 2006 at 09:31:19AM +0100, Guillaume Rousse wrote: > Stepan Kasal wrote: > >You specified the dependency: > > > > corelib/camlimages.ml <-- Makefile > > > >This is not correct. You should specify the ultimate primary sources > >instead of `Makefile'. Prehaps `Makefile.am'

Re: Circular dependency

2006-11-30 Thread Guillaume Rousse
Stepan Kasal wrote: You specified the dependency: corelib/camlimages.ml <-- Makefile This is not correct. You should specify the ultimate primary sources instead of `Makefile'. Prehaps `Makefile.am' is enough? It was to catch configure runs, so I used config.status instead. I hope this

Re: Circular dependency

2006-11-28 Thread Stepan Kasal
Hello, On Tue, Nov 28, 2006 at 03:39:37PM +0100, Guillaume Rousse wrote: > Ralf Wildenhues wrote: > > The automake one happens at the time 'automake' is run, the included > > file is literally put into Makefile.in. a nit: the automake-included file does not neceserilly get copied to Makefile.in.

Re: Circular dependency

2006-11-28 Thread Ralf Wildenhues
* Guillaume Rousse wrote on Tue, Nov 28, 2006 at 03:39:37PM CET: > > But I still didn't understood how to force generation at dependencies > using a specific depcomp mode at configure time. I sent a mail regarding > this issue to the list, I didn't received any answer sofar. Oh, I think I simply

Re: Circular dependency

2006-11-28 Thread Guillaume Rousse
Ralf Wildenhues wrote: > Hello, > > * Stepan Kasal wrote on Mon, Nov 27, 2006 at 07:56:20PM CET: >> * Makefile.in <-- .depend >> This is because automake creates Makefile.in from Makefile.am and all >> included files. Your Makefile.am includes .depend. > > To rephrase this more to the point: > a

Re: Circular dependency

2006-11-27 Thread Ralf Wildenhues
Hello, * Stepan Kasal wrote on Mon, Nov 27, 2006 at 07:56:20PM CET: > > * Makefile.in <-- .depend > This is because automake creates Makefile.in from Makefile.am and all > included files. Your Makefile.am includes .depend. To rephrase this more to the point: automake style 'include' is different

Re: Circular dependency

2006-11-27 Thread Stepan Kasal
Hello, On Mon, Nov 27, 2006 at 05:10:46PM +0100, Guillaume Rousse wrote: > Ralf Wildenhues wrote: > > * Guillaume Rousse wrote on Thu, Nov 23, 2006 at 04:46:50PM CET: > >> However, make keep complaining about a circular dependency issue: > >> make[1]: Circular corelib/camlimages.ml <- Makefile dep

Re: Circular dependency

2006-11-27 Thread Guillaume Rousse
Ralf Wildenhues wrote: > Hello Guillaume, > > * Guillaume Rousse wrote on Thu, Nov 23, 2006 at 04:46:50PM CET: >> I'm using this rule to substitute values in a sourcefile: >> corelib/camlimages.ml: Makefile corelib/camlimages.ml.in > [...] > >> As detailed in autoconf documentation >> http://www.

Re: Circular dependency

2006-11-25 Thread Ralf Wildenhues
Hello Guillaume, * Guillaume Rousse wrote on Thu, Nov 23, 2006 at 04:46:50PM CET: > I'm using this rule to substitute values in a sourcefile: > corelib/camlimages.ml: Makefile corelib/camlimages.ml.in [...] > As detailed in autoconf documentation > http://www.gnu.org/software/autoconf/manual/auto