Awk command line options behaviour on Solaris 10 changes.
---------------------------------------------------------
Key: MODPYTHON-228
URL: https://issues.apache.org/jira/browse/MODPYTHON-228
Project: mod_python
Issue Type: Bug
Components: core
Affects Versions: 3.3.1
Reporter: Graham Dumpleton
Priority: Minor
Configure script uses:
AC_MSG_CHECKING(flex version)
FlexVERSION=`$LEX --version | sed 's/version//g' | awk '/flex/ {print $2}'`
Flex_MAJOR=`echo $FlexVERSION| awk -F . '{print $1}'`
Flex_MINOR=`echo $FlexVERSION| awk -F . '{print $2}'`
Flex_PATCH=`echo $FlexVERSION| awk -F . '{print $3}'`
Problem is that on Solaris 10 the awk program was changed so as not to accept a
space after the -F option.
Ie., on Solaris 9 the manual page says:
/usr/bin/awk [-f progfile] [-F c] [ ' prog '] [parameters] [filename...]
But on Solaris 10 it says:
/usr/bin/awk [-f progfile] [-Fc] [ ' prog '] [parameters] [filename...]
This means that if flex version check performed on Solaris 10 the awk command
will fail.
checking flex version... awk: syntax error near line 1
awk: bailing out near line 1
awk: syntax error near line 1
awk: bailing out near line 1
awk: syntax error near line 1
awk: bailing out near line 1
./configure: line 3187: test: : integer expression expected
For further details see:
http://www.modpython.org/pipermail/mod_python/2007-March/023230.html
Configure script should perhaps search for presence of 'gawk', 'nawk' and 'awk'
in that order. That way it will give preference to BSD awk variants rather than
SYSV variant which can be different in other respects as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
