All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Thomas Devoogdt <thomas.devoogdt@barco.com>,
	Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2] package/util-linux: bump to 2.41
Date: Tue, 22 Apr 2025 09:55:28 +0200	[thread overview]
Message-ID: <20250422095528.0006b78b@windsurf> (raw)
In-Reply-To: <CACXRmJh1modbu_ODmUs8_iqMUw1tRwr3h4LC8EERgCjTZrsz+A@mail.gmail.com>

Hello Thomas,

On Tue, 22 Apr 2025 09:32:55 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:

> The first issue,
> (Reported here https://github.com/util-linux/util-linux/issues/3501)
> 
> error: expected identifier before numeric constant
>    35 |   MS_RDONLY = 1,                /* Mount read-only.  */
>       |   ^~~~~~~~~
> 
> has been fixed by in uClibc in commit
> https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=96af6db3a430a22d5e8a45f6e7284362866b3980.

This one is in uClibc-ng 1.0.52, so it means it will for now continue
to cause issues with Bootlin toolchains, as the latest are based on
1.0.52. I need to have a look at building new Bootlin toolchains, but I
was hoping to do that when gcc 15.x is available.

> The second issue,
> (Reported here https://github.com/util-linux/util-linux/issues/3502)
> 
> sys-utils/lsns.c:580:19: error: ‘SIOCGSKNS’ undeclared (first use in
> this function)
>   nsfd = ioctl(sk, SIOCGSKNS);
>                    ^~~~~~~~~
> 
> has been fixed in commit
> https://github.com/util-linux/util-linux/commit/10ee66ed1b08586bde42582e34355418eef33ef5.
> 
> It is only applicable for Linux < 4.10, but I will update this bump
> with a patch for this.

Thanks, sounds good!

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

  reply	other threads:[~2025-04-22  7:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 10:16 [Buildroot] [PATCH v1] package/util-linux: bump to 2.41 Thomas Devoogdt
2025-03-26 13:24 ` Waldemar Brodkorb
2025-04-02  8:26   ` [Buildroot] [PATCH v2] " Thomas Devoogdt
2025-04-02 10:18     ` Thomas Devoogdt
2025-04-02 11:08     ` Waldemar Brodkorb
2025-04-02 17:08       ` Thomas Devoogdt
2025-04-02 17:40         ` Waldemar Brodkorb
2025-04-02 18:56         ` Waldemar Brodkorb
2025-04-02 20:27           ` Thomas Devoogdt
2025-04-21 21:31             ` Thomas Petazzoni via buildroot
2025-04-22  7:32               ` Thomas Devoogdt
2025-04-22  7:55                 ` Thomas Petazzoni via buildroot [this message]
2025-04-22  7:59                   ` [Buildroot] [PATCH v3] " Thomas Devoogdt
2025-04-22  8:40                     ` Thomas Petazzoni via buildroot
2025-06-25 14:55                     ` Marcus Hoffmann via buildroot
2025-06-26 19:49                       ` Thomas Devoogdt
2025-06-26 19:47                     ` [Buildroot] [PATCH v4] package/util-linux: bump to 2.41.1 Thomas Devoogdt
2025-07-05 17:26                       ` Julien Olivain 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=20250422095528.0006b78b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.devoogdt@barco.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.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.