#6094: runInteractiveProcess not using new PATH
-------------------------------+--------------------------------------------
Reporter: GregWeber | Owner:
Type: task | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.4.1
Resolution: | Keywords:
Os: Unknown/Multiple | Architecture: Unknown/Multiple
Failure: None/Unknown | Difficulty: Unknown
Testcase: | Blockedby:
Blocking: | Related:
-------------------------------+--------------------------------------------
Comment(by simonmar):
I think there may be a misunderstanding here. The `PATH` you set is
definitely used: it becomes the `PATH` of the new process. But in order
to find the executable to run, the `PATH` of the current process is used.
There's nothing magic about this process, we just use
`System.Directory.findExecutable` which searches the `PATH` to find the
full pathname of the executable. So all you have to do is implement your
own version of `findExecutable` (it's only a few lines) and then pass the
full pathname to `runInteractiveProcess`.
By all means submit an update to the documentation, I can understand how
one might expect it to work differently, but I hope you'll agree the way
it currently works does make sense too.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/6094#comment:5>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
