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
@ralphon Discord reports that glfw does not build on their Arch system because of a duplicate WL_MARSHAL_FLAG_DESTROY symbol definition. Our Linux CI pipelines are not facing the same.
From me:
there are two issues at play here, one is why do you get different results than our linux CI pipelines? My guess is something arch specific, but I don't know why/what.
The 2nd issue, which is more directly related to your problem, is likely that https://github.com/hexops/glfw/blob/master/build.zig#L135 is incorrect and should be removed. Presumably if you remove that line, then it will build on your system correctly - but will then begin failing on our linux CI pipelines.
My guess is the correct fix is to remove that line which will presumably break our CI pipelines and fix your issue, and then update https://github.com/hexops/wayland-headers/ (which presumably has the WL_MARSHAL_FLAG_DESTROY definition once updated) to fix our CI pipelines. Then your arch linux + the other linux systems are happy with it, is my guess.
The text was updated successfully, but these errors were encountered:
@ralph on Discord reports that glfw does not build on their Arch system because of a duplicate
WL_MARSHAL_FLAG_DESTROY
symbol definition. Our Linux CI pipelines are not facing the same.From me:
The text was updated successfully, but these errors were encountered: