Matthew Reimer wrote: > > Do you have the openssl port installed? Since openssl was imported to > -stable, the port is not necessary and can actually get in the way. Try > deleting it (pkg_delete openssl-xxx). > > BTW, same goes for the ssh port. No, I haven't installed either of those. This box started life running 4.2-RELEASE. The only thing I changed today was cvsup-ing to -STABLE. It did "Checkout src/secure/lib/libssl/Makefile" however. Hm. Kris, oh, Kris... <g>. I did a diff betwixt -RELEASE and -STABLE, guess what. The usual change in the header, most of the changes were due to cleanup in whitespaces, but one stuck out: 14,19c14,19 < SRCS+= bio_ssl.c s23_clnt.c s23_lib.c s23_meth.c s23_pkt.c s23_srvr.c \ < s2_clnt.c s2_enc.c s2_lib.c s2_meth.c s2_pkt.c s2_srvr.c s3_both.c \ < s3_clnt.c s3_enc.c s3_lib.c s3_meth.c s3_pkt.c s3_srvr.c ssl_algs.c \ < ssl_asn1.c ssl_cert.c ssl_ciph.c ssl_err.c ssl_err2.c ssl_lib.c \ < ssl_rsa.c ssl_sess.c ssl_stat.c ssl_txt.c t1_clnt.c t1_enc.c \ < t1_lib.c t1_meth.c t1_srvr.c --- > SRCS+= bio_ssl.c s23_clnt.c s23_lib.c s23_meth.c s23_pkt.c s23_srvr.c \ > s2_clnt.c s2_enc.c s2_lib.c s2_meth.c s2_pkt.c s2_srvr.c \ > s3_both.c s3_clnt.c s3_enc.c s3_lib.c s3_meth.c s3_pkt.c \ > s3_srvr.c ssl_algs.c ssl_asn1.c ssl_cert.c ssl_ciph.c \ > ssl_err.c ssl_err2.c ssl_lib.c ssl_rsa.c ssl_sess.c ssl_stat.c \ > ssl_txt.c t1_clnt.c t1_enc.c t1_lib.c t1_meth.c t1_srvr.o \ Indeed the patched release has one modifcation too many. I'll see what'll happen when I patch the patch and rebuild. Not that I'm voluntering, mind :)... but I think the development of a standardised test suite would be a good thing. A major undertaking given the complexity no doubt. Yet such a suite has more repeatability than mere wetware humans. Ah well, one can dream. Roelof PS if it works out I'll submit a PR -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
