From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: John Ernberg <j@j-ernberg.se>
Cc: buildroot@buildroot.org, Adam Ford <aford173@gmail.com>,
Bernd Kuhls <bernd@kuhls.net>,
Joseph Kogut <joseph.kogut@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [RFC PATCH] package: {libgl, libglvnd, mesa3d}: Propagate libglvnd GL provider to libgl dependencies
Date: Mon, 19 Oct 2026 09:42:17 +0200 [thread overview]
Message-ID: <atXJtW_DvHyZmjz8@windsurf> (raw)
In-Reply-To: <CAAHg4Zgrrsjech9bC9zdkZREEnaB_sV675doMibN+9qw4ypy1A@mail.gmail.com>
On Sun, Oct 18, 2026 at 10:57:15PM +0200, John Ernberg wrote:
> I'm just running mass builds working on finding conflicting packages,
> to hopefully in the end solve the per-package rebuilds as initially
> discussed with Arnout here:
> https://lore.kernel.org/buildroot/20241227160622.1654822-1-john.ernberg@actia.se/T/#u
>
> I run into quite a bunch of build failures in the process.
>
> Personally I have no interest in libglvnd other than being able to
> build "allyesconfig"-like configurations to find conflicts.
>
> I'm also open to ripping libglvnd out if there is no use for it.
OK, thanks for your feedback. Let's see the outcome of the
conversation started with Yann to decide what we do with libglvnd.
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
next prev parent reply other threads:[~2026-10-19 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 16:06 [Buildroot] [RFC PATCH] package: {libgl, libglvnd, mesa3d}: Propagate libglvnd GL provider to libgl dependencies John Ernberg
2026-10-18 20:41 ` Thomas Petazzoni via buildroot
2026-10-18 20:57 ` John Ernberg
2026-10-19 7:42 ` Thomas Petazzoni via buildroot [this message]
2026-10-19 5:53 ` Yann E. MORIN via buildroot
2026-10-19 7:40 ` Thomas Petazzoni via buildroot
2026-10-19 9:54 ` Yann E. MORIN via buildroot
2026-10-19 12:23 ` Thomas Petazzoni 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=atXJtW_DvHyZmjz8@windsurf \
--to=buildroot@buildroot.org \
--cc=aford173@gmail.com \
--cc=bernd@kuhls.net \
--cc=j@j-ernberg.se \
--cc=joseph.kogut@gmail.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.