February 2021 - Arch-general - lists.archlinux.org

Re: [arch-general] strip command of binutils 2.36 changes ownership in fakeroot 1.25.3
by Genes Lists 10 Feb '21

10 Feb '21

On 2/10/21 4:35 PM, Levente Polyak via arch-dev-public wrote: > Hi all, > Thanks for the update Levente. Separately, I also note that you briefly put 2.36.1 in testing but then pulled it. AM curious what your thinking was around that version as well (seems to be different issues [1]) thanks. gene [1] https://sourceware.org/pipermail/binutils/2021-February/115240.html

2 2

[arch-general] Mounted ext4 filesystem without journal
by Alexander Kapshuk 08 Feb '21

08 Feb '21

Most probably due to a buggy custom kernel, fsck on /dev/sda2, i.e the root partition, failed with a rootfs prompt and an invitation to run fsck on /dev/sda2 presented. On having done that and rebooted, when performing fsck on /dev/sda2, the system reported that: /dev/sda2 had not been cleanly unmounted 0.4% non-contiguous blocks mounting /dev/sda2 on real root EXT4-fs (sda2) mounted filesystem without journal Root device mounted successfully, but /sbin/init does not exist. The wiki article on fsck troubleshooting, https://wiki.archlinux.org/index.php/Fsck#Troubleshooting, suggests using tune2fs to write a new journal to /dev/sda2. But it doesn't seem to be available when in rootfs. Booting into the Arch Linux installation CD and mounting /dev/sda2 over /mnt reveals lost+found as the sole contents of the directory. As an experiment, mounting /dev/sda1 over /mnt confirms the presence of all the files there are on my boot partition. Any pointers on how to proceed with this would be much appreciated.

5 8

[arch-general] Arch Linux OVH end of support
by Óscar García Amor 08 Feb '21

08 Feb '21

Hi, Seems that Arch Linux will be unsupported in OVH [1] maybe a big warning should be added on the wiki [2], especially considering that the contract with OVH is usually signed for one year. Greetings. [1]: https://services.ovhcloud.com/optiext/optiextension.dll?ID=JbaJfV6QoXt4c_Kt… [2]: https://wiki.archlinux.org/index.php/Arch_Linux_on_a_VPS -- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me

4 5

[arch-general] Change how cross compilers are packaged
by Christer Solskogen 08 Feb '21

08 Feb '21

I've been using the aarch64 cross compiler packages for some time, lately I've also taken a look at how that PKGBUILD looks and how it relates to Cross-compiling tools package guidelines. The situation now is that aarch64-linux-gnu-glibc installs into a sysroot in /usr/aarch64-linux-gnu. Where also aarch64-linux-gnu-binutils installs some files into. This is bad because the sysroot is a directory thats supposed to be reserved for the target system. This is fine on bare-metal systems, but not for linux/mingw targets. What do you think of having /usr/sysroot/$target as sysroots instead for targets that are supposed to be configured that way? Only a small hand full of packages needs to be rewritten (aarch64, mingw-w64 and riscv64) - and I can fix that I (the package maintainers still need to review my changes, as I don't have git access) One other option would be to follow gcc's defaults, which is $prefix/$target/sys-root But before I do that, I'd like some comments if you think this is needed. I don't want to waste time :-) At the same time, I would remove some of the old/deprecated options for binutils, glibc and gcc that are present in the current PKGBUILDs. -- chs

1 0

[arch-general] nsd 4.3.5 broken
by Genes Lists 06 Feb '21

06 Feb '21

Good morning nsd package (4.3.5-1) in testing doesn't start for me. 4.3.4 works but 4.3.5 fails - lacks permission in the working directory. This is what log says: service: Changing to the requested working directory failed: Not a directory service: Failed at step CHDIR spawning /bin/kill: Not a directory service: Control process exited, code=exited, status=200/CHDIR The new service start file has: WorkingDirectory=~ I tried: WorkingDirectory=/etc/nsd but this still fails Thanks.

3 8

[arch-general] DKMS problem with the latest linux-ck kernel
by Randy DuCharme 06 Feb '21

06 Feb '21

