Re: compilation error

[Werner LEMBERG]

> > Your fix has a nasty side effect.

Oops!  It's not your fix which causes the problem, sorry.  *All* tests
for header files show

  checking XXX usability... no
  checking XXXpresence... no
  checking for XXX... no

since the CPPFLAGS value isn't set correctly.  From config.log:

  CPPFLAGS='-I/usr/include/python2.5 \
            -I/usr/include/python2.5 \
            -fno-strict-aliasing \
            -march=i586 \
            -mtune=i686 \
            -fmessage-length=0=2 \
            -g '

  cc1: error: argument to "-fmessage-length=" should be a non-negative integer

For example, a compilation with the git repository from Oct. 30th gives

  CPPFLAGS='-I/usr/include/python2.5 '

Note that `python-config --cflags' gives

  -I/usr/include/python2.5 \
  -I/usr/include/python2.5 \
  -fno-strict-aliasing \
  -DNDEBUG \
  -O2 \
  -march=i586 \
  -mtune=i686 \
  -fmessage-length=0 \
  -Wall \
  -D_FORTIFY_SOURCE=2 \
  -g

on my system.  The origin of the problem is now obvious: The line

  PYTHON_CFLAGS=`$PYTHON_CONFIG --cflags | sed -e 's/ 
-\(W\|D\|O\)\(\w\|-\)\+//g'`

in stepmake/aclocal.m4 doesn't correctly remove some of the compiler
options.


     Werner