You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per haskell/cabal#2015, it seems Cabal caches the $PATH when running configure and reuses it later. As a result, if a package needs a particular program on $PATH at compile time, a user who modifies their $PATH after a failure will continue to remain in a failure state until running a stack clean. Perhaps the $PATH should be considered an input dependency of configure steps?
The text was updated successfully, but these errors were encountered:
Good to know! Yes, I think it makes sense to do a reconfigure. The alternative would be to just make this a warning, but that could easily be ignored. Marking as P1 since it has to do with build determinism
Fixing this will probably invalidate previous configure cache info, so ideally would be batched with any other pending changes to it. Would be possible to have support for reading the old cache version.
As per haskell/cabal#2015, it seems Cabal caches the
$PATH
when runningconfigure
and reuses it later. As a result, if a package needs a particular program on$PATH
at compile time, a user who modifies their$PATH
after a failure will continue to remain in a failure state until running astack clean
. Perhaps the$PATH
should be considered an input dependency of configure steps?The text was updated successfully, but these errors were encountered: