From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/lrzsz: fix build error
Date: Wed, 4 Feb 2026 17:33:48 +0100 [thread overview]
Message-ID: <aYN0jqRLaX6HAfc8@windsurf> (raw)
In-Reply-To: <20251205181855.1699260-1-bernd@kuhls.net>
Hello Bernd,
On Fri, Dec 05, 2025 at 07:18:55PM +0100, Bernd Kuhls wrote:
> Fixes:
> https://autobuild.buildroot.net/results/2e3/2e33c61e1c9bee099f973c1e43b696c63e5eed4b/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Could you revisit this patch, providing the information that we expect
when fixing build failures? What is the build failure? When did it
start happening? Also, a fix that's not upstreamable looks strange at
first sight. Can we do better?
> +Adding ac_cv_header_stdc=yes to lrzsz.mk would also fix the build error
> +but masks the fact that the cross-compile environment is misdetected.
Not sure to understand this part. What does "masks the fact that the
cross-compile environment is misdetected" actually mean?
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
prev parent reply other threads:[~2026-02-04 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 18:18 [Buildroot] [PATCH 1/1] package/lrzsz: fix build error Bernd Kuhls
2026-02-04 16:33 ` Thomas Petazzoni via buildroot [this message]
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=aYN0jqRLaX6HAfc8@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox