summaryrefslogtreecommitdiffstats
path: root/eval.c
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2025-02-18 22:33:32 -0800
committerKaz Kylheku <kaz@kylheku.com>2025-02-18 22:33:32 -0800
commitca3098fd635c3368ad161b03e44e2e6a742b314e (patch)
tree4aace410531ecb60a7b6f956eabcc536196a5cde /eval.c
parent724981f71ca154851ad8836e3284b082147db4bb (diff)
downloadtxr-ca3098fd635c3368ad161b03e44e2e6a742b314e.tar.gz
txr-ca3098fd635c3368ad161b03e44e2e6a742b314e.tar.bz2
txr-ca3098fd635c3368ad161b03e44e2e6a742b314e.zip
configure: fix bad gcc verison check.
* configure: The way the verison is represented in the output of gcc varies. A vendor build version may be indicated in parentheses, and that may precede or follow the version number by itself. I don't know all the variations. What I'm implementing here is looping over the white-space separated output of gcc --version, looking for an item of the form number.number.number where number is any decimal string from 0 to 99 with no leading zero, except for zero itself. If we find this item, we assume that is the gcc version, and break it up and process it as before, terminating the loop. We print the parsed gcc version in parentheses to help with spotting problems.
Diffstat (limited to 'eval.c')
0 files changed, 0 insertions, 0 deletions