> > I don't recall for any problems for 8.1 but that was about nine months > ago. I just checked with openssl 1.1.0h and had no warnings or errors. > > -- Bruce
I'm not clear. I had no problem installing openssl-1.1.0f either. It was vsftpd that, if I'm interpretting things right, couldn't find the include files in /usr/include/opsnssl. > Not a package I use, and the only obvious change in the book since > 8.1 is adding libnsl which I assume is not required on the older > glibc. vsf_findlibs.sh finds the libraries fine, including that one. At linking it complains about many undefined SSL symbols in one of the files it compiled without complaint. I'm presuming those should have come from the installed include files. > > Paul might care to google for arch-linux vsftpd : their build file Paul does care to, > shows a change to the conf to apparently enable SSL, and a sed to > link to openssl-1.1. if Paul could find the page to which you refer. > > As always, I cannot recommend using an old version of openssl ;-) I agree, but that can hardly explain my build failure, and presumably the BLFS devs compiled vsftpd-3.0.3 with openssl-1.1.0f as given in the book. > But fixing that means taking steps to fix make-ca. If Paul looked > at a recent version of the svn book with openssh-1.1.0h and > make-ca-0.7, the fix should be there, make-ca-0.8 should be ok. Paul has the 5/22 svn, which only has openssl-1.0.2o! -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
