On 21 May 16:50, Egon Ozer wrote: > It looks like, for whatever reason, you have to feed options directly to the > make command rather than modifying options in the Makefile. > Why? I thought maybe it was the spaces flanking the "=" sign in the > Makefile, but when I removed them (i.e. "HAVE_LIBZ=y" instead of > "HAVE_LIBZ = y"), the error still recurred.
Sorry for resurrecting this, but I found another possible reason why this may be happening. The GNU make manual indicates that variables inside a top-level makefile will not be sent down to sub-makefiles unless they are exported: http://www.gnu.org/software/make/manual/html_node/Variables_002fRecursion.html "The behavior elicited by an export directive by itself was the default in older versions of GNU make." I fixed this issue for me by putting an 'export' in the lines where these variables were set. Maybe it will work for other people. Of course, then there's another web page that suggests using include statements rather than a recursive make, which would also fix this (but is much more work): http://miller.emu.id.au/pmiller/books/rmch/ - David Eccles (who has a new need for Ray, and is now working on genomic sequence from human samples) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Denovoassembler-users mailing list Denovoassembler-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/denovoassembler-users
