-
Notifications
You must be signed in to change notification settings - Fork 22
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
a repository not exist, and file on sources.buildroot.net not exist #2
Comments
How about using this repository, https://github.com/radxa/device-custom.git? |
ok- I updated the readme. You should checkout the buildroot repo commit as mentioned :
If that doesn't fix your problem, plese write all of the commands from begginning to end which you used to build. |
Here are my commands GIT_DIR=/home/hit/rock-3a/buildroot.dl/uboot/git/.git git remote add origin 'https://github.com/radxa/u-boot.git' |
How long does make rkbin take to run ? If you look in the config file this is how uboot is defined :
Buildroot should be fetching uboot from that URL, not sources.buildroot.net. Have you setup the downloads directory, perhaps that is the problem ? |
Can you please start a new thread somewhere else for this device-custom.git ? |
Closing this issue due to cross polination with an unrealted "device-custom" repo discussion. |
I try to build on radxa rock 3a, but failed.
I followed the instructions, in the step "Now build buildroot as per usual", can't finish make.
problem 1:
remote: Repository not found.
fatal: 仓库 'https://github.com/rockchip-linux/device-custom.git/' 未找到
...
This is the second time in a row; bailing out
problem 2:
--2022-02-27 19:54:59-- http://sources.buildroot.net/rkdevice-0fe366cf14a6d5d552a5bddbc7b8ff58260ae6e6-br1.tar.gz
正在解析主机 sources.buildroot.net (sources.buildroot.net)... 104.26.1.37, 104.26.0.37, 172.67.72.56, ...
正在连接 sources.buildroot.net (sources.buildroot.net)|104.26.1.37|:80... 已连接。
已发出 HTTP 请求,正在等待回应... 404 Not Found
It seems that that repository and that file don't exist. How can I fix this problem?
The text was updated successfully, but these errors were encountered: