Re: Porter roll call for Debian Bookworm

On 2021-10-02, Graham Inggs wrote: > * Which architectures are you committing to be an active porter for? armhf, arm64 > * Please describe recent relevant porter contributions. Maintaining u-boot (bootloader used on many arm64 and armhf plaforms), arm-trusted-firmware (arm64 firmware), and oc

Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target

Package: u-boot Version: 2022.01+dfsg1-1 Severity: serious X-Debbugs-Cc: debian-powerpc@lists.debian.org, q...@packages.debian.org, binut...@packages.debian.org Something in the toolchain recently changed which causes u-boot arch:all build to FTBFS... I suspect binutils, as building in "bookworm"

Re: Porter roll call for Debian Bullseye

On 2020-11-20, Graham Inggs wrote: > A friendly reminder about the porter roll call for bullseye. > > On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: >> We are doing a roll call for porters of all release architectures. If >> you are an active porter behind one of the release architectures [1] >

Re: failed powerpc build of u-boot 2014.04+dfsg1-2

On Wed, Jul 09, 2014 at 10:00:02PM +, Debian buildds wrote: > * Source package: u-boot > * Version: 2014.04+dfsg1-2 > * Architecture: powerpc > * State: failed > * Suite: sid > * Builder: praetorius.debian.org > * Build log: > https://buildd.debian.org/fetch.cgi?pkg=u-boot&arch=powerpc&

Re: Bug#754610: u-boot: FTBFS on powerpc: ld.bfd: _GLOBAL_OFFSET_TABLE_ not defined in linker created .got / bad value

On Sun, Jul 13, 2014 at 02:41:04AM +0200, Cyril Brulebois wrote: > your package no longer builds on powerpc: > | LD u-boot > | ld.bfd: _GLOBAL_OFFSET_TABLE_ not defined in linker created .got > | ld.bfd: final link failed: Bad value > | make[2]: *** [u-boot] Error 1 > > Full build log: >