From: Yegor Yefremov <yegorslists@googlemail.com>
To: buildroot@buildroot.org
Cc: thomas.petazzoni@bootlin.com
Subject: Re: [Buildroot] [PATCH] package/ncftp: fix cross compilation detection
Date: Mon, 19 Oct 2026 08:01:55 +0200 [thread overview]
Message-ID: <20261019060155.1095583-1-yegorslists@gmail.com> (raw)
In-Reply-To: <atUydCZOiuRB85Kj@windsurf>
From: Yegor Yefremov <yegorslists@googlemail.com>
Hello Thomas,
Sorry for the late reply.
On Sat, Oct 10, 2026 at 07:42:09PM +0200, Thomas Petazzoni wrote:
> 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?
Yes, it's the latter. We actually used to regenerate it (running
autoconf -I autoconf_local in a pre-configure hook) until the 3.2.9
bump, where I had to drop it because it stopped working. With 3.3.0
it still fails:
configure.in:53: error: AC_LANG: unknown language:
autoconf_local/aclocal.m4:415: wi_TRY_RUN_NATIVE is expanded from...
The macros in autoconf_local/aclocal.m4 depend on autoconf 2.13
internals (AC_LANG used as a value, AC_FD_CC, __oline__, ...), and
upstream even ships patches against autoconf 2.13 itself
(acgeneral-2.13.m4.patch, acspecific-2.13.m4.patch), so their configure
is produced by a patched 2.13. Making it work with autoconf 2.7x would
mean porting all of those macros, which is far more invasive than this
small fix to the generated script.
I've just sent a v2 that adds this explanation to the commit message
and also drops the now unneeded host-autoconf dependency, which is a
leftover from that time.
Best regards,
Yegor
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-19 6:02 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 [this message]
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=20261019060155.1095583-1-yegorslists@gmail.com \
--to=yegorslists@googlemail.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.