[bug #43550] Compiling files in a directory with the same name as the source code fails

Follow-up Comment #2, bug #43550 (project make): Sorry, "... non-phony targets should update a single FILE with the same name as the target ..." ___ Reply to this item at: _

[bug #43550] Compiling files in a directory with the same name as the source code fails

Follow-up Comment #1, bug #43550 (project make): "foo" in the Makefile refers to the directory "foo". Because the directory has no prerequisites, it is considered up to date as long as it exists (up-to-date means newer than all prerequisites). In general, non-phony targets should update a single

[bug #43378] $(guile ...) must be coaxed to accept (or does not accept) valid guile code.

Follow-up Comment #3, bug #43378 (project make): Ah, I see. The #nil trick is a decent enough workaround, although it will be mystifying to anyone reading the code at first glance. I wonder if a just plain empty string would work? Anyway, I'll need to look over my code to see if there are any o

[bug #43378] $(guile ...) must be coaxed to accept (or does not accept) valid guile code.

Follow-up Comment #1, bug #43378 (project make): I just realized that the sharps can be escaped with backslash (not sure why that didn't occur to me before). However, the other problematic characters can't be handled this way: if I enter a ! in $(guile), both characters get passed through to the

[bug #43378] $(guile ...) must be coaxed to accept (or does not accept) valid guile code.

URL: Summary: $(guile ...) must be coaxed to accept (or does not accept) valid guile code. Project: make Submitted by: ahmedtd Submitted on: Wed 08 Oct 2014 12:27:13 AM GMT Severity: 3

[bug #43221] Random string corruption when recursively evaluating guile code.

URL: Summary: Random string corruption when recursively evaluating guile code. Project: make Submitted by: ahmedtd Submitted on: Sun 14 Sep 2014 07:38:49 AM GMT Severity: 3 - Normal