| What | Removed | Added |
|---|---|---|
| Resolution | --- | NOTOURBUG |
| Status | NEW | RESOLVED |
Comment # 15
on bug 101977
from Marek Olšák
Interesting. So it's a UE4 bug after all. If UE4 didn't export its own libelf functions, it would work. When the driver is loaded, the dynamic linker loads libelf, but since UE4 exports the same function names as libelf does, libelf functions are not loaded at all and the functions from UE4 are exposed to the driver instead. The driver, thinking it's calling libelf, is actually invoking the UE4 functions of the same name. A temporary workaround is to load the system libelf first by doing: LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libelf.so ./UE4Editor It will have the opposite effect. UE4 will use system libelf instead of its own, because the symbols conflict and the system one is loaded first. This bug should be fixed in UE4 though. I'm closing this bug, because there is nothing Mesa can do here.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
