unset RK_NETWORK_CHECK./build.sh # 或你原来的编译命令20260420给万象奥科的开发板HD-RK3576-PI适配瑞芯微原厂的Buildroot时解决网络异常Your network is not able to access sources.buildroot.net!2026/4/20 20:23缘起解决编译错误1、Running 95-extra-parts.sh for /home/rootroot/git_RK3576_Linux6.1/buildroot/output/rockchip_rk3576/target (buildroot initbusybox)...Preparing extra partitions...Running 97-ldcache.sh for /home/rootroot/git_RK3576_Linux6.1/buildroot/output/rockchip_rk3576/target (buildroot initbusybox)...Keep original /etc/ld.so.cacheRunning 99-owner.sh for /home/rootroot/git_RK3576_Linux6.1/buildroot/output/rockchip_rk3576/target (buildroot initbusybox)...Running mk-rootfs.sh - build_buildroot /home/rootroot/git_RK3576_Linux6.1/output/buildroot/images succeeded.Running mk-rootfs.sh - build_rootfs succeeded.Start building recovery(buildroot)Your network is not able to access sources.buildroot.net!Please retry later (it could be down for a while) or setup a VPN to bypass the GFW.Unset RK_NETWORK_CHECK in the SDK config to continue...ERROR: Running /home/rootroot/git_RK3576_Linux6.1/device/rockchip/common/scripts/mk-recovery.sh - build_hook failed!ERROR: exit code 1 from line 29:$RK_SCRIPTS_DIR/mk-buildroot.sh $RK_RECOVERY_CFG $IMAGE_DIRERROR: call stack:mk-recovery.sh: build_hook(29)mk-recovery.sh: main(51)ERROR: Running /home/rootroot/git_RK3576_Linux6.1/device/rockchip/common/build-hooks/99-all.sh - build_all failed!ERROR: exit code 1 from line 24:$RK_SCRIPTS_DIR/mk-recovery.shERROR: call stack:99-all.sh: build_all(24)99-all.sh: build_hook(136)build-helper: try_func(63)build-helper: try_hook(96)build-helper: source(165)99-all.sh: main(147)ERROR: Running /home/rootroot/git_RK3576_Linux6.1/device/rockchip/common/build-hooks/99-all.sh - try_func build_hook all failed!ERROR: exit code 1 from line 67:build_hookERROR: call stack:build-helper: try_func(67)build-helper: try_hook(96)build-helper: source(165)99-all.sh: main(147)rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$ unset RK_NETWORK_CHECKrootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$ ./build.shAllocating group tables: doneWriting inode tables: doneCreating journal (1024 blocks): doneCopying files into the device: doneWriting superblocks and filesystem accounting information: donetune2fs 1.47.0 (5-Feb-2023)Setting maximal mount count to -1Setting interval between checks to 0 secondsGenerated /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/oem.imgDone packing /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/oem.imgPreparing partiton userdataMerging /home/rootroot/git_RK3576_Linux6.1/device/rockchip/common/extra-parts/userdata/normal into /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdataPacking /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.img from /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.fsUsing host tools in /home/rootroot/git_RK3576_Linux6.1/buildroot/output/latest/host (except for mke2fs)Making /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.img from /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata (auto sized)Start from 8M for ext4.Making /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.img from /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata with size(8192KB)mke2fs 1.46.5 (30-Dec-2021)Creating regular file /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.imgCreating filesystem with 2048 4k blocks and 2048 inodesAllocating group tables: doneWriting inode tables: doneCreating journal (1024 blocks): doneCopying files into the device: doneWriting superblocks and filesystem accounting information: donetune2fs 1.47.0 (5-Feb-2023)Setting maximal mount count to -1Setting interval between checks to 0 secondsGenerated /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.imgDone packing /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.imgPacked /home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.img without having userdata partition!Running mk-extra-parts.sh - build_extra_part succeeded.Packed files:MiniLoaderAll.bin(/home/rootroot/git_RK3576_Linux6.1/u-boot/rk3576_spl_loader_v1.09.107.bin): 753Kboot.img(/home/rootroot/git_RK3576_Linux6.1/kernel-6.1/boot.img): 40Mmisc.img(/home/rootroot/git_RK3576_Linux6.1/output/misc.img): 48Koem.img(/home/rootroot/git_RK3576_Linux6.1/output/extra-parts/oem.img): 18Mparameter.txt(/home/rootroot/git_RK3576_Linux6.1/device/rockchip/.chips/rk3576/parameter.txt): 508recovery.img(/home/rootroot/git_RK3576_Linux6.1/output/recovery/ramboot.img): 49Mrootfs.img(/home/rootroot/git_RK3576_Linux6.1/buildroot/output/rockchip_rk3576/images/rootfs.ext2): 867Muboot.img(/home/rootroot/git_RK3576_Linux6.1/u-boot/uboot.img): 4.0Muserdata.img(/home/rootroot/git_RK3576_Linux6.1/output/extra-parts/userdata.img): 8.0MMaking update image...Start packing update imageGenerating package-file for update:# NAME PATHpackage-file package-fileparameter parameter.txtbootloader MiniLoaderAll.binuboot uboot.imgmisc misc.imgboot boot.imgrecovery recovery.imgbackup RESERVEDoem oem.imgrootfs rootfs.imgPacking /home/rootroot/git_RK3576_Linux6.1/output/firmware/update.img for update...Android Firmware Package Tool v2.29------ PACKAGE ------Add file: ./package-filepackage-file,Add file: ./package-file done,offset0x800,size0xcb,userspace0x1Add file: ./parameter.txtparameter,Add file: ./parameter.txt done,offset0x1000,size0x208,userspace0x1,flash_address0x00000000Add file: ./MiniLoaderAll.binbootloader,Add file: ./MiniLoaderAll.bin done,offset0x1800,size0xbc1f9,userspace0x179Add file: ./uboot.imguboot,Add file: ./uboot.img done,offset0xbe000,size0x400000,userspace0x800,flash_address0x00004000Add file: ./misc.imgmisc,Add file: ./misc.img done,offset0x4be000,size0xc000,userspace0x18,flash_address0x00006000Add file: ./boot.imgboot,Add file: ./boot.img done,offset0x4ca000,size0x27e9e00,userspace0x4fd4,flash_address0x00008000Add file: ./recovery.imgrecovery,Add file: ./recovery.img done,offset0x2cb4000,size0x30c2000,userspace0x6184,flash_address0x00028000Add file: ./oem.imgoem,Add file: ./oem.img done,offset0x5d76000,size0x11ef000,userspace0x23de,flash_address0x000f8000Add file: ./rootfs.imgrootfs,Add file: ./rootfs.img done,offset0x6f65000,size0x36300000,userspace0x6c600,flash_address0x00138000Add CRC...Make firmware OK!------ OK ------********rkImageMaker ver 2.29********Generating new image, please wait...Writing head info...Writing boot file...Writing firmware...Generating MD5 data...MD5 data generated successfully!New image generated successfully!Run make edit-package-file if you want to change the package-file.Running mk-updateimg.sh - build_updateimg succeeded.Images under /home/rootroot/git_RK3576_Linux6.1/output/firmware/ are ready!Running mk-firmware.sh - build_firmware succeeded.Running 99-all.sh - build_all succeeded.rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$ ./build.sh2、问DeepSeekRK3576的buildroot编译错误Running 95-extra-parts.sh for /home/rootroot/git_RK3576_Linux6.1/buildroot/output/rockchip_rk3576/target (buildroot initbusybox)...Preparing extra partitions...Running 97-ldcache.sh for /home/rootroot/git_RK3576_Linux6.1/buildroot/output/rockchip_rk3576/target (buildroot initbusybox)...Keep original /etc/ld.so.cacheRunning 99-owner.sh for /home/rootroot/git_RK3576_Linux6.1/buildroot/output/rockchip_rk3576/target (buildroot initbusybox)...Running mk-rootfs.sh - build_buildroot /home/rootroot/git_RK3576_Linux6.1/output/buildroot/images succeeded.Running mk-rootfs.sh - build_rootfs succeeded.Start building recovery(buildroot)Your network is not able to access sources.buildroot.net!Please retry later (it could be down for a while) or setup a VPN to bypass the GFW.Unset RK_NETWORK_CHECK in the SDK config to continue...ERROR: Running /home/rootroot/git_RK3576_Linux6.1/device/rockchip/common/scripts/mk-recovery.sh - build_hook failed!ERROR: exit code 1 from line 29:$RK_SCRIPTS_DIR/mk-buildroot.sh $RK_RECOVERY_CFG $IMAGE_DIRERROR: call stack:mk-recovery.sh: build_hook(29)mk-recovery.sh: main(51)ERROR: Running /home/rootroot/git_RK3576_Linux6.1/device/rockchip/common/build-hooks/99-all.sh - build_all failed!ERROR: exit code 1 from line 24:$RK_SCRIPTS_DIR/mk-recovery.shERROR: call stack:99-all.sh: build_all(24)99-all.sh: build_hook(136)build-helper: try_func(63)build-helper: try_hook(96)build-helper: source(165)99-all.sh: main(147)ERROR: Running /home/rootroot/git_RK3576_Linux6.1/device/rockchip/common/build-hooks/99-all.sh - try_func build_hook all failed!ERROR: exit code 1 from line 67:build_hookERROR: call stack:build-helper: try_func(67)build-helper: try_hook(96)build-helper: source(165)99-all.sh: main(147)rootrootrootroot-HP-245-14-inch-G10-Notebook-PC:~/git_RK3576_Linux6.1$用户遇到了Rockchip RK3576的Buildroot编译错误错误信息显示网络无法访问 sources.buildroot.net导致构建失败。用户可能想知道如何解决这个问题。为了全面获取信息我们需要同时进行多项搜索涵盖不同的关键词和可能的解决方案。搜索到 53 个网页搜索结果显示了一些相关的页面。为了全面了解问题并找到解决方案我们需要同时打开这些页面。浏览 6 个页面Lyra Ubuntu SDKLuckfox-Lyra SDK system building issue with buildroot downloadingLuckfox ForumsLuckfox Forums初次编译rk3568rk3576Linux 6.1内核踩坑记录从报错终止到成功解决的完整流程查看全部这些搜索结果显示了与用户相同的问题。有几个相关的页面一个来自 Luckfox 论坛的帖子提到了同样的错误并提供了一个绕过网络检查的解决方法。另一个结果提供了关于修改 check-network.sh 脚本的详细信息。还有一个结果提到了使用预下载的 dl.tar.gz 包来避免网络问题。另外还有一个结果提供了一般的编译问题排查步骤。为了全面了解这些解决方案我们需要同时打开这些相关的页面。浏览 2 个页面Luckfox-Lyra SDK system building issue with buildroot downloading初次编译rk3568rk3576Linux 6.1内核踩坑记录从报错终止到成功解决的完整流程搜索结果中提供了几种解决方案。我的回答将涵盖快速绕过检查、替换Buildroot源码包、使用完整源码包、以及通用网络排查方法。回答会以中文呈现并引用相关来源。从你提供的日志来看编译失败的核心原因是网络连接问题。buildroot 在编译时需要从 sources.buildroot.net 下载一些依赖包但由于网络限制你的环境无法访问这个地址最终导致 recovery 分区的构建过程失败。下面是几种解决方法。? 快速绕过禁用 SDK 网络检查这是最快的方法。根据日志中的提示可以通过禁用 SDK 的网络检查来跳过这个步骤。操作方法在 SDK 的配置文件中取消设置 RK_NETWORK_CHECK。根据 Luckfox 社区的经验你也可以在检查网络状态的脚本 check-network.sh 中直接让它返回 0表示成功来绕过检查。?? 离线构建手动替换 Buildroot 源码包如果跳过检查后仍因网络问题导致下载失败可以提前准备所有必需的源码包。操作方法在其他网络畅通的环境中从 sources.buildroot.net 下载所有必要的软件包即 .tar.gz 等文件然后拷贝到你 SDK 中的 buildroot/dl/ 目录下。这样buildroot 在构建时就会直接使用这些本地文件无需联网下载。?? 终极方案使用完整的 SDK 源码包一些 Rockchip 的开发板厂商会提供预下载了所有依赖项的完整 SDK 压缩包。操作方法检查你的产品资料中是否有 dl.tar.gz 这样的文件。这个压缩包存放了 Buildroot 编译所需的各种开源软件包。如果有请将它解压到 SDK 的 buildroot/ 目录下即可。?? 通用网络排查方法如果上述方案都不适用可以检查一下基础的网络配置检查防火墙/代理确保防火墙、VPN 或代理没有屏蔽对 sources.buildroot.net 的访问。手动测试访问在终端中使用 curl -I http://sources.buildroot.net 命令测试是否能正常访问。更换 DNS 服务器尝试将系统的 DNS 服务器改为公共 DNS如 8.8.8.8 或 114.114.114.114。?? 总结与建议简单总结一下解决这个问题的思路可以按照以下顺序尝试首选在 SDK 配置中取消 RK_NETWORK_CHECK 的设置这是最快的解决办法。备选如果 SDK 本身提供了 dl.tar.gz 离线包直接使用它是最彻底的。手动方案从 sources.buildroot.net 手动下载缺少的源码包并放入 buildroot/dl/ 目录。最后检查确认你的网络环境没有限制能正常访问外网资源。希望这些步骤能帮助你顺利解决编译问题。如果还有其他疑问随时可以继续交流。本回答由 AI 生成内容仅供参考请仔细甄别。请问如何使用unset跳过网络监察我们被问到“请问如何使用unset跳过网络监察”。根据之前的对话用户遇到了RK3576 buildroot编译错误原因是网络无法访问sources.buildroot.net日志中提示“Unset RK_NETWORK_CHECK in the SDK config to continue...”。用户现在问如何使用unset跳过网络监察。需要解释在SDK配置中如何取消设置RK_NETWORK_CHECK变量。可能的方法在命令行中unset环境变量或者修改配置文件。需要具体说明。注意用户使用的环境是Rockchip Linux SDK路径为/home/rootroot/git_RK3576_Linux6.1/。通常SDK有一个配置文件或者可以通过脚本设置环境变量。回答应提供步骤找到设置RK_NETWORK_CHECK的地方可能在device/rockchip/.BoardConfig.mk或sdk的config脚本然后取消定义。或者直接在命令行执行unset RK_NETWORK_CHECK再运行编译。或者修改脚本使其不检查。提供清晰的操作指南。要跳过 RK_NETWORK_CHECK 的网络检查核心思路是确保该环境变量没有被设置即值为空或者让检查脚本直接返回成功。下面是几种具体的操作方法你可以根据自己的需求选择。方法一在命令行中临时 unset最简单每次编译前在终端中执行 unset RK_NETWORK_CHECK然后继续运行编译命令。例如bashunset RK_NETWORK_CHECK./build.sh # 或你原来的编译命令注意这个方法只对当前终端会话有效如果你关闭终端或打开新终端需要重新执行 unset。方法二修改 SDK 的配置文件永久生效Rockchip SDK 通常会在 device/rockchip/.BoardConfig.mk 或 device/rockchip/rk3576/BoardConfig.mk 中定义 RK_NETWORK_CHECK。你可以找到并注释或删除该行。进入 SDK 根目录bashcd /home/rootroot/git_RK3576_Linux6.1查找定义 RK_NETWORK_CHECK 的文件bashgrep -r RK_NETWORK_CHECK device/rockchip/编辑对应的配置文件例如 BoardConfig.mk将类似下面的行makefileexport RK_NETWORK_CHECK : true改为makefile# export RK_NETWORK_CHECK : true # 注释掉或者直接赋值为空makefileexport RK_NETWORK_CHECK :重新加载配置通常执行 source build/envsetup.sh 或重新打开终端。方法三修改网络检查脚本让它总是返回成功SDK 中通常会有一个脚本用于检查网络比如 device/rockchip/common/scripts/check-network.sh。你可以修改它在脚本开头直接返回 0bash# 在 check-network.sh 的第一行shebang 之后添加return 0 # 或者 exit 0注意这种做法会完全跳过所有网络检查如果你后续需要联网下载其他组件可能会遇到隐藏的问题。建议仅作为临时方案。方法四使用环境变量覆盖适用于 Buildroot 独立编译如果你直接调用 Buildroot 的 make 命令不通过 SDK 的封装脚本可以在命令行中临时设置变量为空bashRK_NETWORK_CHECK make注意等号后面不要写任何值这样变量会被赋值为空字符串效果等同于未设置。验证是否已跳过检查执行上述任一方法后重新运行编译命令。如果不再出现类似 Your network is not able to access sources.buildroot.net 的错误说明已成功跳过。如果仍然报错可以尝试在编译命令前加上 set -x 来查看脚本执行过程定位具体是哪里还在检查。补充说明为什么不直接删除检查RK_NETWORK_CHECK 是 Rockchip SDK 用来防止因网络问题导致编译失败的辅助功能。跳过它后如果 Buildroot 在后续步骤中确实需要联网下载源码包而你的网络仍然不通编译仍会失败。那时你就需要采用离线包方案将提前下载好的源码包放入 buildroot/dl/。推荐做法先使用方法一或二跳过检查如果编译过程中因下载源码包失败再参考我上一次回答中的“离线构建”方法。如果还有不清楚的地方欢迎继续提问。