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 (b71fe1a) for riscv64 on riscv64-01.haj.ipfire.org
Date: Sat, 12 Oct 2024 10:05:43 +0000	[thread overview]
Message-ID: <4XQfJR6czgz2xly@riscv64-01.haj.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2024-10-12%2009%3A38%3A25%20%2B0000-b71fe1a1/riscv64

commit b71fe1a1e7bea7d95777ceb6a0bc0c8a87ea14f6
Author: Adolf Belka <adolf.belka(a)ipfire.org>
Date:   Thu Oct 10 18:01:11 2024 +0200

    tshark: Update to version 4.4.1
    
    - Update from version 4.2.7 to 4.4.1
    - The 4.4.x series is the new Stable Release replascing the 4.2.x series which becomes
       the Old Stable Release.
    - There is an sobump so find-dependencies was run for the three libraries with changes
       but all linked programs are within tshark.
    - Changelog is too large to include here. Links provided
        4.4.1
            https://www.wireshark.org/docs/relnotes/wireshark-4.4.1.html
        4.4.0
            https://www.wireshark.org/docs/relnotes/wireshark-4.4.0.html
    
    Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Packaged toolchain compilation
Building IPFire
stage2                                                                  [       24 ][ DONE ]
linux (6.6.56) HEADERS=1                                                [     4:51 ][ FAIL ]

    HDRINST usr/include/linux/wwan.h
    HDRINST usr/include/linux/nilfs2_ondisk.h
    HDRINST usr/include/linux/arcfb.h
    HDRINST usr/include/linux/mpls.h
    HDRINST usr/include/linux/hdlc.h
    HDRINST usr/include/linux/fb.h
    HDRINST usr/include/linux/net.h
    HDRINST usr/include/linux/wmi.h
    HDRINST usr/include/linux/if_ppp.h
    HDRINST usr/include/linux/virtio_iommu.h
    HDRINST usr/include/linux/erspan.h
    HDRINST usr/include/linux/keyboard.h
    HDRINST usr/include/linux/cifs/cifs_mount.h
    HDRINST usr/include/linux/cifs/cifs_netlink.h
    HDRINST usr/include/linux/if_plip.h
    HDRINST usr/include/linux/mrp_bridge.h
    HDRINST usr/include/linux/rkisp1-config.h
    HDRINST usr/include/linux/coda.h
    HDRINST usr/include/linux/cec.h
    HDRINST usr/include/linux/poll.h
    HDRINST usr/include/linux/ptrace.h
    HDRINST usr/include/linux/atmsap.h
    HDRINST usr/include/linux/igmp.h
    HDRINST usr/include/linux/handshake.h
    make[3]: *** [scripts/Makefile.headersinst:63: usr/include/linux/rio_mport_cdev.h] Segmentation fault
    make[2]: *** [/usr/src/linux-6.6.56/Makefile:1297: headers] Error 2
    make[1]: *** [Makefile:234: __sub-make] Error 2
    make[1]: Leaving directory '/usr/src/linux-6.6.56'
    make: *** [linux:127: /usr/src/log/linux-6.6.56-headers] Error 2
    make: Leaving directory '/usr/src/lfs'

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

                 reply	other threads:[~2024-10-12 10:05 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=4XQfJR6czgz2xly@riscv64-01.haj.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