Brave Search

Can't install glibc and glibc-common cause they need each other

unix.stackexchange.com › questions › 314179 › cant-install-glibc-and-glibc-common-cause-they-need-each-other

Where packages are co-dependent you need to install them together like this:

# rpm -i glibc-2.17-105.el7.i686.rpm glibc-common-2.17-105.el7.x86_64.rpm

Answer from Flup on Stack Exchange

RPMfind

rpmfind.net › linux › rpm2html › search.php

RPM resource glibc-common

The glibc-common package includes common binaries for the GNU libc libraries, as well as national language (locale) support.

CERN

linuxsoft.cern.ch › cern › centos › 7 › updates › x86_64 › repoview › glibc-common.html

glibc-common

The glibc-common package includes common binaries for the GNU libc libraries, as well as national language (locale) support.

Discussions

rhel - Can't install glibc and glibc-common cause they need each other - Unix & Linux Stack Exchange

I am working on RHEL 7.2 and I want to install LibXp.so.6 and LibXmu.so.6, but I have problem with glibc-common-2.17-105.el7.x86_64.rpm and glibc-2.17-105.el7.i686.rpm because they need each other. [ More on unix.stackexchange.com

unix.stackexchange.com

October 4, 2016

rpm - How is the "glibc-common" dependency of "glibc.i686" in OracleLinux 8.6 fulfilled? - Unix & Linux Stack Exchange

OracleLinux 8.6 contains the 32-bit package glibc-2.28-189.1.0.1.el8.i686.rpm. This package requires glibc-common in exactly that version: $ rpm -qpv --requires glibc-2.28-189.1.0.1.el8.i686.rpm ... More on unix.stackexchange.com

unix.stackexchange.com

September 28, 2022

rhel - How to downgrade glibc-common from 2.17-260.el7 to 2.17-222.el7 - Unix & Linux Stack Exchange

I am trying to install gcc on my RHEL 7.6 Beta workstation. At the moment, I am doing it using the command yum install gcc, but I keep receiving this error: --> Finished Dependency Resolution E... More on unix.stackexchange.com

unix.stackexchange.com

September 15, 2018

Glibc Error

Hello u/Bad-Mouse Indeed, for rhel8, I can see this version of package, but it should be x86_64 https://access.redhat.com/downloads/content/glibc-common/2.28-251.el8_10.11/x86_64/fd431d51/package For i686, I can see this package only up to rhel6 https://access.redhat.com/downloads/content/glibc-common/2.12-1.212.el6_10.3/i686/fd431d51/package and checking the rhel8 # yum list --showduplicates glibc-common Updating Subscription Management repositories. Last metadata expiration check: 3:20:13 ago on Tue 28 Jan 2025 03:40:18 AM UTC. Installed Packages glibc-common.x86_64 2.28-251.el8_10.5 @rhel-8-for-x86_64-baseos-rpms Available Packages glibc-common.x86_64 2.28-42.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-42.el8_0.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-72.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-72.el8_1.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-101.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-127.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-127.el8_3.2 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-151.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-164.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-164.el8_5.3 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-189.1.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-189.5.el8_6 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-211.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-225.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-225.el8_8.6 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8.7 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8_9.12 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8_9.13 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.2 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.4 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.5 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.11 rhel-8-for-x86_64-baseos-rpms Based on the info above, I believe that your package was installed .. maybe from some 3rd party repo, and unless you really need it, I would recommend you to remove it. But a better advice, if you do have a valid subscription, feel free to open a support case, and also feel free to attach the info above, this will speed up the process. I hope this helps! More on reddit.com

r/redhat

9

2

January 28, 2025

Fedora

packages.fedoraproject.org › pkgs › glibc › glibc-common

glibc-common - Fedora Packages

The glibc-common package includes common binaries for the GNU libc libraries, as well as national language (locale) support.

CentOS Repositories

centos.pkgs.org › 7 › centos-x86_64 › glibc-common-2.17-317.el7.x86_64.rpm.html

glibc-common-2.17-317.el7.x86_64.rpm - CentOS Repositories

The glibc-common package includes common binaries for the GNU libc libraries, as well as national language (locale) support.

Pkgs.org

pkgs.org › download › glibc-common

Glibc-common Download for Linux (rpm)

Download glibc-common linux packages for AlmaLinux, Amazon Linux, CentOS, Fedora, Rocky Linux

Stack Exchange

unix.stackexchange.com › questions › 314179 › cant-install-glibc-and-glibc-common-cause-they-need-each-other

rhel - Can't install glibc and glibc-common cause they need each other - Unix & Linux Stack Exchange

Top answer

1 of 1

7

Where packages are co-dependent you need to install them together like this:

# rpm -i glibc-2.17-105.el7.i686.rpm glibc-common-2.17-105.el7.x86_64.rpm

GitHub

github.com › openembedded › openembedded-core › blob › master › meta › recipes-core › glibc › glibc-common.inc

openembedded-core/meta/recipes-core/glibc/glibc-common.inc at master · openembedded/openembedded-core

SUMMARY = "GLIBC (GNU C Library)" DESCRIPTION = "The GNU C Library is used as the system C library in most systems with the Linux kernel." HOMEPAGE = "http://www.gnu.org/software/libc/libc.html" SECTION = "libs" LICENSE = "GPL-2.0-only & LGPL-2.1-or-later" ·

Author openembedded

Stack Exchange

unix.stackexchange.com › questions › 719051 › how-is-the-glibc-common-dependency-of-glibc-i686-in-oraclelinux-8-6-fulfille

rpm - How is the "glibc-common" dependency of "glibc.i686" in OracleLinux 8.6 fulfilled? - Unix & Linux Stack Exchange

Top answer

1 of 1

1

Yes, the 64-bit version of glibc-common satisfies the 32-bit glibc dependency. It can’t however be a noarch package because it contains “common binaries for the GNU libc libraries, as well as national language (locale) support” — which means that its contents vary on each architecture where it is built.

RHEL 8 and its derivatives only support 64-bit platforms, so the only scenario in which you can install glibc.i686 is as a 32-bit variant of glibc.x86_64. The resolver will consider “main architecture” packages if a same-architecture dependency isn’t available; in this specific case, the dependency will already be resolved anyway, there won’t be anything more to install.

Find elsewhere

Google Bing Mojeek

Anaconda.org

anaconda.org › anaconda › glibc-common-amzn2-aarch64

glibc-common-amzn2-aarch64 - anaconda | Anaconda.org

The glibc-common package includes common binaries for the GNU libc libraries, as well as national language (locale) support.

LinuxQuestions.org

linuxquestions.org › questions › linux-newbie-8 › yum-dependencies-resolution-fail-glibc-common-4175582316

[SOLVED] Yum Dependencies resolution fail (glibc-common)

June 15, 2016 - Hello, I'm trying to install gcc on my XenServer 7.0 (based on CentOS). But I get some problems with dependencies When I install with yum, I get: Code:

RPMfind

rpmfind.net › linux › rpm2html › search.php

RPM resource glibc-common(x86-64)

The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet · The System and Arch are optional added filters, for example ...

Pkgs

oraclelinux.pkgs.org › 8 › ol8-baseos-latest-x86_64 › glibc-common-2.28-42.0.1.el8.x86_64.rpm.html

glibc-common-2.28-42.0.1.el8.x86_64.rpm

We cannot provide a description for this page right now

SysTutorials

systutorials.com › how-to-install-glibc-glibc-common-and-gd-libraries-independently

Installing Glibc, Glibc-common, And GD Libraries Separately - SysTutorials

April 12, 2026 - Installing glibc, glibc-common, and GD Libraries Separately tagged Bash.

Red Hat

access.redhat.com › discussions › 5130441

Red Hat Customer Portal - Access to 24x7 support and knowledge

RPMS glibc-headers-2.17-292.el7.i686.rpm glibc-common-2.17-292.el7.i686.rpm

Stack Exchange

unix.stackexchange.com › questions › 469187 › how-to-downgrade-glibc-common-from-2-17-260-el7-to-2-17-222-el7

rhel - How to downgrade glibc-common from 2.17-260.el7 to 2.17-222.el7 - Unix & Linux Stack Exchange

Top answer

1 of 1

3

I was able to find the solution. After learning a little me more about the platform, the command required to downgrade the glibc package is:

yum -y downgrade glibc glibc-common

In my case, it downgraded glibc from 2.17-260.el7 to 2.17-222.el7.

This method can be apply to any package as long it exists in your repositories. You can double check the different versions for a specific package with the command:

yum list --showduplicates <package_name>

Pbone

rpm.pbone.net › results_limit_8_srodzaj_3_dl_40_search_glibc-common.html

RPM Search glibc-common

RPM Search glibc-common

GitHub

gist.github.com › harv › f86690fcad94f655906ee9e37c85b174

update glibc to 2.17 for CentOS 6 · GitHub

Error: Package: libstdc++-devel-4.4.7-23.el6.x86_64 (@base) Requires: libstdc++(x86-64) = 4.4.7-23.el6 Removing: libstdc++-4.4.7-23.el6.x86_64 (@base) libstdc++(x86-64) = 4.4.7-23.el6 Updated By: libstdc++-4.8.5-44.el7.x86_64 (/libstdc++-4.8.5-44.el7.x86_64) libstdc++(x86-64) = 4.8.5-44.el7 You could try using --skip-broken to work around the problem ** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows: glibc-2.12-1.212.el6_10.3.i686 has missing requires of glibc-common = ('0', '2.12', '1.212.el6_10.3') glibc-2.17-55.el6.x86_64 is a duplicate with glibc-2.12-1.212.el6_10.3.i686

Red Hat

access.redhat.com › ja › solutions › 1335543

glibc-* アップデートでカスタムロケールを保存する - Red Hat Customer Portal

glibc-* を更新する時にカスタムロケールを保存するにはどうしたら良いですか? glibc-* を更新すると、カスタマイズしたロケール情報が削除されるのはなぜですか? glibc-common を再インストールした後、カスタムロケールを保存するにはどうしたら良いですか? glibc と依存パッケージをアップデートすると、# locale -a の出力からロケール情報がなくなります。 # localedef -f WINDOWS-31J -i ja_JP ja_JP.SJIS # locale -a | grep ja ja_JP ja_JP.eucjp ja_JP.sjis

reddit.com › r/redhat › glibc error

r/redhat on Reddit: Glibc Error

January 28, 2025 -

I’m trying to update a RHEL 8 machine with dnf and I’m getting a dependency error for glibc-2.28-251.el8_10.11.i686

It needs glibc-common-2.28-251.el8_10.11.i686.

If I browse Red Hat’s baseos repository, I don’t see it in there. Do you think maybe it hasn’t been added yet or do I have something else wrong? Thanks,

dnf repoquery --requires glibc.i686 says it needs glibc-common with a matching version-release, but doesn't specify the arch. AFAICS, glibc-common.x86_64 should work fine here, and it does install for me in a container, at least.