Stephen J. Turnbull wrote:
Ron Isaacson writes:
> You might argue that #1 is our problem, and that if you specify
> --with-cppflags, that's an override to the default behavior of
> inheriting CPPFLAGS. We've got an easy workaround for that, but it
> still might be something to consider.
It's not properly documented, so that's our problem.
Does `configure --with-cppflags="-newflag $CPPFLAGS" ...' work in your
Yup, that was exactly the workaround we found. Real tricky. :-)
I think that having the `--with-WHATEVERflags' options
override the corresponding environment variables is easier to
explain. It's certainly easier to code!
This option overrides the environment. If you wish to include the
flags that may have been specified in CPPFLAGS, this must be done
explicitly: `--with-cppflags="-addlflag $CPPFLAGS"'.
I think that would do the trick.
Incidentally, once we got this sorted out, customize-face did indeed
work, both with xft and without! Go figure!
ron.isaacson(a)morganstanley.com / (212) 276-0268
NOTICE: If received in error, please destroy and notify sender. Sender
does not waive confidentiality or privilege, and use is prohibited.
XEmacs-Beta mailing list