Bugs item #313603, was opened at 2012-04-09 19:26 You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313603&group_id=100114
Status: Open Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: invoking make implicitly Distribution: None Originally reported in: None Milestone: None Status: None Original bug number: Initial Comment: Anonymous message posted by lb.w...@gmail.com Hey. It seems bash-completion can lead to targets in makefiles being built without ever invoking make. It suffices to type "make <tab>" in order to get a list of possible targets. This is how I can reproduce such behavior on my system: 1. Create a file 'makefile' with these contents: #start of makefile weird_file: touch weird_file include weird_file #end of makefile 2. Type "make " in its directory and hit <tab> That's it. Now "weird_file" exists in that directory. Hitting enter is unnecessary. I'm using bash-completion 1.99 and GNU make 3.82 from the official Arch GNU/Linux repositories. If other systems don't show the same behavior I can add more information about my system. The GNU make manual says at http://www.gnu.org/software/make/manual/make.html#Include : If an included makefile cannot be found in any of these directories, a warning message is generated, but it is not an immediately fatal error; processing of the makefile containing the include continues. Once it has finished reading makefiles, make will try to remake any that are out of date or don't exist. Thanks for bash-completion :) best regards. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313603&group_id=100114 _______________________________________________ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel
