From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15121] New: make nconfig failes with nvidia drivers and mesa3d selected
Date: Fri, 11 Nov 2022 12:46:47 +0000 [thread overview]
Message-ID: <bug-15121-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15121
Bug ID: 15121
Summary: make nconfig failes with nvidia drivers and mesa3d
selected
Product: buildroot
Version: 2022.08
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: ian_ormshaw@waters.com
CC: buildroot@uclibc.org
Target Milestone: ---
I am currently using 2022-11, but this has been a problem with earlier versions
too,
I'm trying to produce a system on which I can run opencl code on an nvidia
graphics card. It would appear to me that both the nvidia drivers and mesa3d
are required to make this work. nconfig allows me to selet both but then fails
on exit after the configuration is saved.
####### making buildroot-config Updating the default AMST buildroot
configuration
make[1]: Entering directory
'/home/ian/build/amst-hiwire-linux_5-provide-an-opencl-platform_x86_64/buildroot'
package/mesa3d-headers/mesa3d-headers.mk:10: *** mesa3d-headers enabled, but
mesa3d enabled too. Stop.
make[1]: *** [Makefile:23: _all] Error 2
make[1]: Leaving directory
'/home/ian/build/amst-hiwire-linux_5-provide-an-opencl-platform_x86_64/buildroot'
make: *** [Makefile:630: buildroot-config] Error 2
--
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
next reply other threads:[~2022-11-11 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 12:46 bugzilla [this message]
2022-11-11 22:45 ` [Buildroot] [Bug 15121] make nconfig failes with nvidia drivers and mesa3d selected bugzilla
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@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 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.