Herold Heiko <[EMAIL PROTECTED]> writes:
>> would insert `make distclean' before the second configure, or *at
>> least* `rm config.cache'.
>
> Exactly my point - shouldn't either everything handled gracefully, or
> cleaned up automatically when necessary (in ./configure ?),
I don't think so. D
> From: Hrvoje Niksic [mailto:[EMAIL PROTECTED]]
> Herold Heiko <[EMAIL PROTECTED]> writes:
>
> > make -f Makefile.cvs
> > ./configure
> > make
> > ./configure --with-ssl
> > make
>
> Isn't this a bit dangerous, what with Autoconf caches and all? I
Most probably.
> would insert `make distclea
Herold Heiko <[EMAIL PROTECTED]> writes:
> make -f Makefile.cvs
> ./configure
> make
> ./configure --with-ssl
> make
Isn't this a bit dangerous, what with Autoconf caches and all? I
would insert `make distclean' before the second configure, or *at
least* `rm config.cache'.
linux, a machine with ssl libs and headers installed in /usr/local .
Current cvs sources,
make -f Makefile.cvs
./configure --with-ssl
make
works flawlessly. On the other hand, starting over again with clean
sources,
make -f Makefile.cvs
./configure
make
./configure --with-ssl
make
fails with
