Automated Code Analysis

checkbashisms analysis of cmor_2.5.3-1.dsc

possible bashism in ./configure line 1936 (should be 'b = a'):
if test "-"${enable_verbose_test} == "-yes" ; then
possible bashism in ./configure line 1941 (should be 'b = a'):
if test "-"${enable_verbose_test} == "-yes" ; then
possible bashism in ./configure line 1950 (should be 'b = a'):
if test "x${enableval}" == "xyes" ; then
possible bashism in ./configure line 1971 (should be 'b = a'):
if test ${enable_debug} == "yes" ; then
possible bashism in ./configure line 1985 (should be 'b = a'):
if test ${enable_fortran} == "-no" ; then
possible bashism in ./configure line 4262 (should be 'b = a'):
    if  test ${HAS_NCCONFIG} == "yes"  ; then
possible bashism in ./configure line 4403 (should be 'b = a'):
if  test ${HAS_NC4} == "no"  ; then
possible bashism in ./configure line 4471 (should be 'b = a'):
  if  test ${HAS_NCCONFIG} == "yes"  ; then
possible bashism in ./configure line 4544 (should be 'b = a'):
    if test ${BUILD_NC3} == "yes"  ; then
possible bashism in ./configure line 5648 (should be 'b = a'):
if test ${enable_fortran} == "-no" ; then
possible bashism in ./configure line 5695 (should be 'b = a'):
if test ${BUILD_NC3} == "no"  ; then
possible bashism in ./configure line 5696 (should be 'b = a'):
  if test ${HAS_NC4} == "yes"  ; then
possible bashism in ./configure line 5719 (should be 'b = a'):
if test "-"${PYTHONEXEC} == "-" ; then

---