Greetings, Seems the latest linux-ck kernel and DKMS don't play well together. The post-install goes something like this: :: Running post-transaction hooks... (1/4) Arming ConditionNeedsUpdate... (2/4) Updating module dependencies... (3/4) Install DKMS modules ==> dkms install --no-depmod -m openrazer-driver -v 2.9.0 -k 5.10.13-3-ck Error! Bad return status for module build on kernel: 5.10.13-3-ck (x86_64) Consult /var/lib/dkms/openrazer-driver/2.9.0/build/make.log for more information. ==> Warning, `dkms install --no-depmod -m openrazer-driver -v 2.9.0 -k 5.10.13-3-ck' returned 10 ==> dkms install --no-depmod -m nvidia -v 390.138 -k 5.10.13-3-ck Error! Bad return status for module build on kernel: 5.10.13-3-ck (x86_64) Consult /var/lib/dkms/nvidia/390.138/build/make.log for more information. ==> Warning, `dkms install --no-depmod -m nvidia -v 390.138 -k 5.10.13-3-ck' returned 10 ==> depmod 5.10.13-3-ck (4/4) Updating linux initcpios... ==> Building image from preset: /etc/mkinitcpio.d/linux-ck.preset: 'default' -> -k /boot/vmlinuz-linux-ck -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-ck.img ==> Starting build: 5.10.13-3-ck -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [filesystems] -> Running build hook: [keyboard] -> Running build hook: [fsck] ==> ERROR: module not found: `nvidia' ==> ERROR: module not found: `nvidia_modeset' ==> ERROR: module not found: `nvidia_uvm' ==> ERROR: module not found: `nvidia_drm' . . . The pertinent lines in the DKMS logs complain about my GLIBC - mine's at 2.35. CC [M] /var/lib/dkms/nvidia/390.138/build/nvidia/nv-cray.o CC [M] /var/lib/dkms/nvidia/390.138/build/nvidia/nv-dma.o scripts/basic/fixdep: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by scripts/basic/fixdep) make[2]: *** [scripts/Makefile.build:279: /var/lib/dkms/nvidia/390.138/build/nvidia/nv-cray.o] Error 1 make[2]: *** Deleting file '/var/lib/dkms/nvidia/390.138/build/nvidia/nv-cray.o' make[2]: *** Waiting for unfinished jobs.... scripts/basic/fixdep: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by scripts/basic/fixdep) make[2]: *** [scripts/Makefile.build:279: /var/lib/dkms/nvidia/390.138/build/nvidia/nv-instance.o] Error 1 make[2]: *** Deleting file '/var/lib/dkms/nvidia/390.138/build/nvidia/nv-instance.o' . . . I spent some time scratching around looking for where/how this is configured but so far I haven't figured it out. Can someone point the way? Where is this set? I looked into the kernel fixdep code a little and tried tweaking it some just to see if I could coax it into installing but haven't yet been able to spend a bunch of time on it. Thanks in advance! -- Randall DuCharme (Radio AD5GB) Powered entirely by Open Source software.

2 1

[arch-general] Gcc 10.2.0-5 cannot create executable error on Archlinux testing.
by fredbezies 04 Feb '21

04 Feb '21

Hello. I had a bad surprise this morning when I tried to build dosbox-x-sdl2-git on my freshly updated Archlinux; checking whether the C compiler works... no configure: error: in `/home/fred/dosbox-x-sdl2-git/src/dosbox-x': configure: error: C compiler cannot create executables I tried midnight commander, same error: ==> Starting build()... checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking whether to enable maintainer-specific portions of Makefiles... no checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking whether make supports the include directive... yes (GNU style) checking for gcc... gcc checking whether the C compiler works... no configure: error: in `/home/fred/mc/src/mc-4.8.25': configure: error: C compiler cannot create executables See `config.log' for more details I noticed binutils, gcc/gcc-libs and glibc were updated this morning. Downgrading these ones and rebooting gave me a working C compiler back. Bug opened: https://bugs.archlinux.org/task/69530 Thread opened on archlinux forum: https://bbs.archlinux.org/viewtopic.php?pid=1953864 -- Frederic Bezies fredbezies(a)gmail.com

1 0

[arch-general] makepkg default flags
by Christopher W. 02 Feb '21

02 Feb '21

A few months back there was a proposal to edit the default makepkg build flags for improved security: https://lists.archlinux.org/pipermail/arch-dev-public/2020-July/030031.html As far as I can tell, this was never committed. The show-stopper at the time was Clang 11 not being released yet. Now that it's been in the repos for a while, could we revisit this improvement and possibly get a mass rebuild with it applied?

1 0