Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ncftp: fix cross compilation detection
Date: Sun, 18 Oct 2026 22:56:37 +0200	[thread overview]
Message-ID: <atUydCZOiuRB85Kj@windsurf> (raw)
In-Reply-To: <asp4qInIYNj-7JlB@windsurf>

Hello Yegor,

Do you have some feedback on the below questions?

Thanks!

Thomas

On Sat, Oct 10, 2026 at 07:42:09PM +0200, Thomas Petazzoni via buildroot wrote:
> Hello,
> 
> On Thu, Sep 03, 2026 at 01:47:21PM +0200, Yegor Yefremov via buildroot wrote:
> 
> > So add a patch making the generated configure script follow what
> > autoconf has been doing since 2.50, and consider the build cross
> > compilation as soon as --host is given and differs from --build,
> > regardless of whether the produced binaries happen to be runnable.
> 
> Instead of patching the generated configure script, have you tried
> using AUTORECONF = YES to fully regenerate the configure script from
> the configure.in? Or perhaps this is hopeless as the configure.in is
> ancient and any modern autoconf while not accept this ancient
> configure.in?
> 
> 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

-- 
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

  reply	other threads:[~2026-10-18 20:56 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 [this message]
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
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=atUydCZOiuRB85Kj@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