From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/ncftp: fix cross compilation detection
Date: Mon, 19 Oct 2026 15:48:02 +0200 [thread overview]
Message-ID: <atYfa40Xpbsq18Lk@windsurf> (raw)
In-Reply-To: <20261019060028.1078791-1-yegorslists@gmail.com>
Hello,
On Mon, Oct 19, 2026 at 08:00:28AM +0200, Yegor Yefremov via buildroot wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> ncftp still ships a configure script generated with autoconf 2.13, which
> determines whether it is cross compiling by simply trying to run a
> trivial program built with $CC, instead of looking at --host/--build.
> That heuristic breaks when the build machine is able to execute the
> binaries produced by the cross compiler, which is typically the case
> when building for x86/x86-64 on an x86-64 machine:
>
> checking whether the C compiler (...) is a cross-compiler... no
[...]
Thanks for the new iteration. But... which commit/change introduced
the regression? If you're not able to trace back the origin of the
regression, does it happen in 2025.02.x?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-19 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:47 [Buildroot] [PATCH] package/ncftp: fix cross compilation detection Yegor Yefremov via buildroot
2026-10-10 17:42 ` Thomas Petazzoni via buildroot
2026-10-18 20:56 ` Thomas Petazzoni via buildroot
2026-10-19 6:01 ` Yegor Yefremov
2026-10-19 6:00 ` [Buildroot] [PATCH v2] " Yegor Yefremov via buildroot
2026-10-19 13:48 ` Thomas Petazzoni via buildroot [this message]
2026-10-19 14:18 ` [Buildroot] [PATCH v3] " Yegor Yefremov via buildroot
2026-10-19 16:57 ` Thomas Petazzoni via buildroot
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=atYfa40Xpbsq18Lk@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.com \
/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