-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to build Milk-V Duo Image #133
Comments
使用 Docker 和直接构建都能观察到类似的问题,最后一段输出如下。
屏幕录像见 bugs |
问题出在 2c5bc4c |
所以现在问题解决了么? |
无进展 |
我们在 Ubuntu 20.04 和 Docker 中测试都没有问题,建议将 buildroot 下的 output 目录删除后重新编译试试,或者新建一个目录重新拉代码编译。 |
该问题似乎和 #49 类似。 检查 build/br.log 发现下列可疑内容
|
sc20ka
added a commit
to sc20ka/duo-buildroot-sdk
that referenced
this issue
Dec 9, 2024
…dbuf (milkv-duo#133) The build process was failing due to the current working directory being present in the LD_LIBRARY_PATH, which can lead to unpredictable behavior and errors. This commit addresses the issue in two ways: 1. Unsetting LD_LIBRARY_PATH: Before invoking , the environment variable is explicitly unset. This ensures that the build process uses system libraries from standard locations, preventing conflicts with potentially outdated or incorrect libraries in the current working directory. 2. Using stdbuf -oL with make: The original command was replaced with . This forces line buffering of the output from , ensuring that build logs are displayed correctly and in a timely manner. This change addresses potential issues with buffering that could lead to incomplete or delayed log output. These changes together resolve the build failures reported in milkv-duo#133 and improve the reliability and consistency of the build process.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build with build.sh
The text was updated successfully, but these errors were encountered: