AskOverflow.Dev

AskOverflow.Dev Logo AskOverflow.Dev Logo

AskOverflow.Dev Navigation

  • 主页
  • 系统&网络
  • Ubuntu
  • Unix
  • DBA
  • Computer
  • Coding
  • LangChain

Mobile menu

Close
  • 主页
  • 系统&网络
    • 最新
    • 热门
    • 标签
  • Ubuntu
    • 最新
    • 热门
    • 标签
  • Unix
    • 最新
    • 标签
  • DBA
    • 最新
    • 标签
  • Computer
    • 最新
    • 标签
  • Coding
    • 最新
    • 标签
主页 / ubuntu / 问题

问题[arm](ubuntu)

Martin Hope
cseha
Asked: 2020-09-26 06:21:34 +0800 CST

ln -s 无法为文件创建符号

  • 0

我正在尝试安装 arm 工具链,我的编程老师给了我如何安装的说明。我提取了下载的库,/opt并尝试创建/usr/local/bin指向的链接/opt/gcc.../bin/*file

他给我的命令:

sudo ln -s opt/gcc-arm-none-eabi-9-2019-q4-major/bin/arm-none-eabi-gcc /usr/local/bin/arm-none-eabi-gcc

然后我检查了版本:

arm-none-eabi-gcc --version

但它说它没有安装。我/usr/local/bin 和午夜指挥官一起调查,链接是红色的:!arm-none-eabi-gcc

我检查了,我写的一切都正确。我在想也许我从 arm 网站下载了错误版本的工具链。

有人能帮我吗?谢谢!

software-installation gcc arm symbolic-link
  • 1 个回答
  • 89 Views
Martin Hope
Niviral
Asked: 2020-08-24 07:45:12 +0800 CST

尝试在 Raspberry Pi 上安装 docker-compose 时出现“ffi.h:没有这样的文件或目录”

  • 8

我正在尝试在 Ubuntu 20.04(ARM Rasberry PI 4)上安装 docker-compose。但是当我遵循Docker 文档的官方指南时,我不能使用标准路由,因为 GitHub 上没有 Linux-aarch64 的版本,只有 x86。

但是当我通过我尝试替代版本时pip install收到错误

    ERROR: Command errored out with exit status 1:
     command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-2kn5p6q3/cffi/setup.py'"'"'; __file__='"'"'/tmp/pip-install-2kn5p6q3/cffi/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-u7mx6nfb/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.8/cffi
         cwd: /tmp/pip-install-2kn5p6q3/cffi/
    Complete output (36 lines):
    running install
    running build
    running build_py
    creating build
    creating build/lib.linux-aarch64-3.8
    creating build/lib.linux-aarch64-3.8/cffi
    copying cffi/recompiler.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/vengine_gen.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/commontypes.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/setuptools_ext.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/cparser.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/api.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/backend_ctypes.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/ffiplatform.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/__init__.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/vengine_cpy.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/verifier.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/model.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/lock.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/pkgconfig.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/error.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/cffi_opcode.py -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/_cffi_include.h -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/parse_c_type.h -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/_embedding.h -> build/lib.linux-aarch64-3.8/cffi
    copying cffi/_cffi_errors.h -> build/lib.linux-aarch64-3.8/cffi
    running build_ext
    building '_cffi_backend' extension
    creating build/temp.linux-aarch64-3.8
    creating build/temp.linux-aarch64-3.8/c
    aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/usr/include/python3.8 -c c/_cffi_backend.c -o build/temp.linux-aarch64-3.8/c/_cffi_backend.o
    c/_cffi_backend.c:15:10: fatal error: ffi.h: No such file or directory
       15 | #include <ffi.h>
          |          ^~~~~~~
    compilation terminated.
    error: command 'aarch64-linux-gnu-gcc' failed with exit status 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-2kn5p6q3/cffi/setup.py'"'"'; __file__='"'"'/tmp/pip-install-2kn5p6q3/cffi/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-u7mx6nfb/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.8/cffi Check the logs for full command output.
software-installation arm docker raspberrypi
  • 1 个回答
  • 10994 Views
Martin Hope
TSpark
Asked: 2020-07-31 05:25:30 +0800 CST

apt update 在 arm 上的 Ubuntu 20.04 容器中引发签名错误

  • 43

我正在尝试构建 Raspberry Pi docker 映像,但我总是遇到相同的错误,类似于this、this和this。

在 a (或只是)apt update中以 root 身份运行命令时,我得到以下输出:arm32v7/ubuntu:20.04ubuntu:latest

root@273d63597ce6:/# apt update
Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [111 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [98.3 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [107 kB]
Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease
  At least one invalid signature was encountered.
Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease
  At least one invalid signature was encountered.
Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease
  At least one invalid signature was encountered.
Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease
  At least one invalid signature was encountered.
Reading package lists... Done
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

我已经尝试了清理 apt、清理 docker 和删除/重新创建的建议解决方案,但均未/var/lib/apt/lists成功。SD 卡为 32G,操作系统为全新安装。df显示26G免费。

更多信息:

  • 这是在树莓派 4 B 上全新安装 2020-05-27-raspios-buster-lite-armhf 时发生的
  • 同样的错误发生在另一个运行 HypriotOS 的 Raspberry Pi 4 B 上
  • 相同图像中的相同命令在安装了 Arch linux 的树莓派 3 B 上运行良好
  • ubuntu:18.04如果我使用旧版本的 ubuntu ( , 16.04, 14.04) ,则不会发生该错误
gnupg arm docker raspberrypi 20.04
  • 4 个回答
  • 36400 Views
Martin Hope
Aleksander Khoroshko
Asked: 2020-05-25 11:04:34 +0800 CST

如何在 Ubuntu 20.04 LTS (Focal Fossa) 上安装 arm-none-eabi-gdb

  • 20

我尝试安装 arm-none-eabi-gdb 作为 gcc-arm-embedded 的一部分。我添加了 PPA:

sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa

并执行:

sudo apt install gcc-arm-embedded 

它的回应是:

Err:8 http://ppa.launchpad.net/team-gcc-arm-embedded/ppa/ubuntu focal Release
  404  Not Found [IP: 91.189.95.83 80]

据我了解-gcc-arm-embedded 没有适用于 Ubuntu 20 的版本。因此,我已将软件和更新中此 PPA 的发布版本更改为仿生,这样我就可以避免错误 404。

即使 ubuntu 20 有 libisl22,现在当我尝试安装 gcc-arm-embedded 时我有未满足的依赖项:

The following packages have unmet dependencies:
 gcc-arm-embedded : Depends: libisl15 (>= 0.15) but it is not installable
E: Unable to correct problems, you have held broken packages.

我无法找到安装请求版本的 libisl 的方法,因为 apt 仅提供两个版本 - libisl22 和 libisl-dev 并且安装程序不接受这两个版本。

我需要有关如何安装 arm-none-eabi-gdb 的建议。谢谢!

apt gcc arm
  • 4 个回答
  • 49209 Views
Martin Hope
Daniel Böhmer
Asked: 2020-02-17 21:19:02 +0800 CST

如何在 ARM 或任何其他来自 Ubuntu Ports 的 Arch 上安装 i386/amd64 软件包

  • 2

我需要在 Raspberry Pi(armhf端口,ARMv7)上使用 QEMU 运行一些 x86 二进制文件,以使打印机与佳能糟糕的二进制 UFRII 驱动程序一起工作。如何仅安装其 x86 依赖项armhf(而不是如何运行它们)?

我可以安装 x86 二进制文件:

root@raspberry-pi:~# dpkg --force-architecture -i /tmp/cnrdrvcups-ufr2-uk_5.10-1_i386.deb

但随后apt一直抱怨缺少它的依赖项。我可能实际上需要它们来运行 UFRII 转换器——所以我真的很想通过apt.

我可以添加i386架构,但apt-get update无法下载一些资源,可能是因为armhf它位于 ports.ubuntu.com 上,而 x86 包位于主镜像上。(我之前曾经在amd64上成功安装过i386包。)

root@raspberry-pi:~# dpkg --add-architecture i386       
root@raspberry-pi:~# apt-get update                  
Hit:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease
Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB]
Ign:5 http://ports.ubuntu.com/ubuntu-ports bionic/main i386 Packages
Ign:6 http://ports.ubuntu.com/ubuntu-ports bionic/restricted i386 Packages
Ign:7 http://ports.ubuntu.com/ubuntu-ports bionic/universe i386 Packages
Ign:8 http://ports.ubuntu.com/ubuntu-ports bionic/multiverse i386 Packages
Ign:5 http://ports.ubuntu.com/ubuntu-ports bionic/main i386 Packages
Ign:6 http://ports.ubuntu.com/ubuntu-ports bionic/restricted i386 Packages
Ign:7 http://ports.ubuntu.com/ubuntu-ports bionic/universe i386 Packages
Ign:8 http://ports.ubuntu.com/ubuntu-ports bionic/multiverse i386 Packages
Ign:5 http://ports.ubuntu.com/ubuntu-ports bionic/main i386 Packages
Ign:6 http://ports.ubuntu.com/ubuntu-ports bionic/restricted i386 Packages
Ign:7 http://ports.ubuntu.com/ubuntu-ports bionic/universe i386 Packages
Ign:8 http://ports.ubuntu.com/ubuntu-ports bionic/multiverse i386 Packages
Err:5 http://ports.ubuntu.com/ubuntu-ports bionic/main i386 Packages
  404  Not Found [IP: 91.189.88.150 80]
Ign:6 http://ports.ubuntu.com/ubuntu-ports bionic/restricted i386 Packages
Ign:7 http://ports.ubuntu.com/ubuntu-ports bionic/universe i386 Packages
Ign:8 http://ports.ubuntu.com/ubuntu-ports bionic/multiverse i386 Packages
Ign:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main i386 Packages
Ign:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted i386 Packages
Ign:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe i386 Packages
Ign:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse i386 Packages
Ign:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main i386 Packages
Ign:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted i386 Packages
Ign:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe i386 Packages
Ign:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse i386 Packages
Ign:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main i386 Packages
Ign:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted i386 Packages
Ign:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe i386 Packages
Ign:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse i386 Packages
Err:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main i386 Packages
  404  Not Found [IP: 91.189.88.150 80]
Ign:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted i386 Packages
Ign:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe i386 Packages
Ign:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse i386 Packages
Ign:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main i386 Packages
Ign:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe i386 Packages
Ign:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main i386 Packages
Ign:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe i386 Packages
Ign:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main i386 Packages
Ign:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe i386 Packages
Err:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main i386 Packages
  404  Not Found [IP: 91.189.88.150 80]
Ign:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe i386 Packages
Ign:15 http://ports.ubuntu.com/ubuntu-ports bionic-security/main i386 Packages
Ign:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted i386 Packages
Ign:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe i386 Packages
Ign:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse i386 Packages
Ign:15 http://ports.ubuntu.com/ubuntu-ports bionic-security/main i386 Packages
Ign:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted i386 Packages
Ign:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe i386 Packages
Ign:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse i386 Packages
Ign:15 http://ports.ubuntu.com/ubuntu-ports bionic-security/main i386 Packages
Ign:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted i386 Packages
Ign:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe i386 Packages
Ign:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse i386 Packages
Err:15 http://ports.ubuntu.com/ubuntu-ports bionic-security/main i386 Packages
  404  Not Found [IP: 91.189.88.150 80]
Ign:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted i386 Packages
Ign:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe i386 Packages
Ign:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse i386 Packages
Fetched 252 kB in 2s (112 kB/s)
Reading package lists... Done
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/binary-i386/Packages  404  Not Found [IP: 91.189.88.150 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/main/binary-i386/Packages  404  Not Found [IP: 91.189.88.150 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/main/binary-i386/Packages  404  Not Found [IP: 91.189.88.150 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/main/binary-i386/Packages  404  Not Found [IP: 91.189.88.150 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

如何解决这个问题?我可能需要调整/添加一些东西,/etc/apt/sources.list但不包含字符串i386/ amd64。所以我不知道从哪里开始。这是我当前的源文件:

## Note, this file is written by cloud-init on first boot of an instance
## modifications made here will not survive a re-bundle.
## if you wish to make changes you can:
## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg
##     or do the same in user-data
## b.) add sources in /etc/apt/sources.list.d
## c.) make changes to template file /etc/cloud/templates/sources.list.tmpl

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://ports.ubuntu.com/ubuntu-ports bionic main restricted
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://ports.ubuntu.com/ubuntu-ports bionic-updates main restricted
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://ports.ubuntu.com/ubuntu-ports bionic universe
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic universe
deb http://ports.ubuntu.com/ubuntu-ports bionic-updates universe
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://ports.ubuntu.com/ubuntu-ports bionic multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic multiverse
deb http://ports.ubuntu.com/ubuntu-ports bionic-updates multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://ports.ubuntu.com/ubuntu-ports bionic-backports main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu bionic partner
# deb-src http://archive.canonical.com/ubuntu bionic partner

deb http://ports.ubuntu.com/ubuntu-ports bionic-security main restricted
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic-security main restricted
deb http://ports.ubuntu.com/ubuntu-ports bionic-security universe
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic-security universe
deb http://ports.ubuntu.com/ubuntu-ports bionic-security multiverse
# deb-src http://ports.ubuntu.com/ubuntu-ports bionic-security multiverse

我发现了如何在基于 ARM 的 Nexus 7 上的 Ubuntu 上安装 i386 软件包的问题?但是那里的人只是回答不可能在 ARM 上运行 x86。这是真的,但不是原始问题的正确答案。

更新:这是dpkg-deb所需驱动程序包的输出,包括其第一级依赖项:

root@raspberry-pi:~# dpkg-deb --info /tmp/cnrdrvcups-ufr2-uk_5.10-1_i386.deb 
 new Debian package, version 2.0.
 size 21503884 bytes: control archive=20743 bytes.
    2058 bytes,    16 lines      control              
   62636 bytes,   896 lines      md5sums              
     339 bytes,    17 lines   *  postinst             #!/bin/sh
      90 bytes,     9 lines   *  postrm               #!/bin/sh
 Package: cnrdrvcups-ufr2-uk
 Version: 5.10-1
 Section: net
 Priority: optional
 Architecture: i386
 Depends: cupsys | cups, libcups2 | libcupsys2 (>= 1.2.7)
 Conflicts: cnrcupsiradv715zk, cnrcupsiradv615zk, cnrcupsiradv525zk, cnrcupsiradv7153zk, cnrcupsiradv6153zk, cnrcupsiradv5253zk, cnrcupsiradv85053zk, cnrcupsiradv85853zk, cnrcupsiradv65753zk, cnrcupsiradv65553zk, cnrcupsiradvc35203zk, cnrcupsiradvc35253zk, cnrcupsiradvc75803zk, cnrcupsiradvc75653zk, cnrcupsiradvc2563zk, cnrcupsiradvc55353zk, cnrcupsiradvc55503zk, cnrcupsiradv45453zk, cnrcupsiradv45253zk, cnrcupsiradvc4753zk, cnrcupswg7000zk, cnrcupswg7000zzk, cnrcupslbp853czk, cnrcupslbp852czk, cnrcupsd1600zk
 Replaces: cnrdrvcups-ufr2-us, cnrdrvcups-lipslx, cnrcupsiradv715zk, cnrcupsiradv615zk, cnrcupsiradv525zk, cnrcupsiradv7153zk, cnrcupsiradv6153zk, cnrcupsiradv5253zk, cnrcupsiradv85053zk, cnrcupsiradv85853zk, cnrcupsiradv65753zk, cnrcupsiradv65553zk, cnrcupsiradvc35203zk, cnrcupsiradvc35253zk, cnrcupsiradvc75803zk, cnrcupsiradvc75653zk, cnrcupsiradvc2563zk, cnrcupsiradvc55353zk, cnrcupsiradvc55503zk, cnrcupsiradv45453zk, cnrcupsiradv45253zk, cnrcupsiradvc4753zk, cnrcupswg7000zk, cnrcupswg7000zzk, cnrcupslbp853czk, cnrcupslbp852czk, cnrcupsd1600zk
 Provides: cnrcupsiradv715zk, cnrcupsiradv615zk, cnrcupsiradv525zk, cnrcupsiradv7153zk, cnrcupsiradv6153zk, cnrcupsiradv5253zk, cnrcupsiradv85053zk, cnrcupsiradv85853zk, cnrcupsiradv65753zk, cnrcupsiradv65553zk, cnrcupsiradvc35203zk, cnrcupsiradvc35253zk, cnrcupsiradvc75803zk, cnrcupsiradvc75653zk, cnrcupsiradvc2563zk, cnrcupsiradvc55353zk, cnrcupsiradvc55503zk, cnrcupsiradv45453zk, cnrcupsiradv45253zk, cnrcupsiradvc4753zk, cnrcupswg7000zk, cnrcupswg7000zzk, cnrcupslbp853czk, cnrcupslbp852czk, cnrcupsd1600zk
 Installed-Size: 76096
 Maintainer: CANON INC. <sup-debian@mail.canon>
 Source: cnrdrvcups-lb
 Description: Canon UFR2 Printer Driver for Linux
  Canon UFR2 Printer Driver for Linux.
  This UFR2 printer driver provides printing functions for Canon LBP/iR
  printers operating under the CUPS (Common UNIX Printing System) environment.
dependencies apt arm raspberrypi multiarch
  • 1 个回答
  • 9329 Views
Martin Hope
shkim
Asked: 2019-10-30 16:36:15 +0800 CST

命令在 ARM 根文件系统中运行

  • 1

我正在开发 ARM 板(beaglebone black)。

当我创建 bootimg 映像时,我只是将 ARM 根文件系统复制到启动磁盘。但是,我想像运行主机 PC 一样运行 Linux 命令。

如何在 rootfilesystem 中运行类似 install package 的 linux 命令?(不是主机 PC 的根文件系统。在 Rootfilesystem 中运行命令以便稍后从主机 PC 复制到 ARM 目标板。)

linux中是否有任何ARM环境仿真工具?

command-line virtualization arm beagleboard
  • 1 个回答
  • 202 Views
Martin Hope
Anisyanka
Asked: 2019-10-16 05:27:36 +0800 CST

交叉编译器路径

  • 4

我有一些针对不同架构的编译器:

$ > whereis gcc
gcc: /usr/bin/gcc /usr/lib/gcc /usr/share/man/man1/gcc.1.gz

$ > whereis arm-linux-gnueabi-gcc
arm-linux-gnueabi-gcc: /usr/bin/arm-linux-gnueabi-gcc /usr/share/man/man1/arm-linux-gnueabi-gcc.1.gz

$ > whereis arm-linux-gnueabihf-gcc
arm-linux-gnueabihf-gcc: ~/.local/bin/arm-linux-gnueabihf-gcc

gcc 适用于我的工作站。它安装在系统路径中。

arm-linux-gnueabi-gcc 用于没有硬浮点的 ARM 目标。它也安装在系统路径中。

arm-linux-gnueabihf-gcc 用于带有硬浮点的 ARM 目标。它安装在我的$(HOME)/.local/目录中。我已将此目录添加到.bashrc脚本中的二进制路径:

export PATH="$HOME/.local/bin:$PATH"

system 命令whereis适用于所有这些编译器,并显示二进制可执行文件的有效路径。

我想用帮助arm-linux-gnueabihf-gcc编译器为 ARM 编译一些项目,但我收到了这个:

as: unrecognised option '-mcpu=cortex-a53'

汇编期间出错。似乎我的构建系统希望为我的 x86 使用汇编程序,而不是arm-linux-gnueabihf-as.

安装arm-linux-gnueabihf到~/.local其中后,会出现一些目录:

 ~/.local> ls -l
arm-linux-gnueabihf/
bin/
gcc-linaro-5.3.1-2016.05-linux-manifest.txt
include/
lib/
libexec/
share/

如果我去,bin/我会看到二进制文件:

arm-linux-gnueabihf-addr2line*  arm-linux-gnueabihf-cpp*        arm-linux-gnueabihf-gcc-ar*      arm-linux-gnueabihf-gdb*       arm-linux-gnueabihf-nm*       arm-linux-gnueabihf-size*     isort*
arm-linux-gnueabihf-ar*         arm-linux-gnueabihf-elfedit*    arm-linux-gnueabihf-gcc-nm*      arm-linux-gnueabihf-gfortran*  arm-linux-gnueabihf-objcopy*  arm-linux-gnueabihf-strings*  pylint*
arm-linux-gnueabihf-as*         arm-linux-gnueabihf-g++*        arm-linux-gnueabihf-gcc-ranlib*  arm-linux-gnueabihf-gprof*     arm-linux-gnueabihf-objdump*  arm-linux-gnueabihf-strip*    pyreverse*
arm-linux-gnueabihf-c++*        arm-linux-gnueabihf-gcc*        arm-linux-gnueabihf-gcov*        arm-linux-gnueabihf-ld*        arm-linux-gnueabihf-ranlib*   epylint*                      runtest*
arm-linux-gnueabihf-c++filt*    arm-linux-gnueabihf-gcc-5.3.1*  arm-linux-gnueabihf-gcov-tool*   arm-linux-gnueabihf-ld.bfd*    arm-linux-gnueabihf-readelf*  gdbserver*                    symilar*

此路径已添加到$PATH.

但是,如果我去./arm-linux-gnueabihf/bin并且会去做ls,我将收到空目录。我可以克服这个错误,如果我将一些符号链接添加到这个目录:

ar -> ../../bin/arm-linux-gnueabihf-ar*
as -> ../../bin/arm-linux-gnueabihf-as*
gcc -> ../../bin/arm-linux-gnueabihf-gcc*
ranlib -> ../../bin/arm-linux-gnueabihf-ranlib*
strip -> ../../bin/arm-linux-gnueabihf-strip*
...

在此之后,我的汇编错误消失了,我可以成功地为 ARM-target 编译项目。但在此之后,我无法为我的工作站 x86 编译任何东西。

谁能解释一下我应该怎么做才能成功编译以及ARM和x86?

UPD:我有 ARM 的 Makefile:

CROSS_COMPILE = arm-linux-gnueabihf-
CC            = $(CROSS_COMPILE)gcc
AS            = $(CROSS_COMPILE)as

INCLUDES      = -I./
SRC           = main.c
TARGET        = my-arm-target

all: $(SRC)
    $(CC) $(INCLUDES) -o $(TARGET)

和 x86 的相同文件,但没有CROSS_COMPILE变量:

CC            = gcc
AS            = as

INCLUDES      = -I./
SRC           = main.c
TARGET        = my-x86-target

all: $(SRC)
    $(CC) $(INCLUDES) -o $(TARGET)
software-installation compiling gcc arm cross-compilation
  • 1 个回答
  • 4840 Views
Martin Hope
catalex
Asked: 2019-10-12 07:01:23 +0800 CST

-bash: ./my_file: 无法执行二进制文件:执行格式错误,但我的架构和精灵匹配

  • 1

我正在尝试使用ubuntu64-16.04.3-minimal-odroid-c2-20171005操作系统在 Odroid-C2 上运行二进制文件。该文件有 777 权限,是为 ARM 编译的。

# ls -l my_file
-rwxrwxrwx 1 root root 136409 Sep 30 13:17 my_file

#pwd
/home

#file my_file
my_file: ELF 32-bit LSB executable, ARM, version 1, statically linked, not stripped

#uname -a
Linux odroid64 3.14.79-116 #1 SMP PREEMPT Tue Sep 26 01:19:06 BRT 2017 aarch64 aarch64 aarch64 GNU/Linux 

当我尝试运行它(./my_file)时,我收到一个错误: -bash: ./my_file: cannot execute binary file:Exec format error

我知道我的二进制文件是 32 位的,而我的 Ubuntu 是 64 位的,所以我按照本教程添加了新架构。这没有帮助,正在发生同样的错误。

我还搜索了另一种解决方案,但似乎出现此错误的唯一问题是架构不匹配。我很确定这不是我的问题——elf 是 ARM,Odroid 也是。我以前在这个 Odroid 上运行过类似的二进制文件,所以我现在真的很困惑。

你能帮我找出我的错误吗?

64-bit bash 32-bit arm binary
  • 1 个回答
  • 5345 Views
Martin Hope
davet
Asked: 2019-07-10 10:20:19 +0800 CST

ATLAS 在 ARM CPU 上的 Ubuntu 18.04 Mate 上安装在哪里?

  • 1

我使用命令在 Ubuntu 18.04 Mate 上安装了 Atlas

sudo apt-get install libatlas-base-dev

我在 Odroid N2 ( https://www.hardkernel.com/shop/odroid-n2-with-4gbyte-ram/ ) 上运行它,所以它是一个 ARM 系统。

虽然安装它的命令有效,但我找不到它的安装位置。我正在尝试运行 GAMESS ( https://www.msg.chem.iastate.edu/gamess/ ),部分配置询问我在哪里安装了 ATLAS。在 Odroid XU4 上的 Ubuntu 16.04 Mate 中,它被安装到 /usr/lib/atlas-base,但我在那里找不到它。提前感谢您的帮助。

arm mate 18.04
  • 1 个回答
  • 1423 Views
Martin Hope
Archisman Panigrahi
Asked: 2019-06-23 23:34:13 +0800 CST

无法在 armhf 中安装 Octave - 加载“libopenblas.so.0”时出错

  • 0

我在手机的 Termux 中安装了 Ubuntu 18.04(使用 Canonical 创建的 armhf rootfs )。

安装 octave ( sudo apt install octave) 时出现以下错误。

Setting up octave (4.2.2-1ubuntu1) ...    
/usr/bin/octave-cli: error while loading shared libraries: libopenblas.so.0: cannot enable executable stack as shared object requires: Permission denied
dpkg: error processing package octave (--configure):
 installed octave package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
  octave                                   
E: Sub-process /usr/bin/dpkg returned an error code (1)

我跑octave --configure了,这又说

/usr/bin/octave-cli: error while loading shared libraries: libopenblas.so.0: cannot enable executable stack as shared object requires: Permission denied

有没有办法解决这个问题?该软件包libopenblas-dev已安装。

android arm shared-library octave 18.04
  • 1 个回答
  • 1646 Views

Sidebar

Stats

  • 问题 205573
  • 回答 270741
  • 最佳答案 135370
  • 用户 68524
  • 热门
  • 回答
  • Marko Smith

    如何运行 .sh 脚本?

    • 16 个回答
  • Marko Smith

    如何安装 .tar.gz(或 .tar.bz2)文件?

    • 14 个回答
  • Marko Smith

    如何列出所有已安装的软件包

    • 24 个回答
  • Marko Smith

    无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗?

    • 25 个回答
  • Martin Hope
    Flimm 如何在没有 sudo 的情况下使用 docker? 2014-06-07 00:17:43 +0800 CST
  • Martin Hope
    Ivan 如何列出所有已安装的软件包 2010-12-17 18:08:49 +0800 CST
  • Martin Hope
    La Ode Adam Saputra 无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗? 2010-11-30 18:12:48 +0800 CST
  • Martin Hope
    David Barry 如何从命令行确定目录(文件夹)的总大小? 2010-08-06 10:20:23 +0800 CST
  • Martin Hope
    jfoucher “以下软件包已被保留:”为什么以及如何解决? 2010-08-01 13:59:22 +0800 CST
  • Martin Hope
    David Ashford 如何删除 PPA? 2010-07-30 01:09:42 +0800 CST

热门标签

10.10 10.04 gnome networking server command-line package-management software-recommendation sound xorg

Explore

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve