On 24/05/2018 03:37, Christopher Gregory wrote: > [...] > > I re-installed openssl-1.1.0g and the objdump command did have some output. > > I then re-compiled openssh with patch and it compiled and installed > without any issues. > > The only thing I can think of that caused openssh to not install before, > is that in jhalfs (managed to work out that the tag to use there to > download was 8.2)
I thought I had answered that mail, but I clicked on "Reply" instead of "Reply list", and for some reason, my ISP did not want to deliver to your private address. Forgot to resend to the list. Sorry. > I asked the final build to use -j12 for compiling > everything. I do not ever strip the builds. Harddrives are so cheap > these days and I do not do any programming nor extensive graphics work so > I am quite happy leaving well enough alone. > > This time when I re-installed openssl-1.1.0g I made sure to pass -j1 to > make. I also passed the -j1 command to openssh as well. > > It may well be that with me installing the older version of openssl (again > using -j1) that things got corrected, and then it made it smooth sailing > for the re-installation of openssl-1.1.0g. > > I do not know if it is possible in jhalfs, or if it would be too much work > to add an exception to the code for openssl to only compile with the -j1 > switch even if people have selected -jxx for the rest of the build? > This problem had been addressed in jhalfs much before I took over on it: Just add the package to the BLACK_LIST variable in optimize/opt_config. BLACK_LIST="$BLACK_LIST openssl" (for this example). Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
