ohos报错记录20220818

这篇博客记录了在Linux环境下开发HarmonyOS过程中遇到的错误及解决过程,涉及操作系统层面和HarmonyOS系统的运维问题。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

root@936e90e41325:/home/openharmony# hb build -f
[OHOS INFO] ohos_build_compiler: clang
[OHOS INFO] //prebuilts/lite/sysroot/build:build_sysroot is marked as prebuilts
[OHOS INFO] //kernel/linux/build:linux_kernel is marked as prebuilts
[OHOS INFO] Done. Made 12 targets from 16 files in 12ms
[OHOS INFO] [1/17] STAMP obj/build/lite/mark_as_prebuilts.stamp
[OHOS INFO] [2/17] STAMP obj/device/xiangyang/imx6ul_nand_linux/imx6ul_nand_linux.stamp
[OHOS INFO] [3/17] STAMP obj/build/lite/ndk.stamp
[OHOS INFO] [4/17] STAMP obj/vendor/xiangyang/imx6ul_nand_linux/imx6ul_nand_linux.stamp
[OHOS INFO] [5/17] STAMP obj/build/lite/ohos.stamp
[OHOS INFO] [6/17] STAMP obj/build/lite/product.stamp
[OHOS INFO] [7/17] ACTION //kernel/linux/build:linux_kernel(//build/lite/toolchain:linux_x86_64_ohos_clang)
[OHOS ERROR] [7/17] ACTION //kernel/linux/build:linux_kernel(//build/lite/toolchain:linux_x86_64_ohos_clang)
[OHOS ERROR] FAILED: obj/kernel/linux/build/linux_kernel_build_ext_components.txt 
[OHOS ERROR] /usr/bin/python3 ../../../build/lite/build_ext_components.py --path=../../../kernel/linux/build --command=./kernel_module_build.sh\ /home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony\ small\ /home/openharmony/prebuilts/clang/ohos/linux-x86_64/llvm\ vendor/xiangyang/imx6ul_nand_linux\ imx6ul_nand_linux\ linux-5.4 --target_dir=/home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/obj/kernel/linux/build/build.log --out_dir=/home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/error.log
[OHOS ERROR] echo "build kernel..."
[OHOS ERROR] build kernel...
[OHOS ERROR] rm -rf /home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/kernel/linux-5.4;mkdir -p /home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/kernel/linux-5.4;cp -arfL /home/openharmony/kernel/linux/linux-5.4/* /home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/kernel/linux-5.4/
[OHOS ERROR] cd /home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/kernel/linux-5.4 && patch -p1 < /home/openharmony/kernel/linux/patches/linux-5.4/imx6ul_nand_linux_patch/hdf.patch && patch -p1 < /home/openharmony/kernel/linux/patches/linux-5.4/imx6ul_nand_linux_patch/imx6ul_nand_linux.patch
[OHOS ERROR] patching file arch/arm/kernel/vmlinux.lds.S
[OHOS ERROR] Hunk #1 FAILED at 121.
[OHOS ERROR] 1 out of 1 hunk FAILED -- saving rejects to file arch/arm/kernel/vmlinux.lds.S.rej
[OHOS ERROR] patching file drivers/Kconfig
[OHOS ERROR] Hunk #1 FAILED at 235.
[OHOS ERROR] 1 out of 1 hunk FAILED -- saving rejects to file drivers/Kconfig.rej
[OHOS ERROR] patching file drivers/Makefile
[OHOS ERROR] Hunk #1 FAILED at 189.
[OHOS ERROR] 1 out of 1 hunk FAILED -- saving rejects to file drivers/Makefile.rej
[OHOS ERROR] patching file drivers/hdf/Makefile
[OHOS ERROR] patching symbolic link drivers/hdf/framework
[OHOS ERROR] patching symbolic link drivers/hdf/khdf
[OHOS ERROR] patching symbolic link include/hdf
[OHOS ERROR] kernel.mk:73: recipe for target '/home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/kernel/linux-5.4/arch/arm/boot/uImage' failed
[OHOS ERROR] make: *** [/home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/kernel/linux-5.4/arch/arm/boot/uImage] Error 1
[OHOS ERROR] you can check build log in /home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony/build.log
[OHOS ERROR] command: "/home/openharmony/prebuilts/build-tools/linux-x86/bin/ninja -w dupbuild=warn -C /home/openharmony/out/imx6ul_nand_linux/imx6ul_nand_openharmony" failed
[OHOS ERROR] return code: 1
[OHOS ERROR] execution path: /home/openharmony
root@936e
### OHOS开发环境中的常见问题分析 在OHOS开发过程中遇到`OHOSException: Failed to init compile config`错误代码0019,通常表明编译配置初始化失败。此问题可能由多种原因引起,例如环境变量未正确设置、必要工具缺失或版本不兼容等问题。 以下是针对该问题的具体解决方案: #### 1. **确认hb工具安装** 如果提示`hb set`命令未找到,则说明HB工具尚未正确安装或路径未被加入到系统的PATH环境变量中。可以通过以下方法验证并解决问题: - 验证HB工具是否存在: 运行以下命令检查是否能找到`hb`可执行文件。 ```bash which hb ``` 如果返回为空,则需重新安装HB工具[^2]。 - 安装HB工具: 参考官方文档下载对应平台的HB工具包,并解压至指定目录。随后将其路径添加到系统环境变量中。 ```bash export PATH=$PATH:/path/to/hb/tool/directory ``` #### 2. **检查build/envsetup.sh文件存在性** 当提示`build/envsetup.sh`文件不存在时,可能是源码克隆过程出现问题或者本地工作区损坏所致。可以尝试如下操作修复: - 确认仓库完整性: 使用Git检出最新代码分支,确保所有必要的子模块均已拉取完成。 ```bash git submodule update --init --recursive ``` - 手动创建envsetup.sh脚本(仅作为临时措施): 若确实缺少该文件,可以从其他正常的工作空间复制一份过来;或者依据官方模板手动编写基础内容。 ```bash touch build/envsetup.sh && chmod +x build/envsetup.sh echo "#!/bin/bash" >> build/envsetup.sh ``` #### 3. **更新依赖项与Git版本** 类似于引用描述的情况,较低版本的Git可能导致某些功能不可用从而引发异常。建议升级至推荐版本范围内的Git软件以规避潜在风险。 - 升级Git版本: 对于Ubuntu系统而言,利用预置脚本简化流程即可实现快速迁移。 ```bash sudo apt-get install software-properties-common sudo add-apt-repository ppa:git-core/ppa sudo apt-get update sudo apt-get install git ``` #### 4. **清理缓存重试构建** 有时残留的数据也可能干扰新项目的初次搭建成功与否。因此有必要先清除旧有记录再继续下一步骤动作。 - 清理现有项目状态: 删除`.repo`隐藏目录以及其他中间产物后再发起全新同步请求。 ```bash rm -rf .repo out repo sync source build/envsetup.sh lunch ohos-wear # 或者选择适合的目标设备型号组合 make -j$(nproc) ``` 通过以上调整应该能够有效缓解乃至彻底消除所列报错现象的发生几率。 ```python print("Environment setup completed successfully.") ```
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值