Configure yum to install dependencies automatically

最新推荐文章于 2024-05-01 02:32:08 发布
转载 最新推荐文章于 2024-05-01 02:32:08 发布 · 617 阅读 · 0

本文解决在 RHEL 6.4 中使用 yum 命令安装 rpm-build 包遇到的问题。默认情况下，系统未注册到 Red Hat Subscription Management，且两个可用的软件源被禁用。通过挂载红帽 DVD/ISO 文件建立本地仓库，并配置新的 repo 文件，最终成功安装 rpm-build 包。
I just install RHEL version 6.4. trying to use yum command to install rpm-build package, but it showing below error messages:

[root@redhat64 ~]# yum install rpm-build
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
No package rpm-build available.
Error: Nothing to do

By default, if you check with “yum repolist all” command, there are 2 repo source with status disabled:

    [root@redhat64 ~]# yum repolist all
    Loaded plugins: product-id, security, subscription-manager
    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
    repo id                              repo name                                                                   status
    rhel-source                          Red Hat Enterprise Linux 6Server - x86_64 - Source                          disabled
    rhel-source-beta                     Red Hat Enterprise Linux 6Server Beta - x86_64 - Source                     disabled
    repolist: 0
    [root@redhat64 ~]#

Check the Redhat repository configuration file, there are two repo name, both are pointed to redhat website:

    [root@redhat64 ~]# cd /etc/yum.repos.d/
    [root@redhat64 yum.repos.d]# ls
    rhel-source.repo
    [root@redhat64 yum.repos.d]# more rhel-source.repo
    [rhel-source]
    name=Red Hat Enterprise Linux $releasever - $basearch - Source
    baseurl=ftp://ftp.redhat.com/pub/redhat/linux/enterprise/$releasever/en/os/SRPMS/
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

    [rhel-source-beta]
    name=Red Hat Enterprise Linux $releasever Beta - $basearch - Source
    baseurl=ftp://ftp.redhat.com/pub/redhat/linux/beta/$releasever/en/os/SRPMS/
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta,file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
    [root@redhat64 yum.repos.d]#

We need to register to RHN in order to use those repo source, even you try to enable the repo, by editing the line “enable=0″ to “enable=1″ but it won’t work. The easy way is build a local repository from your current redhat’s DVD / ISO file:

    # mkdir /media
    # mount /dev/cdrom /media

Rename existing repo file “rhel-source.repo” to “rhel-source.repo.backup” or whatever you want.

Create another repo file name, example “dvd.repo”: 

(Note: keep in mind that never use the default repo name, such as "redhat.repo", otherwise the repo file will be emptied automatically once perform "yum repolist")


    # vi dvd.repo
    [dvd-source]
    name=RHEL 6.4 dvd repo
    baseurl=file:///media/Server
    enabled=1
    gpgcheck=0

