On 13/12/2017 00:35, DJ Lucas wrote: > On December 12, 2017 3:52:21 PM CST, Pol Vangheluwe > <[email protected]> wrote: >> >>> Op 9 dec. 2017, om 19:31 heeft Pol Vangheluwe >> <[email protected]> het volgende geschreven: >>> >>> After a lot of trial and error, I finally could finish the build of >> LFS-8.1-systemd with ALFS. >>> I have now modified the make file to also build the BLFS >> preparations, but the first step (openssl-1.1.0f) fails. >>> I find this in the logfile: >>> >>> pol@PowerMac-G5:/mnt/build_dir/blfs_root$ cat work/logs/002-z-openssl >>> openssl-1.1.0f.tar.gz: OK >>> Operating system: ppc64-whatever-linux2 >>> WARNING! If you wish to build 64-bit library, then you have to >>> invoke './Configure linux-ppc64' *manually*. >>> >>> (…) >>> >>> Configuring for linux-ppc >>> >>> (…) >>> >>> THIRTY_TWO_BIT mode >>> BN_LLONG mode >>> RC4 uses unsigned char >>> >>> Configured for linux-ppc. >>> >>> (…) >>> >>> In file included from /usr/include/features.h:447:0, >>> from /usr/include/assert.h:35, >>> from crypto/aes/aes_ecb.c:10: >>> /usr/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-32.h: No such >> file or directory >>> # include <gnu/stubs-32.h> >>> ^~~~~~~~~~~~~~~~ >>> compilation terminated. >>> In file included from /usr/include/features.h:447:0, >>> from /usr/include/assert.h:35, >>> from crypto/aes/aes_core.c:39: >>> /usr/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-32.h: No such >> file or directory >>> # include <gnu/stubs-32.h> >>> ^~~~~~~~~~~~~~~~ >>> compilation terminated. >>> make[2]: *** [Makefile:689: crypto/aes/aes_ecb.o] Error 1 >>> make[2]: *** Waiting for unfinished jobs.... >>> make[2]: *** [Makefile:681: crypto/aes/aes_core.o] Error 1 >>> make[2]: Leaving directory '/sources/openssl/openssl-1.1.0f' >>> make[1]: *** [Makefile:128: all] Error 2 >>> make[1]: Leaving directory '/sources/openssl/openssl-1.1.0f' >>> >>> So it looks like the system is trying to build the 32-bit version, >> while my libs are 64-bit. >>> This is my first LFS-build on a 64-bit machine (an iMac-G5) and I had >> to modify several LFS command files to make the build succeed. >>> >>> Could it be that I have overlooked something during the LFS-build, >> that now causes this problem or am I doomed to again patch a lot of >> command files to make them run on ppc64? >>> >>> BTW: I have not yet tried the suggestion above to invoke ‘./Configure >> linux-ppc64’ >>> >> If you try, you’ll know… >> So, I replaced: >> >> --openssldir=/etc/ssl \ >> --libdir=lib \ >> shared \ >> zlib-dynamic && >> make >> >> by: >> >> ./Configure --prefix=/usr \ >> --openssldir=/etc/ssl \ >> --libdir=lib \ >> shared \ >> zlib-dynamic \ >> linux-ppc64 && >> make >> >> and could continue untill 012-z-cacerts, where wget is needed, but that >> is only being built with 013-z-wget. >> >> we’re progressing… >> >> pvg > > Use make-ca from the development book as it uses openssl s_client to download > the certs. >
On the cacert page, wget is only needed for downloading files. But wget needs cacerts. That's why, if you tick "Add blfs-tool support", jhalfs downloads the necessary files for cacerts before entering chroot, and removes the instructions using wget from the cacerts script. So normally, the cacert script should run OK. Now, as DJ wrote above, if you use the development version of the cacert script, wget is not needed either. Pierre -- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
