E: Mesa 64bit-portability-issue nouveau_texture.c:400, 489
E: Mesa 64bit-portability-issue nouveau_screen.c:254, 257
nouveau_texture.c: In function 'nouveau_teximage':
nouveau_texture.c:400:2: warning: implicit declaration of function '_mesa_validate_pbo_teximage'
nouveau_texture.c:400:9: warning: assignment makes pointer from integer without a cast
nouveau_texture.c:417:3: warning: implicit declaration of function '_mesa_unmap_teximage_pbo'
nouveau_texture.c: In function 'nouveau_texsubimage':
nouveau_texture.c:489:9: warning: assignment makes pointer from integer without a cast
nouveau_mm.c: In function 'mm_slab_new':
nouveau_mm.c:147:17: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'uint64_t'
nouveau_screen.c: In function 'nouveau_screen_init':
nouveau_screen.c:254:2: warning: implicit declaration of function 'nouveau_mm_create'
nouveau_screen.c:254:18: warning: assignment makes pointer from integer without a cast
nouveau_screen.c:257:18: warning: assignment makes pointer from integer without a cast
nouveau_screen.c: In function 'nouveau_screen_fini':
nouveau_screen.c:266:2: warning: implicit declaration of function 'nouveau_mm_destroy'
Importance: highest/blocker because it is not possible to build it on openSUSE (see: https://build.opensuse.org/package/live_build_log?arch=i586&package=Mesa&project=home%3Ajobermayr&repository=openSUSE_11.4)
and determinate offenders:
- Assign to mesa-dev
- CC Brian Paul, Ben Skeggs
Created attachment 44588 [details] [review]
Fix serious compiler warnings.
It is a damning indictment of main (mesa) developers that they cannot add two '#includes' within two weeks ...
(A non-developer who (still) does not understand any C/C++ source code [not to mention Mesa's source code] must spend days for doing it.)
I've committed your patch. Thanks.
BTW, different people are responsible for different parts of Mesa and the various drivers. Generally, those people take care of the patches/bugs that effect their components. Just because the nouveau developers may not have been active lately isn't a reason to condemn the project or other developers. I guess I missed this bug before.