Check your repo config, Test  and try to install the package:
# yum repolist
# yum install rpm-build

    [root@redhat64 yum.repos.d]# yum repolist
    Loaded plugins: product-id, security, subscription-manager
    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
    repo id                                               repo name                                                    status
    dvd-source                                            RHEL 6.4 dvd repo                                            3,648
    repolist: 3,648
    [root@redhat64 yum.repos.d]# yum install rpm-build
    Loaded plugins: product-id, security, subscription-manager
    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

    dvd-source                                                                                        | 3.9 kB     00:00 ...

    dvd-source/primary_db                                                                             | 3.1 MB     00:00 ...
    Setting up Install Process
    Resolving Dependencies
    --> Running transaction check
    ---> Package rpm-build.x86_64 0:4.8.0-32.el6 will be installed
    --> Finished Dependency Resolution

    Dependencies Resolved

    =========================================================================================================================
     Package                     Arch                     Version                         Repository                    Size
    =========================================================================================================================
    Installing:
     rpm-build                   x86_64                   4.8.0-32.el6                    dvd-source                   126 k

    Transaction Summary
    =========================================================================================================================
    Install       1 Package(s)

    Total download size: 126 k
    Installed size: 315 k
    Is this ok [y/N]: y
    Downloading Packages:
    Running rpm_check_debug
    Running Transaction Test
    Transaction Test Succeeded
    Running Transaction
    Warning: RPMDB altered outside of yum.

      Installing : rpm-build-4.8.0-32.el6.x86_64 [                                                                     ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [####                                                                 ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#####                                                                ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [######                                                               ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#######                                                              ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [########                                                             ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#################                                                    ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#########################                                            ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [###############################                                      ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################                                    ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [###################################                                  ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [####################################                                 ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#########################################                            ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [##########################################                           ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [###########################################                          ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [############################################                         ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [##############################################                       ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################                     ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################################                    ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [########################################################             ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#########################################################            ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [##########################################################           ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################################     ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [##################################################################   ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [###################################################################  ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################################################### ] 1/1
      Installing : rpm-build-4.8.0-32.el6.x86_64                                                                         1/1

    dvd-source/productid                                                                              | 1.7 kB     00:00 ...
      Verifying  : rpm-build-4.8.0-32.el6.x86_64                                                                         1/1
    Installed:
      rpm-build.x86_64 0:4.8.0-32.el6                                                                                        
    Complete!
    [root@redhat64 yum.repos.d]# 
Openstack组件部署 — Nova_Install and configure a compute node
烟云的计算
06-30 1万+
目录目录 前文列表 Prerequisites 先决条件 Install and configure a compute node Install the packages Edit the etcnovanovaconf file Finalize installation前文列表Openstack组件部署 — Overview和前期环境准备 Openstack组建部署 — Environme
ollama linux 安装脚本install.sh
青春不流名
08-09 966
以下为原脚本中JetPack、systemd配置、GPU检测等逻辑（保持不变）mkdir -p "$LOCAL_TGZ_DIR" # 确保目录存在。# 压缩包文件名（移除URL参数中的?，避免文件命名问题）# 核心修改：优先使用/home目录中的压缩包。# 定义压缩包存储路径（/home目录下）# 从本地压缩包解压。
yum安装
m0_61417337的博客
02-20 186
备份
configure --prefix=/ & yum install 路径
思緒凌亂
03-23 2754
linux, configure --prefix=/有什么用   指定安装路径 不指定prefix，则可执行文件默认放在/usr /local/bin，库文件默认放在/usr/local/lib，配置文件默认放在/usr/local/etc。其它的资源文件放在/usr /local/share。你要卸载这个程序，要么在原来的make目录下用一次make uninstall（前提是make文件
linux使用yum安装编译环境,Linux yum的配置使用和程序包的编译安装
weixin_39722070的博客
05-02 271
程序包的编译安装我们有的时候并不能获取到相应软件的rpm包或者是原本就是没有rpm包的，但是一般项目网站都会给我们提供对应的源代码，然后我们可以使用工具进行编译安装。编译C源代码的前提：提供开发环境及开发工具。开发工具：make,gcc等开发环境:开发库，头文件，标准库等在CentOS中是通过“包组”提供开发组件在centos6中：yum groupinstall "Development Too...
SpringBoot自动配置实现平台核心服务自动加载
Jack__iT的博客
05-01 352
什么是自动配置 看下官方原文咋说的，Spring Boot auto-configuration attempts to automatically configure your Spring application based on the jar dependencies that you have added. For example, ifHSQLDBis on your c...
peerDependencies安装
xwnxwn的专栏
05-01 1886
当我们的项目中有peerDependencies时，执行npm install会发现peerDependencies的依赖项并不会下载，如果一个个下载太过麻烦，因此推荐一个npm库npm-install-peers，可以直接下载。 npm install --save-dev npm-install-peers npm script { scripts: { "install-peers": "npm-install-peers" } } 执行对应脚本即
deepcar@ubuntu:~/Desktop$ apt-get apt 2.0.10 (arm64) Usage: apt-get [options] command apt-get [options] install|remove pkg1 [pkg2 ...] apt-get [options] source pkg1 [pkg2 ...] apt-get is a command line interface for retrieval of packages and information about them from authenticated sources and for installation, upgrade and removal of packages together with their dependencies. Most used commands: update - Retrieve new lists of packages upgrade - Perform an upgrade install - Install new packages (pkg is libc6 not libc6.deb) reinstall - Reinstall packages (pkg is libc6 not libc6.deb) remove - Remove packages purge - Remove packages and config files autoremove - Remove automatically all unused packages dist-upgrade - Distribution upgrade, see apt-get(8) dselect-upgrade - Follow dselect selections build-dep - Configure build-dependencies for source packages satisfy - Satisfy dependency strings clean - Erase downloaded archive files autoclean - Erase old downloaded archive files check - Verify that there are no broken dependencies source - Download source archives download - Download the binary package into the current directory changelog - Download and display the changelog for the given package See apt-get(8) for more information about the available commands. Configuration options and syntax is detailed in apt.conf(5). Information about how to configure sources can be found in sources.list(5). Package and version choices can be expressed via apt_preferences(5). Security details are available in apt-secure(8). This APT has Super Cow Powers.有什么问题
03-09
- **错误处理**：若提示 `apt-get command not found`，可能是系统非 Debian 系（如 CentOS 使用 `yum`）[^1]。 - **依赖冲突**：若升级失败，可尝试 `sudo apt-get -f install` 修复依赖。 --- §§ 相关问题 §...
#!/bin/sh # This script installs Ollama on Linux. # It detects the current operating system architecture and installs the appropriate version of Ollama. set -eu red="$( (/usr/bin/tput bold || :; /usr/bin/tput setaf 1 || :) 2>&-)" plain="$( (/usr/bin/tput sgr0 || :) 2>&-)" status() { echo ">>> $*" >&2; } error() { echo "${red}ERROR:${plain} $*"; exit 1; } warning() { echo "${red}WARNING:${plain} $*"; } TEMP_DIR=$(mktemp -d) cleanup() { rm -rf $TEMP_DIR; } trap cleanup EXIT available() { command -v $1 >/dev/null; } require() { local MISSING='' for TOOL in $*; do if ! available $TOOL; then MISSING="$MISSING $TOOL" fi done echo $MISSING } [ "$(uname -s)" = "Linux" ] || error 'This script is intended to run on Linux only.' ARCH=$(uname -m) case "$ARCH" in x86_64) ARCH="amd64" ;; aarch64|arm64) ARCH="arm64" ;; *) error "Unsupported architecture: $ARCH" ;; esac IS_WSL2=false KERN=$(uname -r) case "$KERN" in *icrosoft*WSL2 | *icrosoft*wsl2) IS_WSL2=true;; *icrosoft) error "Microsoft WSL1 is not currently supported. Please use WSL2 with 'wsl --set-version <distro> 2'" ;; *) ;; esac VER_PARAM="${OLLAMA_VERSION:+?version=$OLLAMA_VERSION}" SUDO= if [ "$(id -u)" -ne 0 ]; then # Running as root, no need for sudo if ! available sudo; then error "This script requires superuser permissions. Please re-run as root." fi SUDO="sudo" fi NEEDS=$(require curl awk grep sed tee xargs) if [ -n "$NEEDS" ]; then status "ERROR: The following tools are required but missing:" for NEED in $NEEDS; do echo " - $NEED" done exit 1 fi for BINDIR in /usr/local/bin /usr/bin /bin; do echo $PATH | grep -q $BINDIR && break || continue done OLLAMA_INSTALL_DIR=$(dirname ${BINDIR}) if [ -d "$OLLAMA_INSTALL_DIR/lib/ollama" ] ; then status "Cleaning up old version at $OLLAMA_INSTALL_DIR/lib/ollama" $SUDO rm -rf "$OLLAMA_INSTALL_DIR/lib/ollama" fi status "Installing ollama to $OLLAMA_INSTALL_DIR" $SUDO install -o0 -g0 -m755 -d $BINDIR $SUDO install -o0 -g0 -m755 -d "$OLLAMA_INSTALL_DIR/lib/ollama" status "Downloading Linux ${ARCH} bundle" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" if [ "$OLLAMA_INSTALL_DIR/bin/ollama" != "$BINDIR/ollama" ] ; then status "Making ollama accessible in the PATH in $BINDIR" $SUDO ln -sf "$OLLAMA_INSTALL_DIR/ollama" "$BINDIR/ollama" fi # Check for NVIDIA JetPack systems with additional downloads if [ -f /etc/nv_tegra_release ] ; then if grep R36 /etc/nv_tegra_release > /dev/null ; then status "Downloading JetPack 6 components" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}-jetpack6.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" elif grep R35 /etc/nv_tegra_release > /dev/null ; then status "Downloading JetPack 5 components" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}-jetpack5.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" else warning "Unsupported JetPack version detected. GPU may not be supported" fi fi install_success() { status 'The Ollama API is now available at 127.0.0.1:11434.' status 'Install complete. Run "ollama" from the command line.' } trap install_success EXIT # Everything from this point onwards is optional. configure_systemd() { if ! id ollama >/dev/null 2>&1; then status "Creating ollama user..." $SUDO useradd -r -s /bin/false -U -m -d /usr/share/ollama ollama fi if getent group render >/dev/null 2>&1; then status "Adding ollama user to render group..." $SUDO usermod -a -G render ollama fi if getent group video >/dev/null 2>&1; then status "Adding ollama user to video group..." $SUDO usermod -a -G video ollama fi status "Adding current user to ollama group..." $SUDO usermod -a -G ollama $(whoami) status "Creating ollama systemd service..." cat <<EOF | $SUDO tee /etc/systemd/system/ollama.service >/dev/null [Unit] Description=Ollama Service After=network-online.target [Service] ExecStart=$BINDIR/ollama serve User=ollama Group=ollama Restart=always RestartSec=3 Environment="PATH=$PATH" [Install] WantedBy=default.target EOF SYSTEMCTL_RUNNING="$(systemctl is-system-running || true)" case $SYSTEMCTL_RUNNING in running|degraded) status "Enabling and starting ollama service..." $SUDO systemctl daemon-reload $SUDO systemctl enable ollama start_service() { $SUDO systemctl restart ollama; } trap start_service EXIT ;; *) warning "systemd is not running" if [ "$IS_WSL2" = true ]; then warning "see https://learn.microsoft.com/en-us/windows/wsl/systemd#how-to-enable-systemd to enable it" fi ;; esac } if available systemctl; then configure_systemd fi # WSL2 only supports GPUs via nvidia passthrough # so check for nvidia-smi to determine if GPU is available if [ "$IS_WSL2" = true ]; then if available nvidia-smi && [ -n "$(nvidia-smi | grep -o "CUDA Version: [0-9]*\.[0-9]*")" ]; then status "Nvidia GPU detected." fi install_success exit 0 fi # Don't attempt to install drivers on Jetson systems if [ -f /etc/nv_tegra_release ] ; then status "NVIDIA JetPack ready." install_success exit 0 fi # Install GPU dependencies on Linux if ! available lspci && ! available lshw; then warning "Unable to detect NVIDIA/AMD GPU. Install lspci or lshw to automatically detect and install GPU dependencies." exit 0 fi check_gpu() { # Look for devices based on vendor ID for NVIDIA and AMD case $1 in lspci) case $2 in nvidia) available lspci && lspci -d '10de:' | grep -q 'NVIDIA' || return 1 ;; amdgpu) available lspci && lspci -d '1002:' | grep -q 'AMD' || return 1 ;; esac ;; lshw) case $2 in nvidia) available lshw && $SUDO lshw -c display -numeric -disable network | grep -q 'vendor: .* \[10DE\]' || return 1 ;; amdgpu) available lshw && $SUDO lshw -c display -numeric -disable network | grep -q 'vendor: .* \[1002\]' || return 1 ;; esac ;; nvidia-smi) available nvidia-smi || return 1 ;; esac } if check_gpu nvidia-smi; then status "NVIDIA GPU installed." exit 0 fi if ! check_gpu lspci nvidia && ! check_gpu lshw nvidia && ! check_gpu lspci amdgpu && ! check_gpu lshw amdgpu; then install_success warning "No NVIDIA/AMD GPU detected. Ollama will run in CPU-only mode." exit 0 fi if check_gpu lspci amdgpu || check_gpu lshw amdgpu; then status "Downloading Linux ROCm ${ARCH} bundle" curl --fail --show-error --location --progress-bar \ "https://ollama.com/download/ollama-linux-${ARCH}-rocm.tgz${VER_PARAM}" | \ $SUDO tar -xzf - -C "$OLLAMA_INSTALL_DIR" install_success status "AMD GPU ready." exit 0 fi CUDA_REPO_ERR_MSG="NVIDIA GPU detected, but your OS and Architecture are not supported by NVIDIA. Please install the CUDA driver manually https://docs.nvidia.com/cuda/cuda-installation-guide-linux/" # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#rhel-7-centos-7 # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#rhel-8-rocky-8 # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#rhel-9-rocky-9 # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#fedora install_cuda_driver_yum() { status 'Installing NVIDIA repository...' case $PACKAGE_MANAGER in yum) $SUDO $PACKAGE_MANAGER -y install yum-utils if curl -I --silent --fail --location "https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo" >/dev/null ; then $SUDO $PACKAGE_MANAGER-config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo else error $CUDA_REPO_ERR_MSG fi ;; dnf) if curl -I --silent --fail --location "https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo" >/dev/null ; then $SUDO $PACKAGE_MANAGER config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-$1$2.repo else error $CUDA_REPO_ERR_MSG fi ;; esac case $1 in rhel) status 'Installing EPEL repository...' # EPEL is required for third-party dependencies such as dkms and libvdpau $SUDO $PACKAGE_MANAGER -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-$2.noarch.rpm || true ;; esac status 'Installing CUDA driver...' if [ "$1" = 'centos' ] || [ "$1$2" = 'rhel7' ]; then $SUDO $PACKAGE_MANAGER -y install nvidia-driver-latest-dkms fi $SUDO $PACKAGE_MANAGER -y install cuda-drivers } # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#ubuntu # ref: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#debian install_cuda_driver_apt() { status 'Installing NVIDIA repository...' if curl -I --silent --fail --location "https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-keyring_1.1-1_all.deb" >/dev/null ; then curl -fsSL -o $TEMP_DIR/cuda-keyring.deb https://developer.download.nvidia.com/compute/cuda/repos/$1$2/$(uname -m | sed -e 's/aarch64/sbsa/')/cuda-keyring_1.1-1_all.deb else error $CUDA_REPO_ERR_MSG fi case $1 in debian) status 'Enabling contrib sources...' $SUDO sed 's/main/contrib/' < /etc/apt/sources.list | $SUDO tee /etc/apt/sources.list.d/contrib.list > /dev/null if [ -f "/etc/apt/sources.list.d/debian.sources" ]; then $SUDO sed 's/main/contrib/' < /etc/apt/sources.list.d/debian.sources | $SUDO tee /etc/apt/sources.list.d/contrib.sources > /dev/null fi ;; esac status 'Installing CUDA driver...' $SUDO dpkg -i $TEMP_DIR/cuda-keyring.deb $SUDO apt-get update [ -n "$SUDO" ] && SUDO_E="$SUDO -E" || SUDO_E= DEBIAN_FRONTEND=noninteractive $SUDO_E apt-get -y install cuda-drivers -q } if [ ! -f "/etc/os-release" ]; then error "Unknown distribution. Skipping CUDA installation." fi . /etc/os-release OS_NAME=$ID OS_VERSION=$VERSION_ID PACKAGE_MANAGER= for PACKAGE_MANAGER in dnf yum apt-get; do if available $PACKAGE_MANAGER; then break fi done if [ -z "$PACKAGE_MANAGER" ]; then error "Unknown package manager. Skipping CUDA installation." fi if ! check_gpu nvidia-smi || [ -z "$(nvidia-smi | grep -o "CUDA Version: [0-9]*\.[0-9]*")" ]; then case $OS_NAME in centos|rhel) install_cuda_driver_yum 'rhel' $(echo $OS_VERSION | cut -d '.' -f 1) ;; rocky) install_cuda_driver_yum 'rhel' $(echo $OS_VERSION | cut -c1) ;; fedora) [ $OS_VERSION -lt '39' ] && install_cuda_driver_yum $OS_NAME $OS_VERSION || install_cuda_driver_yum $OS_NAME '39';; amzn) install_cuda_driver_yum 'fedora' '37' ;; debian) install_cuda_driver_apt $OS_NAME $OS_VERSION ;; ubuntu) install_cuda_driver_apt $OS_NAME $(echo $OS_VERSION | sed 's/\.//') ;; *) exit ;; esac fi if ! lsmod | grep -q nvidia || ! lsmod | grep -q nvidia_uvm; then KERNEL_RELEASE="$(uname -r)" case $OS_NAME in rocky) $SUDO $PACKAGE_MANAGER -y install kernel-devel kernel-headers ;; centos|rhel|amzn) $SUDO $PACKAGE_MANAGER -y install kernel-devel-$KERNEL_RELEASE kernel-headers-$KERNEL_RELEASE ;; fedora) $SUDO $PACKAGE_MANAGER -y install kernel-devel-$KERNEL_RELEASE ;; debian|ubuntu) $SUDO apt-get -y install linux-headers-$KERNEL_RELEASE ;; *) exit ;; esac NVIDIA_CUDA_VERSION=$($SUDO dkms status | awk -F: '/added/ { print $1 }') if [ -n "$NVIDIA_CUDA_VERSION" ]; then $SUDO dkms install $NVIDIA_CUDA_VERSION fi if lsmod | grep -q nouveau; then status 'Reboot to complete NVIDIA CUDA driver install.' exit 0 fi $SUDO modprobe nvidia $SUDO modprobe nvidia_uvm fi # make sure the NVIDIA modules are loaded on boot with nvidia-persistenced if available nvidia-persistenced; then $SUDO touch /etc/modules-load.d/nvidia.conf MODULES="nvidia nvidia-uvm" for MODULE in $MODULES; do if ! grep -qxF "$MODULE" /etc/modules-load.d/nvidia.conf; then echo "$MODULE" | $SUDO tee -a /etc/modules-load.d/nvidia.conf > /dev/null fi done fi status "NVIDIA GPU ready." install_success
05-14
- 自动安装缺失依赖：`apt-get install -y libssl-dev`（Debian系） 2. **容器运行时检测**： - 优先检查Docker服务状态：`systemctl is-active docker` - 未安装时自动部署containerd运行时 #### 三、GPU支持...
Install Grafana
TinaYu的博客
10-27 191
[root@postgres_vm ~]# yum search grafana Last metadata expiration check: 3:47:10 ago on Mon 26 Oct 2020 09:06:01 PM CST. ====================================== Name Exactly Matched: grafana ====================================== grafana.src : Metrics dashb
2024年最全【yum】linux离线安装rpm包及其依赖和卸载包及其依赖(1)
m0_60388292的博客
05-01 870
先安装并升级，这个U建议加上，因为有些命令安装是有升级的服务的，如果不加U就失败了【比如java】【如何确定哪些包有升级的包，直接在通外网的服务器上yum安装该服务，看过程即可】[root@ccx ~]# rpm -e --nodeps docker-ce-rootless-extras # 这个卸载报错是因为卸载docker-ce的时候一并给卸载了】如果服务器很多的话，可以写个批量拷贝文件的脚本，然后把下面安装离线包的命令放在后面，一并就解压了哦。卸载完毕重新去下载的时候，发现又是9个包了。
Linux中yum、rpm、configure使用介绍
aipoqiu2566的博客
04-09 312
安装程序命令介绍 安装包选择策略：能上外网：yum方式、绿色方式->不能上外网：rpm方式、configure方式 1、yum命令yum安装包时，会包所依赖的包也会安装到系统，将源换成163的源，解决依赖冲突1）列出系统支持安装的rpm包yum list|more例如：yum-plugin-security.noarch 1.1.30-40.el6 base如果包已被安装，则第...
包管理器 - peer dependency 的安装
anleng6817的博客
03-20 4733
npm 和 yarn 安装依赖（包）时不会自动安装 peer dependence（虽然很旧的 npm 是会自动安装的，但几乎没人用那么旧的了），而是给出如下警告： $ npm install --save-dev rollup-plugin-typescript npm WARN rollup-plugin-typescript@1.0.0 requires a peer of tsl...
解决 yum install 命令 --downloadonly 参数出错的方法
睿思达DBA
06-30 9878
解决 yum install 命令 --downloadonly 参数出错的方法 使用 yum 命令可以安装或者更新一个 RPM 包，并且自动解决依赖关系。但有时需要将一个 RPM 包下载到本地计算机，可以使用–downloadonly 参数。 yum 命令可以用来下载一个RPM包，标准的 yum 命令提供了–downloadonly 参数达到这个目的。使用 --downloaddir 参数指定 RPM 存放的目录。 代码如下: $ yum install -y 包名 --downloadonly --do
yum安装出现No package ****** available问题
qq_44430829的博客
02-15 7174
linux centos7 No package openvpn available. Error: Nothing to do
IDEA加载项目时提示Windows Defender might be impacting your build performance
热门推荐
jesseXu的博客
07-20 5万+
IDEA加载项目时提示Windows Defender might be impacting your build performance. IntelliJ IDEA checked the following directories 原因： 这个是提示 windows defender（防火墙） 可能会影响性能，idea检查出下面这些文件夹 ： 一个是idea的设置路径， 一个是代码路径 大概能明白就是idea觉得windows defender 扫描 那两个文件夹会影响性能。看到这里就明白了，把这两
解决No package npm available. Error: Nothing to do
KennyBro的博客
02-08 1829
rpm -Uvh https://archives.fedoraproject.org/pub/archive/epel/6/x86_64/epel-release-6-8.noarch.rpm
使用yum时出现"No package ........ availsble"的解决办法
L_X_Y_HH的博客
03-11 739
今天在使用yum来安装一些小程序时，总是给我报错“No package ........ availsble”，上网找了一下解决办法，这里写出来帮助大家。。。cd /homewget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpmrpm -ivh epel-release-6-8.noarch.rp...
Centos yum 提示No package available 本地库找不到包的解决办法
wenpi51的专栏
08-17 2286
随即在服务器的 /etc/yum.repos.d目录下建议文件microsoft-prod.repo；最后直接使用 sudo yum install aspnetcore-runtime-6.0 安装成功。从本地安装没有问题，本地有 microsoft-prod.repo这个文件；centOS7.6 安装dotnet core 6运行时报错；/etc/yum.repos.d 目录下面的包中是阿里云；
configure: error: You need to install bison
最新发布
11-14
<think> 我们正在解决两个连续出现的错误： 1. 首先遇到了 'Error: Couldn't find the required submodules'，然后 2. 在解决了子模块问题后，运行配置脚本（如./configure）时又遇到了 'configure: error: You need to install bison' 根据引用[2]和引用[3]，我们可以知道bison是一个依赖项，在构建过程中需要安装。引用[2]明确指出在安装Libpcap之前需要安装bison和flex。虽然这里不是安装Libpcap，但错误信息明确提示需要bison。 因此，解决步骤应该是： 1. 确保已经正确获取了Mono的源代码（包括子模块），这可以通过从官方源下载或正确使用git克隆（带子模块）来解决，如之前所述。 2. 安装构建Mono所需的依赖项，其中就包括bison。 具体步骤： 步骤1: 安装bison 在大多数Linux发行版上，可以使用包管理器安装bison。 对于Debian/Ubuntu系统： ```bash sudo apt-get update sudo apt-get install bison ``` 对于CentOS/RHEL系统： ```bash sudo yum install bison ``` 步骤2: 可能还需要安装其他依赖 根据引用[3]中的经验，有时还需要安装其他库，比如libiconv。但错误信息中明确提到的是bison，所以我们先安装bison。如果后续出现其他依赖问题，再按提示安装。 另外，引用[2]中提到bison的安装同时建议安装flex（因为这两个工具经常一起使用）： 在Ubuntu上： ```bash sudo apt-get install flex ``` 步骤3: 重新运行配置脚本 安装完bison后，重新运行Mono源代码目录中的配置脚本： ```bash ./configure ``` 步骤4: 继续构建和安装 配置成功后，进行构建和安装： ```bash make sudo make install ``` 注意：在构建过程中，可能还会遇到其他依赖问题，例如libiconv（如引用[3]所示）或其他库。请根据配置脚本或make过程中的错误提示安装相应的依赖。 预防措施： 在构建Mono之前，建议查看官方文档中关于依赖的部分。通常，Mono的构建需要以下常见依赖（不同系统可能略有不同）： - GCC及其相关开发工具（build-essential, gcc, g++等） - gettext - libgdiplus（用于System.Drawing） - zlib - libtool - automake - autoconf - pkg-config - bison（现在我们知道需要了） - flex（通常和bison一起使用） 在Ubuntu上，可以一次性安装这些依赖： ```bash sudo apt-get install build-essential automake autoconf libtool pkg-config gettext bison flex ``` 在CentOS/RHEL上： ```bash sudo yum groupinstall "Development Tools" sudo yum install bison flex gettext-devel ``` 综上所述，解决第二个错误（关于bison）的方法是安装bison包，并可能还需要安装flex。然后重新运行配置脚本。 如果用户按照这些步骤操作，应该能够解决bison缺失的问题，并继续构建过程。 注意：在引用[1]中，用户遇到了gcc构建的问题，但当前问题不涉及，因此我们专注于解决bison的问题。 最后，在回答中引用相关引用，但注意引用[1]是关于gcc构建错误的，与当前问题无关；引用[2]和[3]则提供了安装bison和解决依赖的思路。 </think>### 解决 "Error: Couldn't find the required submodules" 后出现 "configure: error: You need to install bison" 的解决方案 这个问题是典型的依赖链错误：解决了子模块问题后，在编译配置阶段又发现缺少构建工具 bison。以下是完整解决方案： #### 1. 安装必需的系统依赖 **bison** 是 GNU 语法分析器生成器，用于解析源代码。根据引用[2]的建议，还需要同时安装 **flex**（词法分析器）： ```bash # Ubuntu/Debian 系统 sudo apt-get update sudo apt-get install bison flex libtool autoconf automake # CentOS/RHEL 系统 sudo yum install bison flex libtool autoconf automake ``` #### 2. 安装其他可能的依赖 根据引用[3]，还需安装 **libiconv**（字符编码转换库）： ```bash wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.17.tar.gz tar zxvf libiconv-1.17.tar.gz cd libiconv-1.17 ./configure --prefix=/usr/local make && sudo make install cd .. ``` #### 3. 验证依赖安装 检查工具是否就位： ```bash # 验证 bison 和 flex bison --version # 应显示 3.x 或更高 flex --version # 应显示 2.6.x 或更高 # 设置库路径 export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH ``` #### 4. 重新配置和编译 Mono ```bash # 清理之前的配置缓存 make distclean || ./autogen.sh --clean # 重新配置（添加 iconv 路径） ./configure --prefix=/usr/local LDFLAGS="-L/usr/local/lib" CPPFLAGS="-I/usr/local/include" # 编译安装 make -j$(nproc) sudo make install ``` #### 5. 关键注意事项 - **依赖顺序**：必须按顺序安装依赖：`bison/flex` → `libiconv` → `Mono` - **权限问题**：使用 `sudo` 安装系统级依赖，但编译 Mono 时避免用 root 用户 - **路径冲突**：如之前安装过旧版 Mono，先卸载：`sudo apt remove mono-complete` - **日志分析**：若失败，检查 `config.log` 获取具体错误信息 #### 预防措施 1. **预装所有依赖**： ```bash # Ubuntu sudo apt-get install bison flex libtool autoconf automake libgdiplus gettext cmake ``` 2. **使用官方源**：始终从 [Mono 官方下载页](https://download.mono-project.com/sources/mono/)获取源码 3. **容器化构建**：使用 Docker 保证环境纯净： ```dockerfile FROM ubuntu:22.04 RUN apt-get update && apt-get install -y bison flex build-essential libtool autoconf automake ``` > **重要提示**：引用[1]中出现的 GCC 编译错误通常由依赖缺失引起[^1]。确保所有开发工具链完整：`sudo apt install build-essential`（Ubuntu）或 `sudo yum groupinstall "Development Tools"`（CentOS）。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值