On 12/19/18 3:55 PM, Hauke Fath wrote:
When I configure with '--cpp=/usr/bin/cpp', the script
be damned if I understand how configure finds and picks a cpp(1), and
how after all this byzantine scripting it does not even bother to check
its pick actually exists, to error out a thousand lines later.
I happened to come across <http://gnats.netbsd.org/53686>
;, where people
dealt with a similar problem for pdksh.
The resulting patch to configure
makes sure that preprocessor warnings from ambitious security settings
do not interfere with finding a working cpp(1).
This should go into configure.in, but what really needs to be amended is
the autoconf "AC_PROG_CPP" macro (which is also the source of the crufty
I tried adapting various compiler options for the build, but it didn't
make a difference for the pdump SIGSEV.
The ASCII Ribbon Campaign Hauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
Respect for open standards Ruf +49-6151-16-21344