You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, while compiling amdvlk from source for the Void-Linux distribution, the maintainers (thank you Johnnynator on the Void repo for your precious help !) noticed a small issue while compiling with musl-libc.
In the file pal/src/core/hw/gfxip/gfx9/gfx9UniversalCmdBuffer.cpp:
at lines 10155 and 10167, the usage of NULL, makes an error as it's interpreted as std::nullptr_t instead of a long unsigned integer as usually expected.
The GlibC compiler seems kinda tolerant to this, as the compiling process goes through without issue.
however Musl stops right through.
According to Johnny's help and my tests, replacing NULL, by 0UL, in both places, seems to fix the issue.
Just in case, we both also made a git patch for our Voidlinux compiler, it will be linked to this issue, for convenience.
Hello, while compiling amdvlk from source for the Void-Linux distribution, the maintainers (thank you Johnnynator on the Void repo for your precious help !) noticed a small issue while compiling with musl-libc.
In the file
pal/src/core/hw/gfxip/gfx9/gfx9UniversalCmdBuffer.cpp
:at lines
10155
and10167
, the usage ofNULL,
makes an error as it's interpreted asstd::nullptr_t
instead of along unsigned integer
as usually expected.The GlibC compiler seems kinda tolerant to this, as the compiling process goes through without issue.
however Musl stops right through.
According to Johnny's help and my tests, replacing
NULL,
by0UL,
in both places, seems to fix the issue.Just in case, we both also made a git patch for our Voidlinux compiler, it will be linked to this issue, for convenience.
amdvlk-fix-musl-build.patch
Best regards - SpidFightFR
The text was updated successfully, but these errors were encountered: