解决Linux下编译.sh文件报错 “[: unexpected operator”

最新推荐文章于 2024-04-29 11:05:19 发布
转载 最新推荐文章于 2024-04-29 11:05:19 发布 · 6.9k 阅读 · 8 ·
CC 4.0 BY-SA版权
原文链接：https://www.linuxidc.com/Linux/2014-11/110010.htm

本文介绍了解决在Linux环境下使用.sh文件编译工程时遇到的错误问题，详细解释了Ubuntu默认使用dash而非bash作为解释器导致的问题，并提供了解决方案，包括将.sh文件的解释器更改为bash的方法。

问题:

在Linux通过编译 .sh文件来生成工程，提示报错：
在这里插入图片描述
然后我就表示很费解，查看我的.sh文件，其中有很多的[] ，都是这些报错，可是之前一直没问题。

后来发现，因为Ubuntu默认的sh是连接到dash的,又因为dash跟bash的不兼容所以出错了.执行时可以把sh换成bash文件名.sh来执行.成功.dash是什么东西,查了一下,应该也是一种shell,貌似用户对它的诟病颇多。

修改sh默认连接到bash的一种方法：

sudo dpkg-reconfigure dash

选择no 即可！

再次编译！通过！搞定！

Linux Shell脚本 [ unexpected operator错误处理
SHELLCODE_8BIT的博客
06-20 4250
shell脚本[]中报unexpected operator，原因是使用了dash来做脚本解析，dash
【工程实践】shell文件报错 “[: XXXX: unexpected operator”
Dong_ZH的博客
01-13 1013
执行文件名为 train.sh 的linux shell 脚本时出现[: xxxx: unexpected operator的错误。
Linux: unexpected operator
weixin_42630613的博客
11-24 1267
文章目录1、保存设置 1、保存设置 def zipdir(path, ziph): files = os.listdir(path) for file in files: if file.endswith(".py") or file.endswith("cfg"): ziph.write(os.path.join(path, file)) if file.endswith("cfg"): os.
[: xxxx: Unexpected operator
weixin_33979745的博客
02-07 302
/*************************************************************************** * [: xxxx: Unexpected operator * 说明： * 在修改shell脚本的时候遇到这个问题，记录一下解决方法。 * * ...
shell 脚本执行报错 unexpected operator
Levon123的博客
05-20 4996
unexpected operator:意外的运算符 出现这个问题，可以先使用以下步骤排查问题： （1） 检查语法是否正确+编码是否正确（使用utf8编码，不能是utf8-bom编码）； （2）确认shell脚本中使用的是#!/bin/bash还是#!/bin/sh，如果是#!/bin/sh修改替换为#!/bin/bash试试 ...
Shell 判断语句出错 [: ==: unexpected operator
程序员「阿基米东」的编程之旅
05-28 5886
有时候，原来运行得好好的 shell 程序，换个平台就运行不了，例如下面 shell 程序。 #!/bin/sh if [ $1 == "hello" ]; then echo "Well done!" fi 在 Ubuntu 上运行，会出现如下的错误： [: ==: unexpected operator 这是因为 shell 脚本开头使用 #!/bin/sh，而不是 #!/bin/bash。而 /bin/sh 使用的是 dash，dash 中默认的判断语句是 =，而不是 bash 使用的
学习鸟哥Linux shell 时遇到的unexpected operator错误
林龙
10-30 1443
但Login Shell（一开始通过字符界面登入系统，不是通过x window界面打开terminal终端的shell）还是bash. 原因是dash更快、更高效，而且它符合POSIX规范。而Bash(GNU Bourne-Again Shell)是大多数Linux平台的内定Shell，也是更经典的shell工具。执行命令会产生一个界面，英文大概意思为：是否使用dash作为默认的系统shell工具，我们选择“No”执行完，再执行命令：ll /bin/sh，发现已经替换为bash了。
报错 source /opt/ros/melodic/setup.bash -bash: /tmp/setup.sh.ccK1AU9hn5: line 38: unexpected EOF while looking for matching `"' -bash: /tmp/setup.sh.ccK1AU9hn5: line 39: syntax error: unexpected end of file -bash: [: 0: unary operator expected
最新发布
12-13
`setup.bash`脚本会调用其他脚本，比如`/opt/ros/melodic/setup.sh`，以及`/etc/catkin/profile.d`目录下的脚本。检查这些脚本中是否有语法错误。 #### 步骤6: 手动执行脚本并跟踪 为了定位问题，我们可以尝试手动...
prepare configs of er7206_un_v2 model. cp -rf tplink/configs/er7206_un_v2/er7206_un_v2.config ./.config cp -rf tplink/configs/er7206_un_v2/er7206_un_v2.kernel.config target/linux/generic/config-5.4 cp -f tplink/configs/er7206_un_v2/resources/mt7981-spim-nand-rfb.dts target/linux/mediatek/files-5.4/arch/arm64/boot/dts/mediatek/ cp -rf tplink/configs/er7206_un_v2/kernel_patches/* target/linux/mediatek/patches-5.4/ mkdir -p /home/huhcen/omada_gateway/staging_dir/host/bin cp -rf tplink/configs/er7206_un_v2/resources/fwtool /home/huhcen/omada_gateway/staging_dir/host/bin/ ./tplink/beta/patch_beta.sh ./tplink/beta/patch_beta.sh: 2: [: unexpected operator ./tplink/beta/patch_beta.sh: 7: [: unexpected operator error: pathspec './src/styles/origin/old/style.less' did not match any file(s) known to git. product.mk:130: recipe for target 'er7206_un_v2_config' failed make: *** [er7206_un_v2_config] Error 1
10-17
- **检查文件编码和换行符**：确保脚本文件是使用Unix/Linux风格的换行符（LF），而不是Windows风格的换行符（CRLF）。可以使用`dos2unix`工具将文件转换为Unix格式： ```bash dos2unix ./tplink/beta/patch_beta.sh...
bash: groups: command not found /usr/bin/lesspipe: 1: /usr/bin/lesspipe: basename: not found /usr/bin/lesspipe: 295: [: =: unexpected operator root@FriendlyELEC:~# cd /home/app_test/2_test/ root@FriendlyELEC:/home/app_test/2_test# ls ledbaseapp ledbase.ko root@FriendlyELEC:/home/app_test/2_test# insmod ledbase.ko insmod: ERROR: could not insert module ledbase.ko: Bad address
06-23
#### 三、`lesspipe: unexpected operator` 错误 该错误通常由 **Shell 解释器不兼容**或**脚本损坏**引起： 1. **检查脚本解释器** ```bash head -n1 $(which lesspipe) # 查看首行shebang ``` 2. **修复方法...
ohos_build_compiler: gcc ERROR at //vendor/bossay/LED/BUILD.gn:4:64: Unexpected token ',' "//device/bossay/hi3861_l0/sdk_liteos:wifiiot_sdk"], ^ hks_config_lite.h
05-29
好的，我现在需要解决用户提出的在OHOS编译过程中遇到的“Unexpectedtoken ','”错误，具体涉及BUILD.gn语法错误和hks_config_lite.h文件的问题。首先，我要理清用户的问题场景，可能的原因以及对应的解决方案。 ...
这个是什么原因 administrator@administrator-pc:~/BHD-713/irdma-1.2.21$ sudo ./build.sh 输入密码 ./build.sh: 15: [: unexpected operator make: 进入目录“/usr/src/linux-headers-5.10.0-9-generic” make: 离开目录“/usr/src/linux-headers-5.10.0-9-generic” ./build.sh: 98: [: unexpected operator make: 进入目录“/usr/src/linux-headers-5.10.0-9-generic” CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/hw.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/cm.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/ctrl.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/hmc.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/pble.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/puda.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/uk.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/utils.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/uda.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/ws.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/trace.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/i40iw_if.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/i40iw_hw.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/irdma_if.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/icrdma_hw.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/configfs.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/virtchnl.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/irdma_kcompat.o CC [M] /home/administrator/BHD-713/irdma-1.2.21/src/irdma/debugfs.o /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.c:580:15: error: initialization of ‘int (*)(struct devlink *, enum devlink_reload_action, enum devlink_reload_limit, u32 *, struct netlink_ext_ack *)’ {aka ‘int (*)(struct devlink *, enum devlink_reload_action, enum devlink_reload_limit, unsigned int *, struct netlink_ext_ack *)’} from incompatible pointer type ‘int (*)(struct devlink *, struct netlink_ext_ack *)’ [-Werror=incompatible-pointer-types] 580 | .reload_up = irdma_devlink_reload_up, | ^~~~~~~~~~~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.c:580:15: note: (near initialization for ‘irdma_devlink_ops.reload_up’) /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.c:581:17: error: initialization of ‘int (*)(struct devlink *, bool, enum devlink_reload_action, enum devlink_reload_limit, struct netlink_ext_ack *)’ {aka ‘int (*)(struct devlink *, _Bool, enum devlink_reload_action, enum devlink_reload_limit, struct netlink_ext_ack *)’} from incompatible pointer type ‘int (*)(struct devlink *, bool, struct netlink_ext_ack *)’ {aka ‘int (*)(struct devlink *, _Bool, struct netlink_ext_ack *)’} [-Werror=incompatible-pointer-types] 581 | .reload_down = irdma_devlink_reload_down, | ^~~~~~~~~~~~~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.c:581:17: note: (near initialization for ‘irdma_devlink_ops.reload_down’) /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c: In function ‘irdma_query_port’: /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:112:46: error: passing argument 2 of ‘irdma_get_eth_speed_and_width’ from incompatible pointer type [-Werror=incompatible-pointer-types] 112 | irdma_get_eth_speed_and_width(SPEED_100000, &props->active_speed, | ^~~~~~~~~~~~~~~~~~~~ | | | u16 * {aka short unsigned int *} /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:61:63: note: expected ‘u8 *’ {aka ‘unsigned char *’} but argument is of type ‘u16 *’ {aka ‘short unsigned int *’} 61 | static void irdma_get_eth_speed_and_width(u32 link_speed, u8 *active_speed, | ~~~~^~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c: In function ‘irdma_reg_user_mr’: /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:2846:23: error: passing argument 1 of ‘ib_umem_get’ from incompatible pointer type [-Werror=incompatible-pointer-types] 2846 | region = ib_umem_get(udata, start, len, access); | ^~~~~ | | | struct ib_udata * In file included from /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.h:35, from /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:3: ./include/rdma/ib_umem.h:74:17: note: expected ‘struct ib_device *’ but argument is of type ‘struct ib_udata *’ 74 | struct ib_umem *ib_umem_get(struct ib_device *device, unsigned long addr, | ^~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c: At top level: /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4310:14: error: initialization of ‘int (*)(struct ib_mw *, struct ib_udata *)’ from incompatible pointer type ‘struct ib_mw * (*)(struct ib_pd *, enum ib_mw_type, struct ib_udata *)’ [-Werror=incompatible-pointer-types] 4310 | .alloc_mw = irdma_alloc_mw, | ^~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4310:14: note: (near initialization for ‘irdma_dev_ops.alloc_mw’) /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4313:15: error: initialization of ‘int (*)(struct ib_ah *, struct rdma_ah_init_attr *, struct ib_udata *)’ from incompatible pointer type ‘int (*)(struct ib_ah *, struct rdma_ah_attr *, u32, struct ib_udata *)’ {aka ‘int (*)(struct ib_ah *, struct rdma_ah_attr *, unsigned int, struct ib_udata *)’} [-Werror=incompatible-pointer-types] 4313 | .create_ah = irdma_create_ah, | ^~~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4313:15: note: (near initialization for ‘irdma_dev_ops.create_ah’) /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4320:16: error: initialization of ‘int (*)(struct ib_pd *, struct ib_udata *)’ from incompatible pointer type ‘void (*)(struct ib_pd *, struct ib_udata *)’ [-Werror=incompatible-pointer-types] 4320 | .dealloc_pd = irdma_dealloc_pd, | ^~~~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4320:16: note: (near initialization for ‘irdma_dev_ops.dealloc_pd’) /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4323:16: error: initialization of ‘int (*)(struct ib_ah *, u32)’ {aka ‘int (*)(struct ib_ah *, unsigned int)’} from incompatible pointer type ‘void (*)(struct ib_ah *, u32)’ {aka ‘void (*)(struct ib_ah *, unsigned int)’} [-Werror=incompatible-pointer-types] 4323 | .destroy_ah = irdma_destroy_ah, | ^~~~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4323:16: note: (near initialization for ‘irdma_dev_ops.destroy_ah’) /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4324:16: error: initialization of ‘int (*)(struct ib_cq *, struct ib_udata *)’ from incompatible pointer type ‘void (*)(struct ib_cq *, struct ib_udata *)’ [-Werror=incompatible-pointer-types] 4324 | .destroy_cq = irdma_destroy_cq, | ^~~~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4324:16: note: (near initialization for ‘irdma_dev_ops.destroy_cq’) In file included from /home/administrator/BHD-713/irdma-1.2.21/src/irdma/irdma_kcompat.h:66, from /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.h:46, from /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:3: /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c: In function ‘irdma_ib_register_device’: /home/administrator/BHD-713/irdma-1.2.21/src/irdma/ubuntu_kcompat.h:36:45: error: too few arguments to function ‘ib_register_device’ 36 | #define kc_ib_register_device(device, name) ib_register_device(device, name) | ^~~~~~~~~~~~~~~~~~ /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:4632:8: note: in expansion of macro ‘kc_ib_register_device’ 4632 | ret = kc_ib_register_device(&iwdev->ibdev, name); | ^~~~~~~~~~~~~~~~~~~~~ In file included from ./include/rdma/ib_mad.h:15, from ./include/rdma/ib_smi.h:13, from /home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.h:29, from /home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.c:3: ./include/rdma/ib_verbs.h:2785:5: note: declared here 2785 | int ib_register_device(struct ib_device *device, const char *name, | ^~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors make[1]: *** [scripts/Makefile.build:286：/home/administrator/BHD-713/irdma-1.2.21/src/irdma/verbs.o] 错误 1 make[1]: *** 正在等待未完成的任务.... cc1: all warnings being treated as errors make[1]: *** [scripts/Makefile.build:286：/home/administrator/BHD-713/irdma-1.2.21/src/irdma/main.o] 错误 1 make: *** [Makefile:1848：/home/administrator/BHD-713/irdma-1.2.21/src/irdma] 错误 2 make: 离开目录“/usr/src/linux-headers-5.10.0-9-generic”
05-25
下载对应分支标签下的 tarball 文件重新安装即可消除此类冲突现象[^5]。 #### 方法三：降级内核版本 作为临时措施，可以选择回退到较低版本的内核环境中执行相同操作流程。不过需要注意的是这种方法可能会带来安全...
shell 脚本执行失败：[: unexpected operator
qq_48391148的博客
04-29 672
ubuntu 默认 sh 默认是软链接到 /usr/bin/dash 而不是bash。当sh 执行脚本的时候一直有这个报错，但是语法没问题，查资料发现。使用bash 执行脚本。
解决Linux下编译.sh文件报错 “[: XXXX: unexpected operator”
weixin_33834679的博客
04-13 482
本人经常在Linux通过编译 .sh文件来生成工程，之前一直都没问题，代码一直都没变，但是今天编译的时候，却提示错误： 然后我就表示很费解，查看我的.sh文件，其中有很多的[] ，都是这些报错，可是之前一直没问题。 后来发现，因为Ubuntu默认的sh是连接到dash的,又因为dash跟bash的不兼容所以出错了.执行时可以把sh换成bash文件名.sh来执行.成功.dash是什么东西,查...
解决 linux下编译.sh文件报错 “[: XXXX: unexpected operator” 问题
热门推荐
671coder的专栏
11-27 1万+
本人经常在linux通过编译 .sh文件来生成工程，之前一直都没问题，代码一直都没变，但是今天编译的时候，却提示错误：        然后我就表示很费解，查看我的.sh文件，其中有很多的[] ，都是这些报错，可是之前一直没问题。       后来发现，因为ubuntu默认的sh是连接到dash的,又因为dash跟bash的不兼容所以出错了.执行时可以把sh换成bash文件名.sh来执行.成功.da
[: 0: unexpected operator
qq_45613171的博客
03-04 1061
将shell脚本第一行#!/bin/sh换成#!/bin/bash
sh报错 [: unexpected operat
程裕强的专栏
04-13 1278
问题shell脚本之前一直执行正常，今天突然报错了root@node:~/scripts# sh JavaInstall.sh JavaInstall.sh: 22: [: unexpected operator JavaInstall.sh: 32: [: unexpected operator解决办法原来Ubuntu下sh连接到dash，不是bash。 dash是啥玩意，不知道。 还是把s
shell文件报错 “XXX: unexpected operator” 问题
lijunlin0329的博客
04-22 993
dash是一种 Unix shell，它执行 shell scripts 的速度比bash快，需要的软件库也较少。貌似用户对它的诟病颇多。因为ubuntu默认的sh是连接到dash的，又因为dash跟bash的不兼容所以出错了，执行时可以把。将== 改为=就行了，dash判断字符串相等用的是=。判断语句[ ]中写有 == 时，运行。在某论坛看到别人讨论的结果。
Linux： [: missing ] 或unexpected operator错误 或 Syntax error: Bad for loop variable
起舞的风的博客
03-23 741
解决方案： 将==改成= 因为在bash中默认的 判断语句是=。 虽然鸟哥私房菜里面说与=效果一样，都是判断，但是实际测试时候发现会报错，改为一个=号即可。 ...
评论 2
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值