commit a3a88ed appears to have removed the function(s) needed by drm kmod to build and run :-(

        Michael

On 4/19/25 09:06, David Wolfskill wrote:
Running:
FreeBSD g1-118.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #445 
main-n276537-7121e9414f29: Fri Apr 18 12:36:30 UTC 2025     
r...@g1-120.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64

after updating sources to main-n276560-83dcc133c876, with a ports tree
at main-n703265-33b43edfb65d, I find:

...
--- i915_gem_mman.o ---
/common/S4/obj/usr/src/amd64.amd64/sys/CANARY/common/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.128_1/drivers/gpu/drm/i915/gem/i915_gem_mman.c:171:77:
 error: call to undeclared function 'vm_page_next'; ISO C99 and later do not 
support implicit function declarations [-Werror,-Wimplicit-function-declaration]
   171 |                         for (vm_page_t page = 
vm_page_find_least(vmobj, 0); page != NULL; page = vm_page_next(page)) {
       |                                                                        
                          ^
/common/S4/obj/usr/src/amd64.amd64/sys/CANARY/common/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.128_1/drivers/gpu/drm/i915/gem/i915_gem_mman.c:171:75:
 error: incompatible integer to pointer conversion assigning to 'vm_page_t' 
(aka 'struct vm_page *') from 'int' [-Wint-conversion]
   171 |                         for (vm_page_t page = 
vm_page_find_least(vmobj, 0); page != NULL; page = vm_page_next(page)) {
       |                                                                        
                        ^ ~~~~~~~~~~~~~~~~~~
2 errors generated.
*** [i915_gem_mman.o] Error code 1

make[1]: stopped making "all" in 
/common/S4/obj/usr/src/amd64.amd64/sys/CANARY/common/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.128_1/i915
make[1]: 1 error
[end of excerpt from typescript -- dhw]

This is using METAMODE (as I've done for ages, now); unfortunately:

.ERROR_TARGET='all'
.ERROR_META_FILE=''
.MAKE.LEVEL='2'
MAKEFILE=''

so not much to be gained there (that I can see).


I note that using the same ports tree, I had no issue with the
similar update for stable/14, from stable/14-n271086-2a88aad6286d
to stable/14-n271131-ee7a874557f4 (same machine; different slice).

And yesterday's up date for head (main-n276506-a962800a09a4 to
main-n276537-7121e9414f29, with the ports tree at
main-n703215-0bca9d486f25) was uneventful.

Peace,
david


Reply via email to