rosetta error: failed to open elf at /lib64/ld-linux-x86-64.so.2怎么解决

最新推荐文章于 2024-03-14 16:38:08 发布
最新推荐文章于 2024-03-14 16:38:08 发布
阅读量3.8k 收藏 11
点赞数 9
CC 4.0 BY-SA版权
分类专栏： DEBUG 文章标签： linux 运维 服务器
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/cliukai/article/details/135559690

今天在打包然后运行docker镜像的时候遇到了这个问题

➜  docker-demo docker run javaweb:1.0 -d
rosetta error: failed to open elf at /lib64/ld-linux-x86-64.so.2
 Trace/breakpoint trap

注意观察，这个库函数里面有x86-64字样，指的是支持64位运算的X86架构的CPU，这种CPU一般由Intel和AMD家生产的芯片。

而如果恰好你的电脑是搭载Apple Chip例如M1/M2/M3的MacBook，那么系统里是没有这个函数库的，就会报错。

解决办法是在Docker引入Base操作系统的时候，加上--platform=linux/amd64指定AMD64格式，然后重新打镜像。

FROM --platform=linux/amd64 ubuntu:16.04

Reference:
https://stackoverflow.com/questions/71040681/qemu-x86-64-could-not-open-lib64-ld-linux-x86-64-so-2-no-such-file-or-direc

