Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configure: error: 'PATH_SEPARATOR' variable not set. Can not continue. #2202

Earnestly opened this issue Dec 29, 2017 · 0 comments


Copy link

Earnestly commented Dec 29, 2017

  • Linux 4.15.0-rc4-mainline
  • GNU Autoconf 2.69
  • GNU automake 1.15.1

When setting PATH to a single item, such as /bin the ./configure script fails as it cannot determine a PATH_SEPARATOR.

Providing either PATH=/bin:junk or manually setting PATH_SEPARATOR works around this issue.

You can reproduce this by running env -i HOME="$HOME" PATH=/bin ./configure

@bagder bagder added the build label Jan 3, 2018
bagder added a commit that referenced this issue Jan 25, 2018
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
@bagder bagder closed this as completed in b7db284 Jan 29, 2018
@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

No branches or pull requests

2 participants