Re: Bullseye on the QNAP TS-220
* Martin Michlmayr [2021-09-16 16:17]: > BTW, Karsten Sperling took another approach and changed the u-boot > config to change the MTD partition layout. Arnaud Mouiche has taken a similar approach and has written a script that will automatically configure QNAP devices. I think that's the best approach for those who want to run bullseye on their QNAP. The script can be found here: https://github.com/amouiche/qnap_mtd_resize_for_bullseye If someone uses this script, please post your feedback here. -- Martin Michlmayr https://www.cyrius.com/
Re: Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8
Hello! On 9/29/21 00:38, John Paul Adrian Glaubitz wrote: > There is actually a baseline violation on i386 as "-march=amdfam10" is > passed to the compiler, see the build log in [1], for example. Comparing the build logs, it seems that this an issue with the newer version of autoconf that was used to build version 3.4.2-2. Looking at the log for 3.4.2-2, a lot of autoconf warnings can be seen which are not present in the log for 3.4.1-1. > https://buildd.debian.org/status/fetch.php?pkg=libffi=powerpc=3.4.2-1=1626443428=0 > https://buildd.debian.org/status/fetch.php?pkg=libffi=powerpc=3.4.2-2=1632868252=0 So, upstream needs to fix compatibility issues with the newer autoconf version. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8
Hi! On 9/28/21 22:40, John Paul Adrian Glaubitz wrote: > We should therefore pass "--enable-portable-binary" in debian/rules. There is actually a baseline violation on i386 as "-march=amdfam10" is passed to the compiler, see the build log in [1], for example. Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=libffi=i386=3.4.2-2=1632469242=0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#995223: libffi: SIGILL on powerpc and ppc64 systems since libffi8
Control: severity -1 serious Hello! It turns out that m4/ax_gcc_archflag.m4 contains code to detect the baseline of the host system and sets the GCC architecture accordingly. Thus, a libffi compiled on a POWER8 machine will not work on a POWER5 machine as the compiler is emitting POWER8 instructions in this case. Since the m4 script contains such a host enviroment detection for aarch64 as well [1], this bug can potentially affect arm64 which is a release architecture. We should therefore pass "--enable-portable-binary" in debian/rules. Adrian > [1] https://github.com/libffi/libffi/blob/master/m4/ax_gcc_archflag.m4#L209 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Debian armhf test system?
On Sat, Sep 25, 2021 at 09:59:51AM -0400, Jeffrey Walton wrote: > We are trying to track down the cause of a build failure on Debian; > see [1]. I want to setup a Debian armhf system for testing. (I have > about 6 testing boards, but they are other OSes). > > I found the relevant area of the manual that says Debian supports > armel, armhf and arm64,[2] but I have not found a list of supported > hardware like a specific SBC. > > Can someone provide a recommendation for a readily available armhf > device? Like something I can order from Amazon? If you have an AWS account, you can launch an arm64 VM on Amazon EC2 running a Debian AMI. From there, setting up an armhf environment is a simple matter of debootstrap and chroot. Debian AMIs are here: https://aws.amazon.com/marketplace/seller-profile?id=4d4d4e5f-c474-49f2-8b18-94de9d43e2c0 noah signature.asc Description: PGP signature
