kiss-community / grepo Goto Github PK

The rust package is currently placed in gcommunity as it has not successfully build. Make sure it can successfully compile and then move it into grepo/extra

Trying to install GKISS Linux, getting this error when trying to rebuild all packages

Sway compiles and works fine from the main repository, can we remove sway, wlroots and pcre2 from the nvidia directory?
EDIT: If so, do not forget to replace pcre with pcre2 in extra

It would be nice to update the repository and add the nvidia-open package 😃
(sway with native wlroots works for me without artifacts)

• Firefox
• Firefox-esr
• LLVM
• Rust

I'm using GKISS with zen-kernel. I built it without any graphics support except for my intel integrated graphics, because I plan on installing the proprietary nvidia driver later.

I put the kernel in the ESP and followed the KISS efibootmgr steps (zen kernel is compiled with efistub support). Boot entry shows up in my BIOS (it did not before when I placed the kernel outside of ESP, so clearly the BIOS is checking that it's valid). When I select it, the screen is black and never changes.

Here is my kernel .config:

zen-dotconfig.txt

Anyway I heard this can be due to the nvidia drivers being required, so, in the chroot, I tried to install nvidia, resulting in an xorg-server error, so then I tried to install xorg-server, resulting in kiss failing to build libepoxy:

-> libepoxy Building package (6/11)
-> libepoxy Extracting sources
-> libepoxy Starting build
The Meson build system
Version: 0.63.0
Source dir: /home/ld/.cache/kiss/proc/6625/build/libepoxy
Build dir: /home/ld/.cache/kiss/proc/6625/build/libepoxy/output
Build type: native build
Project name: libepoxy
Project version: 1.5.10
C compiler for the host machine: cc (gcc 12.1.0 "cc (GCC) 12.1.0")
C linker for the host machine: cc ld.bfd 2.38
Host machine cpu family: x86_64
Host machine cpu: x86_64
Has header "KHR/khrplatform.h" : YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wmissing-declarations: YES
Compiler for C supports arguments -Wformat=2: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wnested-externs: YES
Compiler for C supports arguments -Wbad-function-cast: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Wdeclaration-after-statement: YES
Compiler for C supports arguments -Wunused: YES
Compiler for C supports arguments -Wuninitialized: YES
Compiler for C supports arguments -Wshadow: YES
Compiler for C supports arguments -Wmissing-noreturn: YES
Compiler for C supports arguments -Wmissing-format-attribute: YES
Compiler for C supports arguments -Wredundant-decls: YES
Compiler for C supports arguments -Wlogical-op: YES
Compiler for C supports arguments -Werror=implicit: YES
Compiler for C supports arguments -Werror=nonnull: YES
Compiler for C supports arguments -Werror=init-self: YES
Compiler for C supports arguments -Werror=main: YES
Compiler for C supports arguments -Werror=missing-braces: YES
Compiler for C supports arguments -Werror=sequence-point: YES
Compiler for C supports arguments -Werror=return-type: YES
Compiler for C supports arguments -Werror=trigraphs: YES
Compiler for C supports arguments -Werror=array-bounds: YES
Compiler for C supports arguments -Werror=write-strings: YES
Compiler for C supports arguments -Werror=address: YES
Compiler for C supports arguments -Werror=int-to-pointer-cast: YES
Compiler for C supports arguments -Werror=pointer-to-int-cast: YES
Compiler for C supports arguments -fno-strict-aliasing: YES
Compiler for C supports arguments -Wno-int-conversion: YES
Library dl found: YES
Found pkg-config: /usr/bin/pkg-config (1.8.0)
Run-time dependency gl found: NO (tried pkgconfig and system)
Run-time dependency egl found: YES 1.5
Run-time dependency x11 found: YES 1.8.1
Run-time dependency glesv2 found: YES 3.2
Run-time dependency glesv1_cm found: YES 1.0
Program src/gen_dispatch.py found: YES (/home/ld/.cache/kiss/proc/6625/build/libepoxy/src/gen_dispatch.py)
Configuring config.h using configuration
Compiler for C supports link arguments -Wl,-Bsymbolic-functions: YES
Compiler for C supports link arguments -Wl,-z,relro: YES
Library dl found: YES
Checking for function "dlvsym" with dependency -ldl: YES
Build targets in project: 26

libepoxy 1.5.10

  User defined options
    mandir    : /usr/share/man
    prefix    : /usr
    sysconfdir: /etc
    x11       : true

Found ninja-1.9 at /usr/bin/ninja
ninja: entering directory 'output'
[1/55] Generating src/glx_generated_dispatch.c with a custom command
[2/55] Generating src/egl_generated_dispatch.c with a custom command
[3/55] Generating src/gl_generated_dispatch.c with a custom command
[4/55] Generating include/epoxy/glx_generated.h with a custom command
[5/55] Generating include/epoxy/gl_generated.h with a custom command
[6/55] Generating include/epoxy/egl_generated.h with a custom command
[7/55] Compiling C object test/glx_gles2.p/dlwrap.c.o
[8/55] Compiling C object test/glx_gles2.p/glx_gles2.c.o
[9/55] Compiling C object test/glx_alias_prefer_same_name.p/dlwrap.c.o
[10/55] Compiling C object test/glx_alias_prefer_same_name.p/glx_alias_prefer_same_name.c.o
[11/55] Compiling C object test/glx_shared_znow.p/glx_static.c.o
[12/55] Compiling C object test/glx_has_extension_nocontext.p/glx_has_extension_nocontext.c.o
[13/55] Compiling C object test/glx_glxgetprocaddress_nocontext.p/glx_glxgetprocaddress_nocontext.c.o
[14/55] Compiling C object test/glx_public_api_core.p/glx_public_api_core.c.o
[15/55] Compiling C object test/glx_public_api.p/glx_public_api.c.o
[16/55] Compiling C object test/glx_beginend.p/glx_beginend.c.o
[17/55] Compiling C object test/libglx_common.a.p/glx_common.c.o
[18/55] Compiling C object test/egl_gl.p/egl_gl.c.o
[19/55] Compiling C object test/egl_gles2_without_glx.p/egl_without_glx.c.o
[20/55] Compiling C object src/libepoxy.so.0.0.0.p/meson-generated_.._gl_generated_dispatch.c.o
[21/55] Compiling C object test/egl_gles1_without_glx.p/egl_without_glx.c.o
[22/55] Compiling C object test/egl_epoxy_api.p/egl_epoxy_api.c.o
[23/55] Compiling C object test/egl_has_extension_nocontext.p/egl_has_extension_nocontext.c.o
[24/55] Compiling C object test/libegl_common.a.p/egl_common.c.o
[25/55] Compiling C object test/gl_version.p/gl_version.c.o
[26/55] Compiling C object 'test/khronos typedefs.p/khronos_typedefs_nonepoxy.c.o'
[27/55] Compiling C object 'test/khronos typedefs.p/khronos_typedefs.c.o'
[28/55] Compiling C object 'test/misc defines.p/miscdefines.c.o'
[29/55] Compiling C object 'test/header guards.p/headerguards.c.o'
[30/55] Compiling C object src/libepoxy.so.0.0.0.p/dispatch_glx.c.o
[31/55] Compiling C object src/libepoxy.so.0.0.0.p/dispatch_egl.c.o
[32/55] Compiling C object src/libepoxy.so.0.0.0.p/dispatch_common.c.o
[33/55] Compiling C object src/libepoxy.so.0.0.0.p/meson-generated_.._glx_generated_dispatch.c.o
[34/55] Linking static target test/libglx_common.a
[35/55] Linking static target test/libegl_common.a
[36/55] Compiling C object src/libepoxy.so.0.0.0.p/meson-generated_.._egl_generated_dispatch.c.o
[37/55] Linking target src/libepoxy.so.0.0.0
[38/55] Generating symbol file src/libepoxy.so.0.0.0.p/libepoxy.so.0.0.0.symbols
[39/55] Linking target test/glx_gles2
[40/55] Linking target test/glx_alias_prefer_same_name
[41/55] Linking target test/glx_shared_znow
[42/55] Linking target test/glx_has_extension_nocontext
[43/55] Linking target test/glx_glxgetprocaddress_nocontext
[44/55] Linking target test/glx_public_api_core
[45/55] Linking target test/glx_public_api
[46/55] Linking target test/glx_beginend
[47/55] Linking target test/egl_gl
[48/55] Linking target test/egl_gles2_without_glx
[49/55] Linking target test/egl_gles1_without_glx
[50/55] Linking target test/egl_epoxy_api
[51/55] Linking target test/egl_has_extension_nocontext
[52/55] Linking target test/gl_version
[53/55] Linking target 'test/khronos typedefs'
[54/55] Linking target 'test/misc defines'
[55/55] Linking target 'test/header guards'
ninja: job failed: cc  -o test/glx_beginend test/glx_beginend.p/glx_beginend.c.o -Wl,--as-needed -Wl,--no-undefined -march=native -pipe -Ofast '-Wl,-rpath,$ORIGIN/../src' -Wl,-rpath-link,/home/ld/.cache/kiss/proc/6625/build/libepoxy/output/src -Wl,--start-group test/libglx_common.a src/libepoxy.so.0.0.0 -ldl /usr/lib/libX11.so -Wl,--end-group
/usr/bin/ld: test/glx_beginend.p/glx_beginend.c.o: in function `test_without_epoxy':
/home/ld/.cache/kiss/proc/6625/build/libepoxy/output/../test/glx_beginend.c:69: undefined reference to `glBegin'
/usr/bin/ld: /home/ld/.cache/kiss/proc/6625/build/libepoxy/output/../test/glx_beginend.c:84: undefined reference to `glEnd'
collect2: error: ld returned 1 exit status
ninja: subcommand failed
-> libepoxy Build failed
-> libepoxy Log stored to /home/ld/.cache/kiss/logs/2022-07-14/libepoxy-2022-07-14-06:46-6625
Terminated

Here is my KISS_PATH:

• /home/ld/.local/repo
• /home/ld/.local/repos/grepo/nvidia
• /home/ld/.local/repos/kiss-xorg/xorg
• /home/ld/.local/repos/kiss-xorg/community
• /home/ld/.local/repos/kiss-xorg/extra
• /home/ld/.local/repos/community/community
• /home/ld/.local/repos/grepo/core
• /home/ld/.local/repos/grepo/extra

Links:

• grepo is this
• kiss-xorg
• community
• official KISS repo is not included

.profile:

export KISS_PATH="/home/ld/.local/repo"
export KISS_PATH="$KISS_PATH:/home/ld/.local/repos/grepo/nvidia"
export KISS_PATH="$KISS_PATH:/home/ld/.local/repos/kiss-xorg/xorg"
export KISS_PATH="$KISS_PATH:/home/ld/.local/repos/kiss-xorg/community"
export KISS_PATH="$KISS_PATH:/home/ld/.local/repos/kiss-xorg/extra"
export KISS_PATH="$KISS_PATH:/home/ld/.local/repos/community/community"
export KISS_PATH="$KISS_PATH:/home/ld/.local/repos/grepo/core"
export KISS_PATH="$KISS_PATH:/home/ld/.local/repos/grepo/extra"

export CFLAGS="-march=native -pipe -Ofast"
export CXXFLAGS="$CFLAGS"
export MAKEFLAGS="-j12"

export EDITOR=nano
export LANG=en_US.UTF-8

Here's some more system information:

• efibootmgr -v

  BootCurrent: 0003
  Timeout: 1 seconds
  BootOrder: 0001,0000,0003
  Boot0000* Windows Boot Manager	HD(1,GPT,86b6226f-0f08-4d1c-8067-c56b00c1d072,0x800,0x82000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
        dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 08 00 00 00 00 00 6f 22 b6 86 08 0f 1c 4d 80 67 c5 6b 00 c1 d0 72 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 49 00 43 00 52 00 4f 00 53 00 4f 00 46 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 46 00 57 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
      data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 00 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
  Boot0001* KISS	HD(1,GPT,86b6226f-0f08-4d1c-8067-c56b00c1d072,0x800,0x82000)/File(\VMLINUZ-5.18.11-ZEN)72006f006f0074003d00500041005200540055005500490044003d00620065006100630062006400320038002d0034006300610066002d0034006100650065002d0061006400640038002d00360061003800370035003100320064006600390038003200200072007700
        dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 08 00 00 00 00 00 6f 22 b6 86 08 0f 1c 4d 80 67 c5 6b 00 c1 d0 72 02 02 / 04 04 2e 00 5c 00 56 00 4d 00 4c 00 49 00 4e 00 55 00 5a 00 2d 00 35 00 2e 00 31 00 38 00 2e 00 31 00 31 00 2d 00 5a 00 45 00 4e 00 00 00 / 7f ff 04 00
      data: 72 00 6f 00 6f 00 74 00 3d 00 50 00 41 00 52 00 54 00 55 00 55 00 49 00 44 00 3d 00 62 00 65 00 61 00 63 00 62 00 64 00 32 00 38 00 2d 00 34 00 63 00 61 00 66 00 2d 00 34 00 61 00 65 00 65 00 2d 00 61 00 64 00 64 00 38 00 2d 00 36 00 61 00 38 00 37 00 35 00 31 00 32 00 64 00 66 00 39 00 38 00 32 00 20 00 72 00 77 00
  Boot0003* UEFI:  USB, Partition 1	PciRoot(0x0)/Pci(0x14,0x0)/USB(18,0)/HD(1,GPT,2c7065ea-20a0-426e-8856-fa14e277cfe7,0x800,0x3b92cb)0000424f
        dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 12 00 / 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 cb 92 3b 00 00 00 00 00 ea 65 70 2c a0 20 6e 42 88 56 fa 14 e2 77 cf e7 02 02 / 7f ff 04 00
      data: 00 00 42 4f
  

• /etc/fstab

  # Static information about the filesystems.
  # See fstab(5) for details.
  
  # <file system> <dir> <type> <options> <dump> <pass>
  
  tmpfs /tmp tmpfs defaults,nosuid,nodev 0 0
  /dev/nvme0n1p1 /boot vfat defaults 0 0
  

• kernel command line is root=PARTUUID=beacbd28-4caf-4aee-add8-6a87512df982 rw, blkid is:

  /dev/sda2: UUID="12354155-d7d3-44d4-9c78-879734a705d4" TYPE="ext4"
  /dev/sda1: LABEL="ALPINE-STD" UUID="98DB-4887" TYPE="vfat"
  /dev/nvme0n1p7: LABEL="RESTORE" UUID="2E644DE1644DAD01" TYPE="ntfs"
  /dev/nvme0n1p6: LABEL="RECOVERY" UUID="AE742EB7742E8267" TYPE="ntfs"
  /dev/nvme0n1p5: UUID="beacbd28-4caf-4aee-add8-6a87512df982" TYPE="ext4"
  /dev/nvme0n1p4: LABEL="TRANSFER" UUID="E350-EFE0" TYPE="exfat"
  /dev/nvme0n1p3: LABEL="OS" UUID="01D896A8C78B58E0" TYPE="ntfs"
  /dev/nvme0n1p1: LABEL="SYSTEM" UUID="E4A8-6CBD" TYPE="vfat"
  /dev/loop/0: TYPE="squashfs"
  /dev/loop0: TYPE="squashfs"
  

• ESP contains:

  EFI
  System Volume Information
  System.map-5.18.11-zen
  vmlinuz-5.18.11-zen
  

  (this is a Windows 10 dual boot)

• lspci outside chroot

  00:00.0 Host bridge: Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
  00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
  00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
  00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
  00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
  00:15.0 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0
  00:15.1 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH Serial IO I2C Controller #1
  00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
  00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #17 (rev f0)
  00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
  00:1d.6 PCI bridge: Intel Corporation Device 06b6 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Comet Lake LPC Controller
  00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller
  01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
  01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
  01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
  02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
  03:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
  03:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
  03:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
  04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06)
  3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06)
  3b:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01)
  3c:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  

Let me know if I left anything out.

This may very well be a kernel issue, I'm not 100% sure.

Known occurances:

* ldd

"fails" is in quotes in the title because it does boot, you're just dropped into a shell as root.

=> Remounting rootfs as read-only...
=> Checking filesystems...
fsck: fsck.vfat: No such file or directory
=> Mounting rootfs as read-write...
=> Mounting all local filesystems...
mount: mounting /tmp failed: invalid argument
=> Init system encountered an error, starting emergency shell.
=> When read, type 'exit' to continue the boot.

Since it might be relevant, here's my fstab:

# Static information about the filesystems.
# See fstab(5) for details.

# <file system>					<dir>		<type>	<options>		<dump>	<pass>

# btrfs pool, /dev/nvme0n1p3
UUID=d864fc3d-631c-45ee-9644-d758258eedc3	/mnt/btrfs	btrfs	rw,relatime,compress=zstd:3,ssd,space_cache		0	0

# root, /dev/nvme0n1p3
UUID=d864fc3d-631c-45ee-9644-d758258eedc3	/		btrfs	rw,relatime,compress=zstd:3,ssd,space_cache,subvol=root	0	0

# home, /dev/nvme0n1p3
UUID=d864fc3d-631c-45ee-9644-d758258eedc3	/home		btrfs	rw,relatime,compress=zstd:3,ssd,space_cache,subvol=home	0	0

# esp, /dev/nvme0n1p1
UUID=8CB2-6A4F				 	/efi		vfat	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0	2

# /tmp, tmpfs
tmpfs						/tmp		tmpfs	defaults,nosuid,nodev	0	0

# swap, /dev/nvme0n1p2
UUID=f072bb9c-a7ef-4bac-9b6a-64e837db9a01	none		swap	defaults		0	0

When I try to build the wlroots package (from nvidia), I get an error, please help

ERROR wlroots No local file 'patches/hwdb.patch'

What I meant by symlinks files is the following: https://github.com/jedavies-dev/kiss-aarch64/tree/master/repo/musl

Only the unchanged files are symbolically linked. jedavies-dev would update their symlinks to point to ../../repo/... for example. There's no need to symlink each package in other words. The user can keep the official repositories wherever they like as you include the submodule only for the packages you have partially modified.

Does this make sense? It saves you symlinking everything.

I get an error when I try to build wlroots:

ninja: job failed: /usr/bin/meson --internal exe --capture backend/drm/pnpids.h --feed /root/.cache/kiss/proc/890479/build/wlroots/pnp.ids -- /root/.cache/kiss/proc/890479/build/wlroots/backend/drm/gen_pnpids.sh
Traceback (most recent call last):
  File "/usr/bin/meson", line 33, in <module>
    sys.exit(load_entry_point('meson==0.62.2', 'console_scripts', 'meson')())
  File "/usr/lib/python3.10/site-packages/mesonbuild/mesonmain.py", line 271, in main
    return run(sys.argv[1:], launcher)
  File "/usr/lib/python3.10/site-packages/mesonbuild/mesonmain.py", line 260, in run
    return run_script_command(args[1], args[2:])
  File "/usr/lib/python3.10/site-packages/mesonbuild/mesonmain.py", line 203, in run_script_command
    return module.run(script_args)
  File "/usr/lib/python3.10/site-packages/mesonbuild/scripts/meson_exe.py", line 122, in run
    return run_exe(exe)
  File "/usr/lib/python3.10/site-packages/mesonbuild/scripts/meson_exe.py", line 66, in run_exe
    p = subprocess.Popen(cmd_args, env=child_env, cwd=exe.workdir,
  File "/usr/lib/python3.10/subprocess.py", line 969, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.10/subprocess.py", line 1733, in _execute_child
    self._posix_spawn(args, executable, env, restore_signals,
  File "/usr/lib/python3.10/subprocess.py", line 1678, in _posix_spawn
    self.pid = os.posix_spawn(executable, args, env, **kwargs)
PermissionError: [Errno 13] Permission denied: '/root/.cache/kiss/proc/890479/build/wlroots/backend/drm/gen_pnpids.sh'
ninja: subcommand failed

A temporary solution: add chmod +x backend/drm/gen_pnpids.sh to the build file (before make)

~ $ doas ls
[   49.825687] traps: doas[161] trap divide error (...) error:0 in libc.so.6[...+166000]
Floating point exception

instruction pointer/stack pointer/base pointer for libc omitted as they change on each invocation-- I think only the offset should be relevant. (that being said, I tried looking at the objdump and at that position there is only a SIMD compare instruction, which can't even raise an exception like that as far as i know.... maybe I don't know what I'm doing. that seems plausible.)

oddly, I remember this working fine when I first installed it, but then the error eventually just.. started happening. If this is impossible to reproduce I wouldn't be surprised, though I'm also really curious why doas would be doing any sort of floating point math in the first place.

if there's anything else I can check on my end, let me know.

EDIT: also, sometimes the "traps:" line doesn't show and it just says "Floating point exception".

tmp folder does not have correct rw permissions set for all users
currently only root user can write to the tmp folder.

permissions need to be :

chmod 1777 /tmp

drwxrwxrwt 21 root root 12288 Apr 28 16:18 /tmp

Firefox from the kiss repos currently fails, that shouldn't be the case...

The section of the log from when the build failed:

[4107/48830] CXX obj/third_party/vulkan-deps/glslang/src/glslang_lib_sources/PpScanner.o
ninja: job failed: python3 ../../v8/third_party/inspector_protocol/code_generator.py --jinja_dir ../../third_party/ --output_base gen/v8/src/inspector --config ../../v8/src/inspector/inspector_protocol_config.json --inspector_protocol_dir //v8//third_party/inspector_protocol
Traceback (most recent call last):
  File "/home/david/.cache/kiss/proc/6273/build/chromium/out/Release/../../v8/third_party/inspector_protocol/code_generator.py", line 702, in <module>
    main()
  File "/home/david/.cache/kiss/proc/6273/build/chromium/out/Release/../../v8/third_party/inspector_protocol/code_generator.py", line 584, in main
    jinja_env = initialize_jinja_env(jinja_dir, config.protocol.output, config)
  File "/home/david/.cache/kiss/proc/6273/build/chromium/out/Release/../../v8/third_party/inspector_protocol/code_generator.py", line 190, in initialize_jinja_env
    import jinja2
  File "/home/david/.cache/kiss/proc/6273/build/chromium/third_party/jinja2/__init__.py", line 33, in <module>
    from jinja2.environment import Environment, Template
  File "/home/david/.cache/kiss/proc/6273/build/chromium/third_party/jinja2/environment.py", line 16, in <module>
    from jinja2.defaults import BLOCK_START_STRING, \
  File "/home/david/.cache/kiss/proc/6273/build/chromium/third_party/jinja2/defaults.py", line 32, in <module>
    from jinja2.tests import TESTS as DEFAULT_TESTS
  File "/home/david/.cache/kiss/proc/6273/build/chromium/third_party/jinja2/tests.py", line 13, in <module>
    from collections import Mapping
ImportError: cannot import name 'Mapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py)
ninja: subcommand failed
-> chromium Build failed
-> chromium Log stored to /home/david/.cache/kiss/logs/2021-10-16/chromium-2021-10-16-09:22-6273
Terminated

Looking it up, it seems that Python 3.10 changed where Mapping lives from collections to collections.abc.
I'm unsure if it would be simpler to bundle in an older version of python or to look for and patch all such errors in chromium (or if there's some newer version of chromium that doesn't have the issue..? Yet I'm pretty sure the one I was trying to build was last updated today...)

When I run sway with sway --unsupported-gpu an error occurs:

00:00:00.000 [ERROR] [sway/main.c:62] !!! Proprietary Nvidia drivers are in use !!!
00:00:00.004 [ERROR] [wlr] [backend/backend.c:217] Found 0 GPUs, cannot create backend
00:00:00.004 [ERROR] [wlr] [backend/backend.c:386] Failed to open any DRM device
00:00:00.006 [ERROR] [sway/server.c:57] Unable to create backend

Can you please tell me what I missed? ALL the commands I used for install here.

While building glibc going through the fresh install process for GKISS, I am getting the following error (abusing discord as a CDN here, additionally sorry for screenshot of text but I am not even into GUI yet):

https://media.discordapp.net/attachments/313639629146423296/885299296369532928/20210908_180114.jpg

Any workaround? I've made sure I am using GNU Awk and GNU Grep, so I don't know what it could be if it is indeed user error.

I know, I too often create issues here :)
but it would be nice to update rootfs, the last update was about half a year ago

Is this possible? Currently, I'm running into 2 issues:

1

Xorg can't find the nvidia module:
https://termbin.com/hr5q

2

libepoxy cannot be compiled with mesa compiled using libglvnd (for some reason).

I'm not sure if I'm doing anything wrong - or if there are some modifications which need to be done for Xorg. Any help would be greatly appreciated! Thanks in advance.

When I run kiss u I get:

-> Updating repositories 
-> /root/kiss/grepo  
Already up to date.
Submodule path 'kiss-repo': checked out '37ff4d8a25b7be52d25cd44abe9fe87cbab44a42'
fatal: HEAD does not point to a branch
-> /root/kiss/grepo/wayland  
-> /root/kiss/community  
Already up to date.
-> Checking for new package versions 
gcc 12.1.0-1 => 12.2.0-1
-> Packages to update (1): gcc 
-> Continue?: Press Enter to continue or Ctrl+C to abort 
█

What does fatal: HEAD does not point to a branch mean?

Currently the only graphical browser that is packaged is firefox. KISS Linux had issues with compiling ungoogled-chromium, however it should be possible (with a bit of work) on glibc.

Some early attempts at builds have failed, however it seems progress is slowly being made.

The "ungoogled-chromium-exp" build by aosync https://github.com/aosync/kiss-aosync is used as a base to develop upon. Once compiling ungoogled chromium succeeds it's dependencies should be moved into grepo.

Note also that the external yasm dependency should be removed and instead use an internal one to stay consistent with the firefox build in the KISS Linux repos.

Hello, is there any way to "enable" OpenGL with NVIDIA in this repository (to run games, etc.)? For example when I try to run gzdoom, I get this:

OS: KISS Linux, Linux 5.18.9 on x86_64
M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
 adding ./gzdoom.pk3, 668 lumps
 adding ./game_support.pk3, 2514 lumps
 adding ./DOOM.WAD, 2306 lumps
 adding ./game_widescreen_gfx.pk3, 214 lumps
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
  Opened device ALSA Default
[ALSOFT] (WW) pthread_setschedparam failed: Operation not permitted (1)
[ALSOFT] (WW) D-Bus not supported
  EFX enabled
ID out of range. Using default device.
I_Init: Setting up machine state.
CPU speed: 2904 MHz
CPU Vendor ID: GenuineIntel
  Name: Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz
  Family 6, Model 158, Stepping 10
  Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 F16C FMA3 BMI1 BMI2 HyperThreading
V_Init: allocate screen.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 124.54 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
Using video driver wayland
libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)


Could not create OpenGL window:
Could not initialize EGL

starting with kiss version 5.5.21, I am unable to remove packages, even when setting KISS_FORCE=1. Posting here in the GKISS repo because the circular dependency seems to always involve glibc.

$ kiss remove weechat
ERROR Circular dependency detected perl <> openssl

$ kiss depends openssl
perl make

$ kiss depends perl
bzip2
glibc
zlib

$ kiss depends glibc
gawk make
linux-headers make
python make

$ kiss depends python
bzip2
expat
libffi
ncurses
openssl
readline
sqlite
xz
zlib

https://gitlab.freedesktop.org/glvnd/libglvnd/-/archive/v1.4.0/libglvnd-v1.4.0.tar.gz
And if I may ask - why sway version is upstream and not 1.7?

i installed kiss linux on a partition on my disk, i did everything the guide said but when i tried to boot it up it just didnt
my screen said this:
"Loading linux 6.4.9"

my caps lock light went crazy and no matter how much time i waited it just didnt boot up

pd: i also tried safe mode

It was broken

At the moment the package says 2.31, however 2.30 is actually used. However simply installing a new glibc causes most builds to fail.

I've got no clue how to solve this to be honest. Right now I'm thinking to rebuild everything from scratch, however this would be an issue to anyone on an existing system.

For now gkiss will keep on using glibc 2.30...

I have:

grepo/bin
grepo/core
grepo/extra
grepo/wayland
community/community
grepo/repo/core
grepo/repo/extra
grepo/repo/wayland
kiss-xorg/xorg

libepoxy is not available in any of these, but grepo/bin/firefox depends on libepoxy. is there a recommended place to get it?

After running kiss u and it updating OpenSSL, I find that now I no longer have libssl.so.1.1. I have no direct need for this, but the issue is that git-remote-https and curl both seem to depend upon it. If I build OpenSSL 1.1 myself and use that to rebuild git, it seems to still default to depending upon 1.1.

What is the intended way to upgrade things to the new OpenSSL 3.0 version? At the moment it's tempting to just throw an OpenSSL 1.1 package together and use that, but that does not seem like the intended path.

(Maybe this should be something I ask about upstream in kisslinux/repo instead-- if so, let me know)

Hello, i started using gkiss
But when i run some apps i get this error and app wont run:
/usr/lib/libstdc++.so.6: no version information available
I tried firefox (the tarball on the official website) and tried qutebrowser that i installed thru pip, and both gave the same error. This does not occur on my other gentoo installation.
How can i fix this?

Input still works, I can login and reboot the system. Switching TTYs does not change anything, it just simply keeps saying "Loading Linux 5.15.4".

I tried several GRUB parameters, including nomodeset, nouveau.nomodeset=0, and as expected, none of them worked. All nouveau kernel options are disabled:

/linux-5.15.4 # cat .config | grep NOUVEAU
# CONFIG_DRM_NOUVEAU is not set

It seems to be working whenever I boot through my old Gentoo kernel (including my old initramfs), but whenever I boot with my new kernel it just simply does not do anything. Just vanilla kernel, no patches, and no initramfs.

Further information:

• GPU: GM 204 (GTX 970)
• Kernel version 5.15.4
• Beforementioned gentoo kernel version: 5.10.4

Any help would be appreciated, thanks in advance!

I'm unsure if this is an issue on normal KISS as well.

First, lld:

then mold:

binutils ld seems to just hang, consuming more and more memory.

The same segfault/hang (respectively) occurs when running cargo install alacritty as well, so it makes me think there's some issue with the linkers as they are on the system rather than just pcre being bad.

-> nvidia Starting build
Creating directory NVIDIA-Linux-x86_64-510.39.01-no-compat32
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 510.39.01.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
xorg-server 21.1.3-1
wayland 1.20.0-1
make[1]: *** /lib/modules/5.4.0-91-generic/build: No such file or directory.  Stop.
make: *** [Makefile:82: modules] Error 2

Seems to be something about kernel modules. Fresh install with kiss-xorg.

KISS_PATH=/repo/local:/repo/grepo/bin:/repo/grepo/core:/repo/grepo/extra:/repo/grepo/nvidia:/repo/kiss-xorg/community:/repo/kiss-xorg/extra:/repo/kiss-xorg/xorg:/repo/grepo/kiss-repo/core:/repo/grepo/kiss-repo/extra:/repo/grepo/kiss-repo/testing:/repo/grepo/kiss-repo/wayland:/repo/community/community

All binary packages in the official KISS rrpos should be ported over to GKISS.

Hey, may I know the difference between gkiss and kiss?

This can be easily fixed by copying the upstream ccache in kiss-repo, which just passes in -DREDIS_STORAGE_BACKEND=OFF.

EDIT: Although I doubt it's necessary, here's the log the build gives:

-- Checking for module 'hiredis>=0.13.3'
--   Package 'hiredis', required by 'virtual:world', not found
CMake Error at /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  please install libhiredis or use -DHIREDIS_FROM_INTERNET=ON or disable with
  -DREDIS_STORAGE_BACKEND=OFF (missing: HIREDIS_INCLUDE_DIR HIREDIS_LIBRARY)
  (Required is at least version "0.13.3")
Call Stack (most recent call first):
  /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  cmake/Findhiredis.cmake:64 (find_package_handle_standard_args)
  CMakeLists.txt:105 (find_package)

curl will segfault when a download reaches 100% if /etc/nsswitch.conf contains "hosts: files dns" AND the -L flag is set.
kisslinux/repo#274 for reference

libc_cv_include_x86_isa_level=no
This disables “x86 ISA needed” property in Glibc libraries. Use it if you are building Glibc with -march option in CFLAGS, to workaround an issue in Glibc-2.33 breaking it.

https://www.linuxfromscratch.org/~thomas/multilib/chapter05/glibc.html

It would be nice to remove the atk dependency from the firefox[bin] package, since it has been removed from the repository