On Sep 21, 2005, at 2:13 PM, David Smith wrote:
OK, here's a cleaner solution. It does this the "right" way using a
cached config variable.
So should that be applied to the configure.in *before* your previous
patch?
If so, does it mean that there's no need to have the user say where
th
On Wed, 2005-09-21 at 11:47, Guy Harris wrote:
> David Smith wrote:
>
> > At first I tried to do this the "right" way of using a cached configure
> > variable, but the ac_cv_ssleay_path code is a bit too complicated for
> > that, since it actually sets two variables - ac_cv_ssleay_path and
> > inc
David Smith wrote:
At first I tried to do this the "right" way of using a cached configure
variable, but the ac_cv_ssleay_path code is a bit too complicated for
that, since it actually sets two variables - ac_cv_ssleay_path and
incdir.
So, this Xprefix change is a bit of a hack, but not *too* g
CVS log entries from 20.09.2005 (Tue) 09:05:19 - 21.09.2005 (Wed) 09:05:20 GMT
=
Summary by authors
=
Author: hannes
File: tcpdump/print-isoclns.c; Revisions: 1.152, 1.133.2.19
Fi
