From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15121] make nconfig failes with nvidia drivers and mesa3d selected
Date: Fri, 11 Nov 2022 22:45:31 +0000 [thread overview]
Message-ID: <bug-15121-163-8d7ncZqTfz@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15121-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15121
Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Thanks for your bug report, but there is no bug here.
Buildroot only allows one OpenGL provider to be selected. Indeed, if you have
multiple OpenGL providers, they will simply step on each other.
mesa3d-headers is a package that is selected by the nvidia drivers package, as
the nvidia drivers package does not provide the OpenGL headers.
mesa3d is another OpenGL implementation.
So having mesa3d and nvidia drivers enabled in the same configuration does not
make sense, and that's what the error message is telling you.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-11 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 12:46 [Buildroot] [Bug 15121] New: make nconfig failes with nvidia drivers and mesa3d selected bugzilla
2022-11-11 22:45 ` bugzilla [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=bug-15121-163-8d7ncZqTfz@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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