On Thu, 16 Mar 2000, David Bushong wrote:
> > Well, I couldn't replicate this when I tried (under several different
> > conditions). The only bug I found with compiling without crypto support
> > was in tcpdump. Perhaps you have a stale /usr/obj?
> >
> I got this exact behavior from having only src-all in my supfile, and not
> cvs-crypto.
I still can't replicate this. I did the following:
1) cvsupped to 4.0-stable (4.0-release would be no different here, as
nothing has changed to affect it except the tcpdump fix).
2) Blew away all traces of the installed crypto libraries/headers from my
system.
3) Blew away my entire crypto/ and secure/ source directories
4) Did a 'make world'.
It completed with no problems, and I also completed several other
variations also with no problems. The only conclusion I can draw is that
you have something stale about your system, perhaps old files in crypto/
or secure/ which it is detecting and trying to build with (or even just
empty directories, although that breaks earlier in the build and always
will have).
Kris
----
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
