public inbox for nightly-builds@lists.ipfire.org
 help / color / mirror / Atom feed
From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (8f36e4c) for aarch64 on arm64-01.zrh.ipfire.org
Date: Tue, 19 Nov 2024 20:00:43 +0000	[thread overview]
Message-ID: <4XtFjR15tJz1xrg@arm64-01.zrh.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2799 bytes --]

https://nightly.ipfire.org/next/2024-11-19%2020%3A32%3A47%20%2B0100-8f36e4c8/aarch64

commit 8f36e4c8960b43548fca6eee18132e8ead91f7ea
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Tue Nov 19 20:32:47 2024 +0100

    transmission: add minipnpc as dependency
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=8f36e4c8960b43548fca6eee18132e8ead91f7ea

Packaged toolchain compilation
Building IPFire
stage2                                                                  [        1 ][ DONE ]
linux (6.6.62) HEADERS=1                                                [       10 ][ FAIL ]

    cd /usr/src/linux-6.6.62 && patch -Np1 < /usr/src/src/patches/linux/linux-5.15-NFQUEUE-Hold-RCU-read-lock-while-calling-nf_reinject.patch
    patching file net/netfilter/nfnetlink_queue.c
    Hunk #1 succeeded at 232 with fuzz 1 (offset 4 lines).
    # Fix external module compile
    cd /usr/src/linux-6.6.62 && patch -Np1 < /usr/src/src/patches/linux/linux-6.0-fix_external_module_build.patch
    patching file Makefile
    Hunk #1 succeeded at 1791 (offset 57 lines).
    # Apply Arm kernel patches.
    cd /usr/src/linux-6.6.62 && cat patch /usr/src/src/patches/linux/aarch64/* | patch -Np1
    cat: patch: No such file or directory
    patching file arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
    patching file arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
    patching file arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
    patching file arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
    patching file drivers/mmc/core/core.c
    Hunk #1 succeeded at 1368 (offset 5 lines).
    patching file drivers/pci/controller/pcie-rockchip-host.c
    patching file arch/arm64/boot/dts/rockchip/Makefile
    Hunk #1 succeeded at 50 (offset 1 line).
    patching file arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s-oc.dts
    patching file arch/arm64/boot/dts/rockchip/Makefile
    Hunk #1 FAILED at 15.
    1 out of 1 hunk FAILED -- saving rejects to file arch/arm64/boot/dts/rockchip/Makefile.rej
    patching file arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2c-oc.dts
    patching file arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2c-plus-oc.dts
    patching file arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-oc.dts
    patching file arch/arm64/boot/dts/rockchip/rk3328-orangepi-r1-plus-lts-oc.dts
    patching file arch/arm64/boot/dts/rockchip/rk3328-orangepi-r1-plus-oc.dts
    make: *** [linux:125: /usr/src/log/linux-6.6.62-headers] Error 1
    make: Leaving directory '/usr/src/lfs'

ERROR: Building linux                                                   [ FAIL ]
    Check /build/nightly/next/log_aarch64/_build.ipfire.log for errors if applicable[ FAIL ]

                 reply	other threads:[~2024-11-19 20:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4XtFjR15tJz1xrg@arm64-01.zrh.ipfire.org \
    --to=nightly-builds@ipfire.org \
    --cc=nightly-builds@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox