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
This happens because the xemu-version.sh macro is failing to fill the XEMU_VERSION variables. (filling them manually allows the build to succeed)
I am already using the latest container image, and this happens even on a freshly cloned repository.
It worked for me in mid December, and the aforementioned macro has not been changed in the meantime, so it could be either an issue on my system or a problem with the Docker image. (other users on Discord are reporting the same issue when using the Docker image, while it's working on GitHub agents)
Expected Behavior
The build should succeed.
xemu Version
0.8.31.0
Last working for me in: 0.7.132.123 (mid December 2024)
System Information
OS: Ubuntu 24.04, running on Windows 11 via VirtualBox (although the same issue has been reported also on WSL)
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
When building for Windows using the Docker image (as described here) the build fails with the following error:
This happens because the xemu-version.sh macro is failing to fill the XEMU_VERSION variables. (filling them manually allows the build to succeed)
I am already using the latest container image, and this happens even on a freshly cloned repository.
It worked for me in mid December, and the aforementioned macro has not been changed in the meantime, so it could be either an issue on my system or a problem with the Docker image. (other users on Discord are reporting the same issue when using the Docker image, while it's working on GitHub agents)
Expected Behavior
The build should succeed.
xemu Version
0.8.31.0
Last working for me in: 0.7.132.123 (mid December 2024)
System Information
OS: Ubuntu 24.04, running on Windows 11 via VirtualBox (although the same issue has been reported also on WSL)
Additional Context
No response
The text was updated successfully, but these errors were encountered: