OpenSSH 2.4.0 patch call..

[mouring at etoh.eviladmin.org]

On Fri, 29 Dec 2000, Lutz Jaenicke wrote:

> On Fri, Dec 29, 2000 at 04:30:05PM -0600, mouring at etoh.eviladmin.org wrote:
> > > 	.c.o:
> > > 		$(CC) $(CFLAGS) $(CPPFLAGS) -c $<
> > > This way it should work for all platforms.
> > > (Another commonly used way is to start in Makefile with something like
> > > CFLAGS= $(CFLAGS) $(CPPFLAGS) or similar.)
> > > 
> > That's simple enough.  However if it's not being honored within
> > 'configure' (as it is not on NeXT) then I may opt to just back out of the
> > CPPFLAGS/CFLAGS patch.  (If all that is affected is NeXT then I'll just
> > look for a NeXT work around.)
> 
> I don't care for either solution, as long as it works :-)
> It may however also be practical to fix "configure". Distinguishing between
> CFLAGS and CPPFLAGS is a normal practice when using autoconf. My experience
> is that typically "configure" manages to handle CFLAGS and CPPFLAGS
> consistently and then later CPPFLAGS is not used in Makefile.in...
> That reminds me to send an error message stating that and some things more
> to the author of wvware/libwmf (wordviewer for windows)...
> 
> What is your problem with "configure"?
> 
hmmmm.. I'll retract my comment about ./configure not working right with a
split CPPFLAGS/CFLAGS.  I seem to have bits of another patch I was working
on causing the problems.

- Ben