From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [SOLVED] eselect-opengl Blockage (with a capital "B") problem
Date: Tue, 19 May 2020 15:14:03 +0200 [thread overview]
Message-ID: <A6A61905-C5D5-4DE1-B167-15A15BF95025@antarean.org> (raw)
In-Reply-To: <20200518183518.GA10652@waltdnes.org>
On 18 May 2020 20:35:18 CEST, Walter Dnes <waltdnes@waltdnes.org> wrote:
>On Mon, May 18, 2020 at 07:07:32PM +0100, Ashley Dixon wrote
>> On Mon, May 18, 2020 at 01:53:19PM -0400, Walter Dnes wrote:
>> >
>> > ...is attached, gzipped. Problems with "Block". My secondary
>machine
>> > is about to undergo the python 3.6 to 3.7 upgrade if that means
>> > anything. I've tried the usual trick of unmerging eselect-opengl
>but
>> > that didn't help. A similar update went OK on my main machine.
>>
>> The mesa ebuild blocks eselect-opengl if the libglvnd USE-flag is
>set.
>> If you want eselect-opengl, remove the libglvnd flag.
>
> Thank you very much. I've got the update (156 packages) running now.
>I had set "-libglvnd" in make.conf on my main machine, but only against
>xorg-server on my secondary machine. Setting "-libglvnd" in make.conf
>solves the problem.
Only for now.
"Libglvnd" is scheduled to be removed as a USE flag.
I would definitely suggest to switch to having that one on before it becomes mandatory.
It has a lot of benefits over the eselect hack to be able to have multiple opengl implementations running.
--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-05-19 13:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 17:53 [gentoo-user] eselect-opengl Blockage (with a capital "B") problem Walter Dnes
2020-05-18 18:07 ` Ashley Dixon
2020-05-18 18:35 ` [gentoo-user] [SOLVED] " Walter Dnes
2020-05-19 13:14 ` J. Roeleveld [this message]
2020-05-20 3:44 ` Walter Dnes
2020-05-20 4:06 ` Ashley Dixon
2020-05-20 5:49 ` J. Roeleveld
2020-05-20 6:07 ` Dale
2020-05-20 11:37 ` Victor Ivanov
2020-05-20 12:10 ` Dale
2020-05-20 12:47 ` J. Roeleveld
2020-05-20 16:28 ` Dr Rainer Woitok
2020-05-20 17:04 ` Dale
2020-05-20 12:46 ` J. Roeleveld
2020-05-18 18:09 ` [gentoo-user] " Neil Bothwick
2020-05-18 18:21 ` Ashley Dixon
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=A6A61905-C5D5-4DE1-B167-15A15BF95025@antarean.org \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.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