重新安装zlib1g包: 现在,尝试重新安装zlib1g包: bash sudo apt install zlib1g:i386 如果安装过程中仍然出现“unable to locate package”的错误,可能是因为你的软件源中没有包含这个包,或者你的Ubuntu版本太新或太旧,而该版本的软件源中不再提供这个包。 考虑使用其他方法: 如果上述步骤都不奏效,你可能需要...
E:Unable to Locate Package devlb-dev 折腾半天,最后换了个源,解决了。 另外,rvm安装的ruby,如果缺少zlib的换,也能安装成功,只是自带的gem不能用。 报错: no such file to load -- zlib 错误 解决方法:重新编译依赖zlib的几个文件: #1 安装zlib1g 和 zlib1g-dev 包,然后 1.回到ruby源码目录 ext/zlib ...
The command '/bin/sh -c apt-get update && apt-get install -y libzip-dev && apt-get install -y zlib1g-dev && rm -rf /var/lib/apt/lists/* && docker-php-ext-install zip' returned a non-zero code: 100 ERROR: Service 'www' failed to build : Build failed ...
例如,软件包 golang 如果错误地输入为 golamg 会导致无法找到。在很多情况下,软件包名称和实际安装包名称并不相同,比如 zlib 在 Ubuntu 中的包名是 zlib1g。 你可以使用以下命令确认包名是否正确: apt-cache search package_name 2. 更新存储库缓存 如果缓存过时,可能会导致软件包无法找到。解决方法是更新软件源缓...
tryTry this: sudo apt-get install -y make build-essential libssl-dev zlib1g-dev libbz2-dev libreadline-dev libsqlite3-dev wget curl llvm libncurses5-dev libncursesw5-dev xz-utils tk-dev libffi-dev liblzma-dev python3-openssl sudo apt-get install -y make build-essential libssl-dev zli...
addons: apt: sources: - ubuntu-toolchain-r-test packages: - gcc-4.8 - g++-4.8 - python2.7 - wget - pkg-config - zip - zlib1g-dev - libunwind8-dev When it is run, it says it unable to locate the package. I tried with libunwind7-dev and libunwind-dev variations and again the sa...
apt-get install g++ u-boot-tools lib32z1 lib32ncurses5 lib32bz2-1.0 lib32stdc++6 zlib1g-dev liblzo2-dev uuid-dev libacl1-dev libncurses5-dev 1. 结果出现下面问题: E: Unable to locate package lib32bz2-1.0 E: Couldn't find any package by glob 'lib32bz2-1.0' ...
老师我用的是阿里云的服务器,sudo apt-get install golang python3-dev python-dev libcupti-dev libjpeg-turbo8-dev make tmux htop chromium-browser git cmake zlib1g-dev libjpeg-dev xvfb libav-tools xorg-dev python-opengl libboost-all-dev libsdl2-dev swig 我执行这一句的时候,有一个包报错 ...
在使用Linux下载packages时报错: ---好多不认识的--- E: Unable to locate package scipy 遇到这种问题,通常是由于镜像源没有更新下
Prerequisite Make sure your problem is not listed in the common build problems. Make sure no duplicated issue has already been reported in the pyenv issues. You should look for closed issues, too. Make sure you are not asking us to help ...