[Git][NTPsec/ntpsec][master] Explicitly check for m4 during configure to avoid surprises later
Matt Selsky
gitlab at mg.gitlab.com
Mon Mar 5 05:51:33 UTC 2018
Matt Selsky pushed to branch master at NTPsec / ntpsec
Commits:
7ea832b9 by Matt Selsky at 2018-03-05T05:29:57Z
Explicitly check for m4 during configure to avoid surprises later
If bison can't find m4 at build time, it throws a non-obvious error.
Fix GitLab issue #464
- - - - -
1 changed file:
- wscript
Changes:
=====================================
wscript
=====================================
--- a/wscript
+++ b/wscript
@@ -123,6 +123,8 @@ def configure(ctx):
ctx.load('compiler_c')
ctx.start_msg('Checking compiler version')
ctx.end_msg("%s" % ".".join(ctx.env.CC_VERSION))
+ # Ensure m4 is present, or bison will fail with SIGPIPE
+ ctx.find_program('m4')
ctx.load('bison')
for opt in opt_map:
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/7ea832b9b9b4d16837700e225b53c174c35ddf3e
---
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/7ea832b9b9b4d16837700e225b53c174c35ddf3e
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20180305/099267c4/attachment.html>
More information about the vc
mailing list