Created a TKLDev VM in Proxmox. initially confused that there was already a "core" folder under "products". Deleted that and used git to get the core files.

Make seemed to run ok until right at the end it gives an error. (see below)

So recreated VM and tried again using the core folder already in TKLDev. Same error.

Last lines of compilation are shown below. 

I can try any ideas you suggest. TKLDev VM is ready to roll.

cp build/root.sandbox/usr/lib/syslinux/modules/bios/vesamenu.c32 build/cdroot/isolinuxcp build/root.sandbox/usr/lib/syslinux/modules/bios/gfxboot.c32 build/cdroot/isolinuxcp build/root.sandbox/boot/vmlinuz-5.10.0-11-amd64 build/cdroot/live/vmlinuzcp build/root.sandbox/boot/initrd.img-5.10.0-11-amd64 build/cdroot/live/initrd.gzrm -f build/cdroot/live/20sandbox.squashfsxorriso -as mkisofs -o build/product.iso -r -J -V core -b isolinux/isolinux.bin -c isolinux/boot.cat -isohybrid-mbr /usr/lib/ISOLINUX/isohdpfx.bin -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e efi.img -no-emul-boot -isohybrid-gpt-basdat build/cdroot/xorriso 1.5.2 : RockRidge filesystem manipulator, libburnia project.Drive current: -outdev 'stdio:build/product.iso'Media current: stdio file, overwriteableMedia status : is blankMedia summary: 0 sessions, 0 data blocks, 0 data, 12.1g freexorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rulesAdded to ISO image: directory '/'='/turnkey/fab/products/core/build/cdroot'xorriso : UPDATE :      16 files added in 1 secondsxorriso : UPDATE :      16 files added in 1 secondsxorriso : NOTE : Copying to System Area: 432 bytes from file '/usr/lib/ISOLINUX/isohdpfx.bin'xorriso : FAILURE : Cannot find path '/efi.img' in loaded ISO imagexorriso : NOTE : -return_with SORRY 32 triggered by problem severity FAILUREmake: *** [/usr/share/fab/product.mk:516: build/product.iso] Error 32

Same error with VMWare ESXi.

Perhaps I am totally misunderstanding the instructions (although they are not difficult) or there is some subtlety missing. Trying to compile LAMP does not get fare before a python mysqldb (?) requirement is not found.

TKLCoredownloaded works fine so some disconnect as to how you do it and the instructions, Let me know what I can try next.

• reply

Thanks Jeremy for your help on these issues.

I did indeed recognise that change to Python3 was causing the problem but had no idea how to correct it.

Updating that line in plan/main AND updating "fab" allowed the compilation to complete. I did test commenting out the line in plan/main but that failed.

Anyway I now have a version of LAMP to test with various photo databases to check that all is well.

Will report back as I test.

Ian

I knew this was not likely to succeed but hopefully the following will be of use.

wordpress/plan/main needs to be amended as follows.

Initial errors showed tinymce and php-gettext were responsible. Modified plan as below:

#include <turnkey/base>#include <turnkey/lamp>libjs-cropper       /* wordpress dep */libjs-jquery        /* wordpress dep */libjs-prototype     /* wordpress dep */libjs-scriptaculous /* wordpress dep */libphp-phpmailer    /* wordpress dep */libphp-snoopy       /* wordpress dep */php-php-gettext         /* wordpress dep */php-gd              /* wordpress dep *///tinymce             /* wordpress dep */php-zip             /* wordpress recommends */php-imagick         /* wordpress recommends */php-curl            /* needed by some plugins */unzip               /* most wordpress plugins and themes are zip archives */

"tinymce" had no target. https://tracker.debian.org/pkg/tinymce seems to indicate it is no longer in Debian.

Compilation then proceeded further  until this error:

rm build/root.patched/etc/resolvconf/resolv.conf.d/originalrm build/root.patched/etc/apt/trusted.gpg~warning: file or directory 'build/root.patched/etc/apt/trusted.gpg~' not found!rm build/root.patched/etc/apt/trusted.gpg.d/debian.gpg~warning: file or directory 'build/root.patched/etc/apt/trusted.gpg.d/debian.gpg~' not found!rm build/root.patched/etc/apt/trusted.gpg.d/turnkey.gpg~warning: file or directory 'build/root.patched/etc/apt/trusted.gpg.d/turnkey.gpg~' not found!rm build/root.patched/var/log/dpkg.logrm build/root.patched/var/log/bootstrap.logrm build/root.patched/var/log/apt/term.logrm build/root.patched/var/log/apt/history.logrm -r build/root.patched/var/www/html# apply the product-local units# apply the product-local root overlayif [ -d overlay ]; then fab-apply-overlay overlay build/root.patched; fi# run the product-local configuration scripts$(call run-conf-scripts, conf.d)fab-chroot build/root.patched --script conf.d/main+ WPROOT=/var/www/wordpress+ NAME=wordpress+ USER=www-data+ DB_PREFIX=wp_++ mcookie+ DB_PASS=145707b3bb6946d70e4decd6edcdd7dc+ ADMIN_USER=admin+ ADMIN_PASS=turnkey+ ADMIN_MAIL=admin@example.com+ PHPINI=/etc/php/7.3/apache2/php.ini+ sed -i 's|^memory_limit.*|memory_limit = 128M|' /etc/php/7.3/apache2/php.inised: can't read /etc/php/7.3/apache2/php.ini: No such file or directorymake: *** [/usr/share/fab/product.mk:569: build/stamps/root.patched] Error 2

Searched for relevant file for PHPINI and found wordpress/conf.d/main where I changed "7.3" to "7.4".

Compilation completed and produce product.iso!!!

Testing it I have found there isno request for a WordPress password during install. I do have a password and its encrypted form so modified in adminer and could then log in to WordPress.

Looking at plugins, there is no TinyMCE, just a replacement for it called "Advanced Editor Tools (previously TinyMCE Advanced)". Installed in WP and works.

At the end of installation there is minor confusion over the unmount/eject commands - just a detail for tidying up.

Once the vital absence of WP password is fixed, this looks good to go.

Hope all that helps. Almost gave up a few time but in the end it was a bit of fun!

Ian