Hello!
> > `+' after `*' isn't portable, IIRC. In fact, I don't understand what
> > we're trying to accomplish with that construct. It makes no sense at
> > all to me.
If it's not portable let's use '^ *[+]' to be on the safe side. Both grep
and egrep 2.4.2 interpret is in the way it was intended - literal plus
sign after spaces (0 or more) in the begginning of string.
Mathieu, the original author of the report, must have had a different
problem but he got confused by this regular expression.
My understanding is that his "gcc -E" outputs some error to the stderr
that is not (and should not be) filtered out. egrep would filter out
everything (since '+' matches one or more symbols) but it is not the right
solution.
Mathieu, could you please add "copy conftest.out save.out; exit" after the
line containing "grep -v" and analyze save.out after running configure?
Regards,
Pavel Roskin
