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
The logic tries to figure out what the path separator in the $PATH
variable is, but if there's only one directory in the $PATH it
fails. This change make configure *guess* on colon instead of erroring
out, simply because that is probably the more common character.
PATH_SEPARATOR can always be set by the user to override the guessing.
(tricky bug to reproduce, as in my case for example the configure script
requires binaries in more than one directory so passing in a PATH with a
single dir fails.)
Reported-by: Earnestly on github
Fixes#2202
When setting
PATH
to a single item, such as/bin
the./configure
script fails as it cannot determine aPATH_SEPARATOR
.Providing either
PATH=/bin:junk
or manually settingPATH_SEPARATOR
works around this issue.You can reproduce this by running
env -i HOME="$HOME" PATH=/bin ./configure
The text was updated successfully, but these errors were encountered: