e obviously not worth doing anything gross like figuring out
>> whether the command is "test", whether "test" exists on the PATH, or
>> whether it's a shell script, or anything like that.
I don't think the fix will penalize in Real World, because
- As
hould be faster.
Well Linux and *BSD uses binary /bin/test so slow path is slower.
If speed is at premium for bare "test",
you can detect the shellscriptness of the /bin/test and switch accordingly
in the configure
(which is a mess, and doesn't gain mu
rfs if it wasn't generated, and signals the FAIL of the test)
The point is not the slow path but the return code to
let the make **Stop.
--
kabe
___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make
(Also submitted as BugID 7606)
(Platform: QNX 6.2.0)
* When a "test" command is a shell builtin, and
* no /bin/test as a file is provided in the system,
all:
test
will fail with "make: test: Command not found" .
You could easily reproduce this by setting PATH to bogus path, as
$ PATH=/no
