Puppy Linux Discussion Forum

KLV-Hyprland-CE-3.9 stable
Added all the latest improvements

I compiled the latest version (hyprland-0.35.0_1.x86_64.xbps), I will try what happened. The compilation was successful. compilation was done differently than the previous version

• hyprland / hyprland_nvidia
• xdg-desktop-portal-hyprland
• hyprland-protocols
• Other dependency packages

Hi all

I have NOT installed any OSes in the last 4 years. I run only with those which allow persistence from their ISO/IMGs. Disk space for me is, now, reduced to data-only and persistence...NOT OSes on any given PCs. Same for MS.

Is there a script/GUI/method, documented, on how to turn the output of a build (seen below) into a bootable ISO/IMG?

This is needed in those cases where an ISO file is not presented for KLs.

version does not start (hyprland-0.35.0_1.x86_64.xbps) .something was done to her guys are overdoing it

error

Hyprland: /usr/lib/libstdc++.so.6: version 'GLIBCXX_3.4.32' not found ( required by Hyprland )
Hyprland: /usr/lib/libstdc++.so.6: version 'GLIBCXX_3.4.31' not found ( required by Hyprland )

the test shows that everything is in place
strings /usr/lib/libstdc++.so.6 | grep GLIBCXX

──[ root@void-live ] [ 04:36:53 ]
├── ~
└> strings /usr/lib/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_3.4.20
GLIBCXX_3.4.21
GLIBCXX_3.4.22
GLIBCXX_3.4.23
GLIBCXX_3.4.24
GLIBCXX_3.4.25
GLIBCXX_3.4.26
GLIBCXX_3.4.27
GLIBCXX_3.4.28
GLIBCXX_3.4.29
GLIBCXX_3.4.30
GLIBCXX_3.4.31
GLIBCXX_3.4.32
GLIBCXX_TUNABLES
GLIBCXX_DEBUG_MESSAGE_LENGTH

Sofiya wrote: Mon Feb 12, 2024 7:47 pm

... * hyprland / hyprland_nvidia ...

If one of your ISO surfaces with this, I have 2 test PCs with nvidia cards that I can test for resulting boots to desktop.

hyprland-0.35.0_1.x86_64.xbps is compiled with libgcc-13.2.1-3, so it won’t work for us because we use libgcc-12.2.0_3. We’ll wait for the update ( libgcc-12.2.0_3 )

KLV-Hyprland-CE-4.0 stable - Build script updated for February 15.02.2024
Amendments made
added (xdg-desktop-portal-hyprland).
added a modified program unetbootin-hyprland-70.2_2.x86_64.xbps for writing iso to a flash drive. requires "syslinux" dependency
Changes have been made for "Gparted".
other fixes.

I thought for a long time and could not understand what was wrong. I replaced the mirror and the build comes with libgcc-13 I'll try to build KLV with "hyprland-0.35.0_1.x86_64.xbps"

Ran the KLbuild_Void_hyprland_swayBASE.sh again.

Questions

• Where is the utility that creates the KL ISO file?

• OR, is there a parm that I should have used when invoking the sh utility in the beginning?

Conclusion

Refer to /mnt/sda2/makeKLV-hypr4/grub_config.txt for
copy of this information plus blkid info.
Note that you can remove w_changes=RAM2 if you don't want
save session on demand mode.
# ls *.iso
ls: cannot access '*.iso': No such file or directory
# ls 
00zdrv_vanilladpup_10.0.30.sfs
01fdrv_vanilladpup_10.0.30.sfs
07firstrib_rootfs
12KL_gtkdialogGTK3filemnt64.sfs
build_firstrib_rootfs.sh
f_00_Void_wayland_hyprland_no-kernelBASE.plug
grub_config.txt
initrd.gz
KLbuild_Void_hyprland_swayBASE.sh
KLbuild_Void_hyprland_swayBASE.sh.FALSE.gz
modify_initrd_gz.sh
mount_chroot.sh
mount_chroot_umount.sh
umount_chroot.sh
vmlinuz
wd_grubconfig

@Clarity I think the script makes the distro with the rootfs still uncompressed and no ISO. What I do is use an F96-CE_4 to run the build scripts so I have access to all of the tools needed to assemble a boot-able ISO. Then I squash the rootfs directory (filesystem) using PackIt. I use xz compression 1M block size.

Then move the uncompressed rootfs you just made the SFS from to a safe place outside of the distro's directory.
Move outside of the distro directory and then in a terminal ->

mkisofs -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -D -l -R -v -V "KLV-Hyperland" -no-emul-boot -boot-load-size 4 -boot-info-table -o "KLV-Hyperland-CE-3.9.iso"  KLV-Hyperland-CE-3.9

followed by ->

isohybrid KLV-Hyperland-CE-3.9.iso

Thanks @rockedge for guidance.

This helps to know the steps to an ISO file for testing making it easy to gather any info on either the KL's use or reporting to development if problems exist in test operations. This make it easy for us users to help development with operational info important to their objective.

YOur procedure suggest 3 or 4 additional terminal commands after the build script is run. (Can/should the commands be scripted and added to the build directory for ISO-IMG file generation?)

1. Test to see if packit is present

2. run packit command like this

   Code: Select all

   packit create squashfs 07firstrib_rootfs.xz --xz-block-size=1M 07firstrib_rootfs

3. run mkisofs command (I am not confident the following is correct command to use with 'packit' outcome)

   Code: Select all

   mkisofs -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -D -l -R -v -V "KLV-Hyperland" -no-emul-boot -boot-load-size 4 -boot-info-table -o "KLV-Hyperland-CE-3.9.iso"  KLV-Hyperland-CE-3.9

4. followed by

   Code: Select all

   isohybrid KLV-Hyperland-CE-3.9.iso

Is this correct?

@Clarity Once the PackIt creation of the rootfs is done, this SFS is added to the distro root. See example ->

Once your directory looks similar, Go up one level and run the make ISO commands

mkisofs -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -D -l -R -v -V "KLV-Hyperland" -no-emul-boot -boot-load-size 4 -boot-info-table -o "KLV-Hyperland-CE-3.9.iso"  KLV-Hyperland-CE-3.9

and followed by:

isohybrid KLV-Hyperland-CE-3.9.iso

@rockedge I think you want me to get rid of ALL files except the ones you show before making the ISO file. Correct? ... and Thansk in advance.

@Clarity Correct! Though the other files are some tools to work with the uncompressed rootfs, thouse are not needed in the ISO.

Only the files needed to be a boot-able distro in ISO form are shown.

Double check the /boot/grub/menu.lst, /boot/grub/grub.cfg and /boot/grub/loopback.cfg if the look alright. They should be.

The build will be assembled as shown below, before squashing the rootfs and streamlining for the ISO construction.

You're almost there!

@Clarity I thought this might be easier......I made an ISO of KLV-Hyprland-CE-4.1 for you to test!

KLV-Hyprland-CE-4.1.iso
SHA1-MD5.txt