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 errors because of syntax errors in the use of test shell command #3517

Closed
ackalker opened this issue May 21, 2019 · 2 comments · Fixed by #3518
Closed

configure errors because of syntax errors in the use of test shell command #3517

ackalker opened this issue May 21, 2019 · 2 comments · Fixed by #3518

Comments

@ackalker
Copy link
Contributor

ackalker commented May 21, 2019

Please use this template for reporting suspected bugs or requests for help.

Issue description

On my system, where /bin/sh -> /bin/dash, runnung ./configure produces errors which I tracked down to configure.ac and acinclude.m4 using the test shell command with a == operator, syntax which is not valid in a POSIX-like shell like dash. See man 1p test for details.

Environment

  • libzmq version (commit hash if unreleased): cef8065
  • OS: Void Linux x86_64

Minimal test code / Steps to reproduce the issue

  1. Run ./autogen.sh
  2. Run ./configure

What's the actual result? (include assertion message & call stack if applicable)

[...output from step 2...]
./configure: 21529: test: x: unexpected operator
./configure: 21534: test: unexpected operator

Full output of running the repro steps on my system:
step 1: output
step 2: output.

What's the expected result?

Running configure should produce no such errors.

@ackalker ackalker changed the title configure errors because of Bashisms: test <x> == <y> configure errors because of syntax errors in the use of test shell command May 21, 2019
@bluca
Copy link
Member

bluca commented May 21, 2019

Could you please send a PR to fix it?

@ackalker
Copy link
Contributor Author

Will do, I'm already on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants