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


Groups > linux.debian.bugs.dist > #1260511 > unrolled thread

Bug#1114674: otf2 FTCBFS: uses the build architecture compiler

Started byHelmut Grohne <helmut@subdivi.de>
First post2025-09-08 14:00 +0200
Last post2025-09-15 10:50 +0200
Articles 5 — 2 participants

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1114674: otf2 FTCBFS: uses the build architecture compiler Helmut Grohne <helmut@subdivi.de> - 2025-09-08 14:00 +0200
    Bug#1114674: otf2 FTCBFS: uses the build architecture compiler Samuel Thibault <sthibault@debian.org> - 2025-09-08 16:50 +0200
      Bug#1114674: otf2 FTCBFS: uses the build architecture compiler Helmut Grohne <helmut@subdivi.de> - 2025-09-11 21:00 +0200
        Bug#1114674: otf2 FTCBFS: uses the build architecture compiler Samuel Thibault <sthibault@debian.org> - 2025-09-12 16:20 +0200
          Bug#1114674: otf2 FTCBFS: uses the build architecture compiler Helmut Grohne <helmut@subdivi.de> - 2025-09-15 10:50 +0200

#1260511 — Bug#1114674: otf2 FTCBFS: uses the build architecture compiler

FromHelmut Grohne <helmut@subdivi.de>
Date2025-09-08 14:00 +0200
SubjectBug#1114674: otf2 FTCBFS: uses the build architecture compiler
Message-ID<LsIHn-dLiK-3@gated-at.bofh.it>

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

Source: otf2
Version: 3.1.1-3
Tags: patch
User: debian-cross@lists.debian.org
Usertags: ftcbfs

otf2 fails to cross build from source, because it uses the build 
architecture compiler. The project has opinions on compilers and 
overrides them by default. One may opt out of this by passing 
--with-custom-compilers and then it cross builds. I'm attaching a patch 
for your convenience. I also compared a native build with and without 
this additional option to see whether it would result in undesired 
changes. The only file that changes is /usr/share/otf2/otf2.summary and 
that contains all configure arguments.

Helmut

[toc] | [next] | [standalone]


#1260530

FromSamuel Thibault <sthibault@debian.org>
Date2025-09-08 16:50 +0200
Message-ID<LsLlT-dNhF-19@gated-at.bofh.it>
In reply to#1260511
Hello,

Helmut Grohne, le jeu. 04 sept. 2025 12:10:37 +0200, a ecrit:
> otf2 fails to cross build from source, because it uses the build 
> architecture compiler. The project has opinions on compilers and 
> overrides them by default. One may opt out of this by passing 
> --with-custom-compilers and then it cross builds. I'm attaching a patch 
> for your convenience.

It seems it didn't work on the salsa CI:

https://salsa.debian.org/debian/otf2/-/jobs/8240376

“
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in '/builds/debian/otf2/debian/output/source_dir/build-backend':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use '--host'.
”

Samuel

[toc] | [prev] | [next] | [standalone]


#1261015

FromHelmut Grohne <helmut@subdivi.de>
Date2025-09-11 21:00 +0200
Message-ID<LtUGt-eA0e-1@gated-at.bofh.it>
In reply to#1260530
Hi Samuel,

On Mon, Sep 08, 2025 at 04:42:06PM +0200, Samuel Thibault wrote:
> It seems it didn't work on the salsa CI:
> 
> https://salsa.debian.org/debian/otf2/-/jobs/8240376
> 
> “
> checking for suffix of executables...
> checking whether we are cross compiling... configure: error: in '/builds/debian/otf2/debian/output/source_dir/build-backend':
> configure: error: cannot run C compiled programs.
> If you meant to cross compile, use '--host'.
> ”

As much as I see this failing on salsa-ci, I cannot reproduce this
failure locally. This output is from the nested configure invocation.
For reference, the invocation is:

configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr'  'CC_FOR_BUILD=' '--infodir=${prefix}/share/info' '--host=aarch64-linux-gnu' 'CXX=' '--localstatedir=/var' 'FC_FOR_BUILD=' 'CXX_FOR_BUILD=' 'CFLAGS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard' 'CXXFLAGS=-g -O2 -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard' 'FCFLAGS=-g -O2 -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -mbranch-protection=standard' 'F77_FOR_BUILD=' '--build=x86_64-linux-gnu' 'CC=' '--runstatedir=/run' '--sysconfdir=/etc' 'FFLAGS=-g -O2 -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -mbranch-protection=standard' 'FC=' '--libdir=${prefix}/lib/aarch64-linux-gnu' '--includedir=${prefix}/include' 'F77=' '--mandir=${prefix}/share/man' '--with-custom-compilers' '--enable-backend-test-runs' '--disable-dependency-tracking' '--disable-maintainer-mode' '--disable-silent-rules' 'ac_scorep_platform=linux' 'ac_scorep_cross_compiling=no' --cache-file=/dev/null --srcdir=.