linux目录误删文件 /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory
qq_37960317的博客
03-18 2462
4.重启后出现这个界面，把光标移动到Troubleshooting，按回车，再选择Rescue a CentOS system，按回车就入救援模式。使用sln命令，可以创建到源文件的符号链接目标文件，它是静态链接的，无需动态链接，可以绕过ln命令。这个时候再使用sudo命令也不好使了，该怎么办。2.启动虚拟机时，选择电源–>打开电源时进入固件，进入启动界面。5.等待一段时间后，会出现如下界面，这里我们直接输入1。1.编辑虚拟机设置，挂载系统镜像，并设置启动时连接。这个时候，会再次看到下面的界面，依然选择。
之前安装docker桌面版，成功后卸载重新安装，出现了问题提示 Docker Desktop installation failed.
qi23118的博客
05-23 316
通过官网卸载方案，把文件全部删除。特别注意，需要设置权限才可以删除。
rosetta error: failed to open elf at /lib64/ld-linux-x86-64.so.2
ttyy1112的专栏
03-14 1841
在MacOS使用docker build构建镜像时提示如下错误注意观察，这个库函数里面有x86-64字样，指的是支持64位运算的X86架构的CPU，这种CPU一般由Intel和AMD家生产的芯片。而如果恰好你的电脑是搭载Apple Chip例如M1/M2/M3的MacBook，那么系统里是没有这个函数库的，就会报错。解决办法是在Docker引入Base操作系统的时候，加上指定AMD64格式，然后重新打镜像。
linux 出现bash: ****: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory
weixin_34334744的博客
08-30 3422
误删除glibc-2.12-1.192.el6.x86_64 rpm包，导致整个系统的所有命令（cd除外）都不能用。使用命令出现如下提示：bash: /bin/cp: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directorybash: /bin/ls: /lib64/ld-lin...
【报错】-bash: /bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory
康师傅没有眼泪
05-11 7895
【linux】-bash: /bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory linux操作移动了根目录下的/lib和/lib64之后系统使用除了cd之外的任何命令都提示 -bash: /bin/ls: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory。 删除 mysql的..
Rosetta error:bad input问题（解决）
Suuo1的博客
03-19 2572
命令： 给出的报错： 原因：xml脚本太旧，需要更新，尝试过 python $ROSETTA/tools/xsd_xrw/rewrite_rosetta_script.py --input <input.xml> --output <output.xml> 还是error:未预期的符号 `newline' 附近有语法错误 最后把<>改成单引号''就成功了 python Rosetta/tools/xsd_xrw/rewrite_rosetta_s.
(base) liu_wd@structure4:/media/stor4/prog/Rosetta/rosetta_bin_linux_3.14_bundle/rosetta.binary.linux.release-371/main/inputs-LZL$ #!/bin/bash ROSETTA_PATH="/media/stor4/prog/Rosetta/rosetta_bin_linux_3.14_bundle/rosetta.binary.linux.release-371" g++ -O3 -std=c++11 mutation_scan.cpp \ -I $ROSETTA_PATH/main/source/src \ -I $ROSETTA_PATH/main/source/external/include \ -I $ROSETTA_PATH/external/include \ -L $ROSETTA_PATH/main/source/build/src/release/linux/5.14/64/x86/gcc/11/default/ \ -Wl,-rpath,$ROSETTA_PATH/main/source/build/src/release/linux/5.14/64/x86/gcc/11/default/ \ -lcore -lprotocols -lbasic -lutility -lchemical -lobjexxfcl -lz \ -lboost_system -lboost_thread -lpthread \ -o mutation_scan mutation_scan.cpp:17:10: fatal error: core/init.hh: No such file or directory 17 | #include <core/init.hh> | ^~~~~~~~~~~~~~ compilation terminated.
最新发布
07-14
我们正在解决用户编译Rosetta程序时出现的头文件缺失问题。用户遇到了`core/init.hh`找不到的错误，这通常是由于编译配置不正确导致的。下面将详细分析问题并提供解决方案。 ### 问题分析 1. **错误本质**：`fatal ...
stellaechen@STELLAECHEN-MC1 Python-2.7.13 % make ./python.exe -E -S -m sysconfig --generate-posix-vars ;\ if test $? -ne 0 ; then \ echo "generate-posix-vars failed" ; \ rm -f ./pybuilddir.txt ; \ exit 1 ; \ fi running build running build_ext building '_Qt' extension gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/stellaechen/download/Python-2.7.13/Mac/Include -I. -IInclude -I./Include -I/usr/local/include -I/Users/stellaechen/download/Python-2.7.13/Include -I/Users/stellaechen/download/Python-2.7.13 -c /Users/stellaechen/download/Python-2.7.13/Mac/Modules/qt/_Qtmodule.c -o build/temp.macosx-15.4-arm64-2.7/Users/stellaechen/download/Python-2.7.13/Mac/Modules/qt/_Qtmodule.o -Wno-deprecated-declarations error: unable to open output file 'build/temp.macosx-15.4-arm64-2.7/Users/stellaechen/download/Python-2.7.13/Mac/Modules/qt/_Qtmodule.o': 'Operation not permitted' 1 error generated. building '_tkinter' extension gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -I/System/Library/Frameworks/Tcl.framework/Headers -I/System/Library/Frameworks/Tcl.framework/Versions/Current/PrivateHeaders -I/System/Library/Frameworks/Tk.framework/Headers -I/System/Library/Frameworks/Tk.framework/Versions/Current/PrivateHeaders -I/usr/X11R6/include -I/Users/stellaechen/download/Python-2.7.13/Mac/Include -I. -IInclude -I./Include -I/usr/local/include -I/Users/stellaechen/download/Python-2.7.13/Include -I/Users/stellaechen/download/Python-2.7.13 -c /Users/stellaechen/download/Python-2.7.13/Modules/_tkinter.c -o build/temp.macosx-15.4-arm64-2.7/Users/stellaechen/download/Python-2.7.13/Modules/_tkinter.o -framework Tk clang: warning: -framework Tk: 'linker' input unused [-Wunused-command-line-argument] In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_tkinter.c:71: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/tk.h:86:11: fatal error: 'X11/Xlib.h' file not found 86 | # include <X11/Xlib.h> | ^~~~~~~~~~~~ 1 error generated. building '_ctypes' extension gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I_ctypes/darwin -I/Users/stellaechen/download/Python-2.7.13/Mac/Include -I/Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include -I/Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/powerpc -I. -IInclude -I./Include -I/usr/local/include -I/Users/stellaechen/download/Python-2.7.13/Include -I/Users/stellaechen/download/Python-2.7.13 -c /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/_ctypes.c -o build/temp.macosx-15.4-arm64-2.7/Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/_ctypes.o -DMACOSX In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/_ctypes.c:113: /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffi.h:65:3: error: "Unsupported MacOS X CPU type" 65 | # error "Unsupported MacOS X CPU type" | ^ In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/_ctypes.c:113: In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffi.h:73: /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffitarget.h:12:2: error: "Unsupported CPU type" 12 | #error "Unsupported CPU type" | ^ In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/_ctypes.c:113: In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffi.h:74: /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/fficonfig.h:51:2: error: "Unknown CPU type" 51 | #error "Unknown CPU type" | ^ In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/_ctypes.c:113: /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffi.h:171:5: error: unknown type name 'ffi_abi' 171 | ffi_abi abi; | ^ /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffi.h:193:2: error: unknown type name 'ffi_sarg' 193 | ffi_sarg sint; | ^ /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffi.h:194:2: error: unknown type name 'ffi_arg' 194 | ffi_arg uint; | ^ /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/libffi_osx/include/ffi.h:307:11: error: unknown type name 'ffi_abi' 307 | ffi_abi abi, | ^ In file included from /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/_ctypes.c:129: /Users/stellaechen/download/Python-2.7.13/Modules/_ctypes/ctypes.h:99:5: error: unknown type name 'ffi_closure' 99 | ffi_closure *pcl_write; /* the C callable, writeable */ | ^ 8 errors generated. Python build finished, but the necessary bits to build these modules were not found: _bsddb _curses _curses_panel _sqlite3 _ssl bsddb185 bz2 dbm dl gdbm imageop linuxaudiodev nis ossaudiodev readline spwd sunaudiodev zlib To find the necessary bits, look in setup.py in detect_modules() for the module's name. Failed to build these modules: _ctypes _Qt _tkinter running build_scripts stellaechen@STELLAECHEN-MC1 Python-2.7.13 % make install /usr/bin/install -c python.exe /usr/local/bin/python2.7 install: /usr/local/bin/INS@20xsco: Permission denied make: *** [altbininstall] Error 71 stellaechen@STELLAECHEN-MC1 Python-2.7.13 %
07-05
我们正在解决用户在 macOS 上编译 Python 2.7.13 时遇到的三个主要问题：`_Qt`、`_tkinter`、`_ctypes` 模块构建失败，以及最后的 `make install` 权限问题。我们将逐一分析并提供解决方案。 ### 问题分析 1. **`_...
ERROR in ./src/views/Layout/index.vue?vue&type=style&index=0&id=5d5a9732&scoped=true&lang=scss (./node_modules/css-loader/dist/cjs.js??clonedRuleSet-22.use[1]!./node_modules/@vue/vue-loader-v15/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/dist/cjs.js??clonedRuleSet-22.use[2]!./node_modules/sass-loader/dist/cjs.js??clonedRuleSet-22.use[3]!./node_modules/@vue/vue-loader-v15/lib/index.js??vue-loader-options!./src/views/Layout/index.vue?vue&type=style&index=0&id=5d5a9732&scoped=true&lang=scss) Module build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: Node Sass does not yet support your current environment: OS X Unsupported architecture (arm64) with Unsupported runtime (127) For more information on which environments are supported please see: https://github.com/sass/node-sass/releases/tag/v9.0.0 at module.exports (/Users/xiaol/Desktop/2024034314-作品主文件夹/2024034314-02素材与源码/code/vue/monkey/monkey/node_modules/node-sass/lib/binding.js:13:13) at Object.<anonymous> (/Users/xiaol/Desktop/2024034314-作品主文件夹/2024034314-02素材与源码/code/vue/monkey/monkey/node_modules/node-sass/lib/index.js:13:35) at Module._compile (node:internal/modules/cjs/loader:1554:14) at Object..js (node:internal/modules/cjs/loader:1706:10) at Module.load (node:internal/modules/cjs/loader:1289:32) at Function._load (node:internal/modules/cjs/loader:1108:12) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:220:24) at Module.require (node:internal/modules/cjs/loader:1311:12) at require (node:internal/modules/helpers:136:16) at getDefaultSassImplementation (/Users/xiaol/Desktop/2024034314-作品主文件夹/2024034314-02素材与源码/code/vue/monkey/monkey/node_modules/sass-loader/dist/utils.js:36:10) at getSassImplementation (/Users/xiaol/Desktop/2024034314-作品主文件夹/2024034314-02素材与源码/code/vue/monkey/monkey/node_modules/sass-loader/dist/utils.js:45:30) at Object.loader (/Users/xiaol/Desktop
04-02
如果用户必须使用node-sass，可能需要通过安装特定版本或使用Rosetta 2来模拟x86环境。 最后，应该总结步骤，给出具体的命令和配置修改，让用户能一步步操作。还要提醒常见问题，比如依赖冲突、版本锁定，以及建议...
SyntaxError: invalid syntax >>> import talib Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/anaconda3/lib/python3.12/site-packages/talib/__init__.py", line 109, in <module> from ._ta_lib import ( ImportError: dlopen(/opt/anaconda3/lib/python3.12/site-packages/talib/_ta_lib.cpython-312-darwin.so, 0x0002): tried: '/opt/anaconda3/lib/python3.12/site-packages/talib/_ta_lib.cpython-312-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/opt/anaconda3/lib/python3.12/site-packages/talib/_ta_lib.cpython-312-darwin.so' (no such file), '/opt/anaconda3/lib/python3.12/site-packages/talib/_ta_lib.cpython-312-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64'))
03-22
另外，Rosetta 2可能是一个临时解决方案，让用户在x86_64环境下运行，但这不是长久之计，最好还是原生支持ARM架构。需要分步骤指导用户如何正确安装依赖，编译源码，并确保Python环境也是ARM64版本。 可能还需要...
qingguo@YideMacBook-Pro ~ % lipo -info /opt/homebrew/lib/libgsl.a Non-fat file: /opt/homebrew/lib/libgsl.a is architecture: arm64 qingguo@YideMacBook-Pro ~ %
03-21
/path/to/x86_64/libgsl.a ``` - 验证编译环境匹配： ```bash # 查看当前 shell 的 CPU 架构 uname -m # 确认 Xcode 选择的架构 xcodebuild -sdk -version ``` 该输出表明你的开发环境已正确配置为 Apple ...
/lib/ld-linux.so.2: bad ELF interpreter: No such file or directory问题解决
漫天雪_昆仑巅
06-27 3370
在linux中，有的时候会遇到以下错误：/lib/ld-linux.so.2: bad ELF interpreter: No such file or directory解决方法：# yum install glibc.i686安装以上依赖库即可！
m1芯片 遇到 /lib64/ld-linux-x86-64.so.2: No such file or directory 报错
liangliang233的博客
02-16 2621
mac m1芯片，安装java环境报错
linux oracle bad elf,oracle11g安装到red hat6.2 64位系统报错：/lib/ld-linux.so.2: bad ELF interpreter...
weixin_35414475的博客
04-04 204
oracle11g安装到red hat6.2 64位系统报错：/lib/ld-linux.so.2: bad ELF interpreter1、问题如下：[oracle@just ~]$ cd database/[oracle@just database]$ ./runInstaller./runInstaller: /u01/soft/client/install/.oui: /lib/ld-l...
linux解释器错误没有文件或目录,/lib/ld-linux.so.2：错误的ELF解释器：没有这样的文件或目录...
weixin_30030437的博客
05-01 1706
当我执行命令安装应用程序时出现以下错误： /lib/ld-linux.so.2：错误的ELF解释器：没有这样的文件或目录/lib/ld-linux.so.2：错误的ELF解释器：没有这样的文件或目录我不知道如何解决这个问题，找出我搜索了净solotutions分辨率，发现如下决议：yum install glibc.i686 or yum install glibc.i386但坏运气这不是在工作所...
qemu-x86_64: Could not open ‘/lib/ld-musl-x86_64.so.1‘: No such file or directory
陈万洲的专栏
01-01 1337
因此如果您可以选择从 ARM64 映像开始，并且可以在构建期间在容器内编译任何您无法安装为 ARM64 二进制文件的软件。在基于 M1 的 Mac 上运行容器时， ARM64 CPU 上被模拟为 x86_64。在Dockerfile中From中添加 --platform=linux/amd64。如果你有其他方案请留言。
Rosetta安装过程报错集锦
药研猿的博客
10-29 1084
运行内存太小，可以通过增加swap分区的方式弥补（一般需要运行内存+swap分区大于16G）缺少gcc、g++、gfortran其中一个或多个。同上文error2的情况，也是由于内存不够引起的。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值