[Bug 294096] graphics/nvidia-drm-66-kmod unbuildable ISO C99 and later do not support implicit function declarations

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294096

--- Comment #2 from [email protected] ---
(In reply to Tomoaki AOKI from comment #1)
amd64 releng 15 p5, was in the middle of updating from p4 via source, compiled
but not installed yet as is my custom when both nvidia and the patch level go
up together.

make.conf is pretty basic, only tweaks here, native because gcc in ports don't
know what zen5 in proper cputype jargon means for amd 9975WX 

CPUTYPE?=native
COPTFLAGS+= -O -pipe
KERNCONF?=CUSTOMNAME
LICENSES_ACCEPTED=UNKNOWN ZIB BROADCOM NONE ISC MPEG2ENC Proprietary
MAKE_JOBS_NUMBER=60
DEFAULT_VERSIONS+=ssl=base
DEFAULT_VERSIONS+=mysql=1011m
DEFAULT_VERSIONS+=samba=4.22
DOC_LANG?=      en en_US.ISO8859-1 en_US.UTF-8
WITH_LETTERSIZE=yes
PAPERSIZE=letter

no custom anything, first time in like at least 5 years I'm not even running
local ports patch hacks for options I wanted that never made it to ports. 

really wanted to have maybe no more kernel traps randomly at boot when nvidia
driver loads with my 5070, but stuck on 580 legacy drivers. Even after install
releng15.0p5, and attempts to rebuild still dies at same place. even tried
turning off old options in my portconf config files for the driver part,
nothing. Outside of running custom kernel mainly to remove impossible to use
hardware or add support for this systems.

then there is this which suggest the function dying pm_vt_switch_required
doesn't exist until 15-stable oct 2025

https://mail-archive.freebsd.org/cgi/getmsg.cgi?fetch=474836+0+archive/2025/dev-commits-src-all/20251215.dev-commits-src-all

so yeah, I would suspect you can build it on 15-stable if your system is up to
date, whereas releng 15 doesn't have that function defined in the linuxkpi
stack

/sys/compat/linuxkpi/common/include/linux/pm.h

checked there after finding the mail archive result on searching, and looked in
my header, which is at least from june 2024, not sure of date in tree vs
timestamp in my local git repo.

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.