Bug 15664 - Can't compile mesa3d with v3d driver
Summary: Can't compile mesa3d with v3d driver
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2023.05
Hardware: All Linux
: P5 critical
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-23 15:09 UTC by HiFiBerry (Daniel)
Modified: 2023-06-24 14:27 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description HiFiBerry (Daniel) 2023-06-23 15:09:24 UTC 
To reproduce:

make raspberrypi4_defconfig
make menuconfig
 - Select mesa3d and "Gallium v3d driver"

make clean
make

breaks with

Program decode.py found: YES (/home/m/buildroot-2023.05/output/build/mesa3d-23.1.0/src/compiler/isaspec/decode.py)
Program encode.py found: YES (/home/m/buildroot-2023.05/output/build/mesa3d-23.1.0/src/compiler/isaspec/encode.py)
Run-time dependency v3dv3 found: NO (tried pkgconfig and cmake)
Run-time dependency simpenrose found: NO (tried pkgconfig and cmake)

output/build/mesa3d-23.1.0/src/gallium/drivers/vc4/meson.build:87:16: ERROR:
Trying to compare values of different types (UserFeatureOption, str) using !=.
This was deprecated and undefined behavior previously and is as of 0.60.0 a hard error.

A full log can be found at /home/m/buildroot-2023.05/output/build/mesa3d-23.1.0/build/meson-logs/meson-log.txt
make[1]: *** [package/pkg-generic.mk:283: /home/m/buildroot-2023.05/output/build/mesa3d-23.1.0/.stamp_configured] Error 1
make: *** [Makefile:82: _all] Error 2

Same config is working fine of 2023.02 buildroot release
Comment 1 Bernd Kuhls 2023-06-23 16:36:29 UTC 
The reason for this error is a local buildroot patch:
https://git.busybox.net/buildroot/tree/package/mesa3d/0002-vc4-add-meson-option-to-disable-optional-neon-suppor.patch#n47

Adding the patch author to this bug report...
Comment 2 Bernd Kuhls 2023-06-24 14:27:31 UTC 
The bug was fixed by this commit:
https://git.busybox.net/buildroot/commit/?id=da19c18af2d531b63b6d54f02dc2f16785756e66