All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/ncurses: install wide-char headers in usr/include/ncursesw/
Date: Thu, 29 Oct 2026 22:12:11 +0100	[thread overview]
Message-ID: <auOzktFWazi2guZ8@windsurf> (raw)
In-Reply-To: <20261029204953.1447140-1-bernd@kuhls.net>

On Thu, Oct 29, 2026 at 09:49:52PM +0100, Bernd Kuhls wrote:
> Python 3.15 changed its ncurses wide-/non-wide-char detection and now
> relies on detecting the correct headers:
> https://github.com/python/cpython/commit/383c7bd38a5f0923db48f67fda9d852d189921e6
> 
> Buildroot toolchain x86-64-core-i7--glibc--bleeding-edge-2026.08-1
> contains the non-wide-char version of sysroot/usr/include/curses.h
> which overwrites the wide-char version provided by the ncurses package
> during the configure/rsync stage of the python3 package in the case of
> BR2_PER_PACKAGE_DIRECTORIES=y. The toolchain package is sorted alpha-
> betically after the ncurses package.

I am wondering if this is not a defect of the Bootlin
toolchains. Their sysroot should be "pure", i.e not be polluted by
extra libraries. I'm actually confused why we have ncurses in the
target sysroot in the first place, I see no reason for that.

So if that patch is solely to fix this issue with Bootlin toolchains,
I would rather fix the toolchains.

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

      parent reply	other threads:[~2026-10-29 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 20:49 [Buildroot] [PATCH 1/2] package/ncurses: install wide-char headers in usr/include/ncursesw/ Bernd Kuhls
2026-10-29 20:49 ` [Buildroot] [PATCH 2/2] package/python3: bump version to 3.15.2 Bernd Kuhls
2026-10-29 21:13   ` Thomas Petazzoni via buildroot
     [not found]   ` <auO2ugenOrGrEKGM__30665.5666836136$1793308450$gmane$org@windsurf>
2026-10-29 21:33     ` Bernd Kuhls
2026-10-29 21:49       ` Thomas Petazzoni via buildroot
2026-10-29 21:12 ` 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=auOzktFWazi2guZ8@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=james.hilliard1@gmail.com \
    --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.