From 24a492683ca02f234d727740f03c1fb2949f2b44 Mon Sep 17 00:00:00 2001 From: Dan Gohman Date: Thu, 28 Oct 2010 20:34:33 +0000 Subject: [PATCH] Revert r117582, which reverted r77396. Searching PATH for a string which contains slashes is inconsistent with the meaning of PATH on Unix-type platforms, and pretty surprising. If the user has given a specific path to execute and we can't execute it, we should fail and say why. (Apparently the new posix_spawn code doesn't always say why, but that's a separate issue.) git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@117596 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/System/Unix/Program.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/System/Unix/Program.inc b/lib/System/Unix/Program.inc index 3741bf8e6ba..110a6d14f48 100644 --- a/lib/System/Unix/Program.inc +++ b/lib/System/Unix/Program.inc @@ -63,7 +63,7 @@ Program::FindProgramByName(const std::string& progName) { return Path(); // Use the given path verbatim if it contains any slashes; this matches // the behavior of sh(1) and friends. - if (progName.find('/') != std::string::npos && temp.canExecute()) + if (progName.find('/') != std::string::npos) return temp; // At this point, the file name does not contain slashes. Search for it -- 2.34.1