Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #80280

Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa

From Johannes Schauer Marin Rodrigues <josch@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa
Date 2023-09-03 10:10 +0200
Message-ID <H9Qlc-6nsE-11@gated-at.bofh.it> (permalink)
References (1 earlier) <H95YZ-5SFI-1@gated-at.bofh.it> <H96BH-5TeG-5@gated-at.bofh.it> <H9DnX-6eTa-3@gated-at.bofh.it> <H95YZ-5SFI-1@gated-at.bofh.it> <H9DnX-6eTa-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Quoting Bastian Blank (2023-09-02 20:10:44)
> On Fri, Sep 01, 2023 at 09:15:50AM +0200, Johannes Schauer Marin Rodrigues wrote:
> > Helmut informed me that bugs that break bootstrap (rebootstrap fails to
> > cross-build linux-libc-dev because of this bug) are usually filed with serious
> > severity, so doing that now. Thanks!
> 
> Cross-building linux-libc-dev, by using the proper build profiles
> pkg.linux.nokernel and pkg.linux.notools, does not even reach this code
> paths.

so rebootstrap uses the stage1 build profile which should be building headers
only. Still it fails with the same error I've reported for a full build:

https://jenkins.debian.net/view/rebootstrap/job/rebootstrap_arm64_gcc13_supported/lastFailedBuild/console

Is the stage1 build profile accidentally going the wrong code-path but should
not? Theoretically, stage1 should automatically exclude kernel and tools,
right?

Thanks!

cheers, josch

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-09-01 08:40 +0200
  Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-09-01 09:20 +0200
    Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Bastian Blank <waldi@debian.org> - 2023-09-02 20:20 +0200
      Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-09-03 10:10 +0200
        Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Bastian Blank <waldi@debian.org> - 2023-09-03 10:30 +0200
  Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-09-01 11:00 +0200
  Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Bastian Blank <waldi@debian.org> - 2023-09-02 20:20 +0200
    Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-09-02 20:20 +0200

csiph-web