From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ncurses: fix uClibc-ng compile error
Date: Wed, 14 Aug 2024 23:03:58 +0200 [thread overview]
Message-ID: <20240814230358.576be4cc@windsurf> (raw)
In-Reply-To: <Zrz8vdUIY6wBPD7m@waldemar-brodkorb.de>
Hello Waldemar!
On Wed, 14 Aug 2024 20:51:41 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> Unfortunately upstream does not use any SCM.
Yeah, kind of crazy.
> See here for the Changelog:
> https://invisible-island.net/ncurses/NEWS.html#index-t20231014
>
> "+ updated configure script macro CF_XOPEN_SOURCE, for uClibc-ng"
>
> Fixes:
> - http://autobuild.buildroot.net/results/01c/01cbc188c70f53fe492128100b430857f1cd98f2
> - http://autobuild.buildroot.net/results/e2b/e2ba6a5554bfa0bf9b4c2eaf9222d041204f00e9
>
> And many more.
So I've applied to master, but to me this is not the "perfect" patch.
The perfect patch would have researched when this issue was introduced,
so that we know if it needs to be backported to a LTS branch. Could you
try to think about this for next fixes?
Another suggestion: I see that ncurses 6.5 has been released, perhaps
time to update? (But of course that will be for our 'next' branch).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-14 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 18:51 [Buildroot] [PATCH] package/ncurses: fix uClibc-ng compile error Waldemar Brodkorb
2024-08-14 21:03 ` 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=20240814230358.576be4cc@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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