Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Cc: Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/glibc: add a patch to fix build issue in kernels >= 3.15 and < 5.1 on Microblaze
Date: Tue, 25 Jan 2022 18:39:15 +0100	[thread overview]
Message-ID: <2d5dcf47-01c7-8a69-5ac9-25440798bd19@korsgaard.com> (raw)
In-Reply-To: <20211226104520.663206-1-thomas.petazzoni@bootlin.com>

On 26/12/2021 11.45, Thomas Petazzoni wrote:
> As explained in the patch itself, there is a bug in the handling of
> __pselect32() in glibc for the Microblaze architecture. There a
> special Microblaze variant that was added to support kernels older
> than < 3.15, but it "hides" a generic implementation that is needed to
> support kernels newer than 3.15 but older than 5.1 (which is when the
> time64 support for 32-bit architectures was added, making __pselect32
> no longer needed).
> 
> This bug causes a glibc build failure for kernels >= 3.15 but < 5.1,
> on Microblaze.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2021.11.x, thanks.

--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-01-25 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 10:45 [Buildroot] [PATCH] package/glibc: add a patch to fix build issue in kernels >= 3.15 and < 5.1 on Microblaze Thomas Petazzoni
2021-12-27 21:27 ` Yann E. MORIN
2022-01-25 17:39 ` Peter Korsgaard [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=2d5dcf47-01c7-8a69-5ac9-25440798bd19@korsgaard.com \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox