On Feb 12, 2008 4:07 PM, Mike Frysinger <vapier@gentoo.org> wrote: []Oh, this? It's like doing syscall for every write to "/dev/null". At least this will not crash, if you don't have some variable set. Efficiency there is lesser number of variables(-2 vs +2), that are copied for every make job, and are textually parsed and searched. Right. Seems like you are talking about "[quite_]cmd_*", which are commands. Here you've invented such rules for ordinary utility in `filechk`. And by try they've failed due to mixing functionality dependency on having arbitrary variable being set. Shell syntax tried to avoid this, but `make` syntax and ``convention'' did a boom. Boom, where hacker's V=1 mode failed itself and failed to give a clue about problem (at least, when i saw Sam's message in linux-kbuild). Yea, `make` is not needed. -- -o--=O`C #oo'L O <___=E M --
| Linus Torvalds | Linux 2.6.27-rc5 |
| Greg Kroah-Hartman | [PATCH 007/196] Chinese: add translation of stable_kernel_rules.txt |
| Kamalesh Babulal | [Build Failure] 2.6.25-rc5-mm1 Build fails with allmodconfig probe_4drives undefined |
| Gabriel C | Re: Linus 2.6.23-rc1 |
| David Woodhouse | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
git: | |
