Bug 14946 - Missing dependencies for virgl xorg configuration
Summary: Missing dependencies for virgl xorg configuration
Status: RESOLVED MOVED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2022.05.1
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-06 13:57 UTC by Tobias Röhmel
Modified: 2024-06-15 15:03 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Röhmel 2022-08-06 13:57:04 UTC
Hi all,

I was trying to run buildroot on AARCH64 softmmu Qemu with X-server and virgl graphics acceleration and found out that it doesn't work without these 2 configurations: BR2_PIC_PIE (RELRO Protection=none) BR2_PACKAGE_LIBEPOXY.

My buildroot configuration is qemu_aarch64_virt_defconfig + the graphics stuff
as in the attachment.

If RELRO Protection is enabled, the X-server loads libraries in such an order that virtio_gpu_dri.so (the virtio GPU driver) is not found.

If BR2_PACKAGE_LIBEPOXY is not enabled, xorg is built without glamor_gbm which makes the dri2 initialization for the driver fail.

I'm not a graphics expert so I don't know if this is somehow intended. I think it would be easier if these dependencies would be sorted out automatically.

The Qemu I used is upstream with the following configure:
configure --target-list=aarch64-softmmu --enable-debug --enable-opengl --enable-virglrenderer --enable-gtk --enable-sdl
and the following command:
qemu-system-aarch64 -machine virt -cpu max -kernel Image -serial mon:stdio -m size=4G -device virtio-gpu-gl-pci -display sdl,gl=on

Best regards,
Tobias
Comment 1 Yann E. MORIN 2024-06-15 15:03:54 UTC
Thank you for your report.

The issue tracker for the Buildroot project has been moved to
the Gitlab.com issue tracker:
    https://gitlab.com/buildroot.org/buildroot/-/issues

We are taking this opportunity to close old issues in this old
tracker. If you believe your issue is still relevant, please
open one in the new issue tracker.

Thank you!