Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14856] nvidia-driver package fails to build
Date: Tue, 21 Jun 2022 07:30:12 +0000	[thread overview]
Message-ID: <bug-14856-163-KCh0esGMHH@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14856-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14856

--- Comment #5 from Dr I J Ormshaw <ian_ormshaw@waters.com> ---
I am still not able to compile the drivers.  It would appear from
https://gist.github.com/joanbm/144a965c36fc1dc0d1f1b9be3438a368.  That the
patch you have applied only works for 5.10 -> 5.13 and the build breaks again
from 5.14 on.

In file included from
../nvidia-driver-390.144/kernel/common/inc/os-interface.h:27,
                 from ../nvidia-driver-390.144/kernel/nvidia/nv-procfs.c:14:
../../host/lib/gcc/x86_64-WatersAMST-linux-gnu/11.3.0/include/stdarg.h:52:
note: this is the location of the previous definition
   52 | #define va_copy(d,s)    __builtin_va_copy(d,s)
      | 
../nvidia-driver-390.144/kernel/nvidia-drm/nvidia-drm-drv.c: In function
‘nv_drm_register_drm_device’:
../nvidia-driver-390.144/kernel/nvidia-drm/nvidia-drm-drv.c:814:10: error:
‘struct drm_device’ has no member named ‘pdev’; did you mean ‘dev’?
  814 |     dev->pdev = pdev;
      |          ^~~~
      |          dev
make[3]: *** [scripts/Makefile.build:288:
/home/ian/build/amst-hiwire-linux-9297fa84-x86_64/buildroot/build/nvidia-driver-390.144/kernel/nvidia-drm/nvidia-drm-drv.o]
Error 1
../nvidia-driver-390.144/kernel/nvidia/nvlink_linux.c: In function
‘nvlink_sleep’:
../nvidia-driver-390.144/kernel/nvidia/nvlink_linux.c:600:18: error: ‘struct
task_struct’ has no member named ‘state’; did you mean ‘__state’?
  600 |         current->state = TASK_INTERRUPTIBLE;
      |                  ^~~~~
      |                  __state
make[3]: *** [scripts/Makefile.build:288:
/home/ian/build/amst-hiwire-linux-9297fa84-x86_64/buildroot/build/nvidia-driver-390.144/kernel/nvidia/nvlink_linux.o]
Error 1
make[2]: *** [Makefile:1868:
/home/ian/build/amst-hiwire-linux-9297fa84-x86_64/buildroot/build/nvidia-driver-390.144/kernel]
Error 2
make[2]: Leaving directory
'/home/ian/build/amst-hiwire-linux-9297fa84-x86_64/buildroot/build/linux-5.15.44'
make[1]: *** [package/pkg-generic.mk:294:
/home/ian/build/amst-hiwire-linux-9297fa84-x86_64/buildroot/build/nvidia-driver-390.144/.stamp_built]
Error 2
make[1]: Leaving directory
'/home/ian/projects/amst-hiwire-linux/source/buildroot'
make: *** [Makefile:616: buildroot] Error 2

The no cc check patch works as expected on Fedora 36

-- 
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

  parent reply	other threads:[~2022-06-21  7:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  9:03 [Buildroot] [Bug 14856] New: nvidia-driver package fails to build bugzilla
2022-06-20  9:16 ` [Buildroot] [Bug 14856] " bugzilla
2022-06-20 13:47 ` bugzilla
2022-06-20 14:17 ` bugzilla
2022-06-20 17:32 ` bugzilla
2022-06-21  7:30 ` bugzilla [this message]
2022-06-21  8:43 ` bugzilla
2022-06-21 12:02 ` bugzilla
2022-06-21 12:43 ` bugzilla
2024-06-15 15:03 ` 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-14856-163-KCh0esGMHH@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