Please observe that the 5th option is --host. It is not clear to me why
that is failing on salsa-ci and succeeding locally in sbuild. I suggest
that you move ahead and we check crossqa.debian.net.

Helmut

[toc] | [prev] | [next] | [standalone]


#1261115

FromSamuel Thibault <sthibault@debian.org>
Date2025-09-12 16:20 +0200
Message-ID<LucN4-eMyK-11@gated-at.bofh.it>
In reply to#1261015
Helmut Grohne, le mar. 09 sept. 2025 17:54:46 +0200, a ecrit:
> On Mon, Sep 08, 2025 at 04:42:06PM +0200, Samuel Thibault wrote:
> > It seems it didn't work on the salsa CI:
> > 
> > https://salsa.debian.org/debian/otf2/-/jobs/8240376
> > 
> > “
> > checking for suffix of executables...
> > checking whether we are cross compiling... configure: error: in '/builds/debian/otf2/debian/output/source_dir/build-backend':
> > configure: error: cannot run C compiled programs.
> > If you meant to cross compile, use '--host'.
> > ”
> 
> As much as I see this failing on salsa-ci, I cannot reproduce this
> failure locally. This output is from the nested configure invocation.
> For reference, the invocation is:
> 
> configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr'  'CC_FOR_BUILD=' '--infodir=${prefix}/share/info' '--host=aarch64-linux-gnu' 'CXX=' '--localstatedir=/var' 'FC_FOR_BUILD=' 'CXX_FOR_BUILD=' 'CFLAGS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard' 'CXXFLAGS=-g -O2 -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard' 'FCFLAGS=-g -O2 -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -mbranch-protection=standard' 'F77_FOR_BUILD=' '--build=x86_64-linux-gnu' 'CC=' '--runstatedir=/run' '--sysconfdir=/etc' 'FFLAGS=-g -O2 -ffile-prefix-map=/builds/debian/otf2/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -mbranch-protection=standard' 'FC=' '--libdir=${prefix}/lib/aarch64-linux-gnu' '--includedir=${prefix}/include' 'F77=' '--mandir=${prefix}/share/man' '--with-custom-compilers' '--enable-backend-test-runs' '--disable-dependency-tracking' '--disable-maintainer-mode' '--disable-silent-rules' 'ac_scorep_platform=linux' 'ac_scorep_cross_compiling=no' --cache-file=/dev/null --srcdir=.
> 
> Please observe that the 5th option is --host. It is not clear to me why
> that is failing on salsa-ci and succeeding locally in sbuild.

Does your sbuild tree have arm64 binfmt emulation enabled? It would work
then.

I have found the issue: the score-p infrastructure assumes that Linux
does not cross-compile (as opposed to bluegene etc. environments which
do cross-compile). And another small bit about libdir. It does
cross-build on my box, it should be fine on salsa as well, we will see
on https://salsa.debian.org/debian/otf2/-/pipelines/935033

Samuel

[toc] | [prev] | [next] | [standalone]


#1261500

FromHelmut Grohne <helmut@subdivi.de>
Date2025-09-15 10:50 +0200
Message-ID<Lvd4m-fstP-21@gated-at.bofh.it>
In reply to#1261115
Hi Samuel,

On Fri, Sep 12, 2025 at 04:15:03PM +0200, Samuel Thibault wrote:
> Does your sbuild tree have arm64 binfmt emulation enabled? It would work
> then.

Spot-on. I usually keep a tight eye on disabling qemu-binfmt (as sbuild
does not yet mount the binfmt fs), but here it got enabled again.
crossqa.debian.net would have failed in the same way and thus identified
my build environment as bad.

> I have found the issue: the score-p infrastructure assumes that Linux
> does not cross-compile (as opposed to bluegene etc. environments which
> do cross-compile). And another small bit about libdir. It does
> cross-build on my box, it should be fine on salsa as well, we will see
> on https://salsa.debian.org/debian/otf2/-/pipelines/935033

Cool. Thank you.

Helmut

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web