Solution to "No such file or directory" in locale after installing glibc-2.14 in CentOS6.5

1. Falling into the pit

Recently, a test server (CentOS6.5) within the company needed to upgrade the glibc library to install a certain software. glibc is a core library of Linux. If the original version is directly replaced and upgraded, unpredictable exceptions may occur (such as a large number of commands cannot be run).
So I manually upgraded and installed glibc-2.14, referring to the process of upgrading glibc in Centos6.5 <br /> Downloaded the tarball of glibc-2.14 from the official website, and compiled and installed it according to the above steps:

$ mkdir build // Create a build folder in the glibc-2.14 directory$ cd build // Enter the build directory$ ../configure --prefix=/opt/glibc-2.14 // Note: Configure glibc and set the current glibc-2.14 installation directory$ make && make install // Compile and install the glibc-2.14 library

After modifying the soft link pointing to /lib64/libc.so.6, the program can run normally, but the Chinese characters are garbled .

So, according to my own experience and the opinions of most people on the Internet, I think this is simple. Can't I just reset the language and it will be done?

Just do it, run locale in Shell, and the following error occurs:

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

_Note: The above error occurs not only when running the locale command manually, but also every time you log in to the shell remotely through ssh. _

2. Struggle to no avail

To solve the above problem, I searched a lot on Baidu and G-Dog and tried the following methods, but the problem still exists.

Use the following command:
export LANG="en_US.utf8"
You can modify the environment variable LANG. The modification will take effect immediately. When the system is restarted, the language will return to the original one. There are two other ways to modify the language:
1. Configure the following files:
vi /etc/sysconfig/i18n
Change the original configuration to:
LANG="zh_CN.utf8"
Change to LANG="en_US.utf8"
After saving, it will not take effect immediately, but will take effect after restarting.

3. The impulse of youth

When I was in a state of panic, I went out to smoke for a while. It seems that I should get back to the essence of the problem. Since the error No such file or directory appeared, it means that we have configured a locale that does not exist or is not supported by the system. For example, in the solution above, by changing the language LANG="en_US.UTF-8", the locale is set to zh_CN.UTF-8. When the operating system initialized the localization environment through configuration, it did not find the corresponding language pack (in fact, it is not just the language pack, locale also includes time zone, currency measurement, etc.), that is, OS cannot find the corresponding locale file. It will be easy to solve this problem if you understand it.

First use the locale command to see if there is this locale in the system

[****@****** bin]# locale -a|grep en_US
en_US
en_US.iso88591
en_US.iso885915
en_US.utf8

I was stunned when I saw it. There is en_US.utf8 in it, which means that the OS supports configuring the locale to en_US.utf8. Then why does the following error still appear:

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

4. A ray of hope

Have you overlooked something? Go back to the starting point and examine it again. Suddenly, a question came to mind: we reinstalled a new glibc library instead of overwriting the upgrade, which means that there are at least two locale commands in the system. How does CentOS know which one to use?

Could it be that our newly installed /opt/glibc-2.14/bin/locale is used instead of the system default /usr/bin/locale? This idea can be easily verified with the following command:

[****@****** bin]# /opt/glibc-2.14/bin/locale -a 
C
POSIX

Sure enough, this locale only supports C and POSIX, but not en_US.utf8, so if we configure the locale to en_US.utf8, it will naturally report the No such file or directory error.

The question is, where do the localized language packages listed in the /opt/glibc-2.14/bin/locale command come from? Through a configuration file? Or directly read the files in a directory?
Of course, if you look at the source code, it is easy to find the answer to the above question. Since I am lazy, I will make a bold guess: it should be read from a certain directory, which should contain all the locale files supported by the system. This guess comes from the error message that says "no such file or directory".

In order to find the location of this directory, I thought of the strings command and used the following command directly:

[****@****** bin]# strings /opt/glibc-2.14/bin/locale|grep locale
setlocale
/locale.
locale (GNU %s) %s
/opt/glibc-2.14/lib/locale
/opt/glibc-2.14/share/locale
all-locales
/opt/glibc-2.14/lib/locale/locale-archive
locale: %-15.15s archive: /opt/glibc-2.14/lib/locale/locale-archive
locale: %-15.15s directory: %.*s
Cannot set LC_CTYPE to default locale
Cannot set LC_MESSAGES to default locale
Cannot set LC_COLLATE to default locale
Cannot set LC_ALL to default locale
Write names of available locales
Get locale-specific information.

Sure enough, there is a path /opt/glibc-2.14/lib/locale/locale-archive . From the name, it is easy to guess that this is probably the locale command to read the location of all supported locale directories (or archive files).

5. Problem KO

A ls of the above directory shows that it is indeed empty and there is no archive file called locale-archive.

[****@****** bin]# ll /opt/glibc-2.14/lib/locale/

Now the solution is very simple. Just copy the locale-archive file used by the locale command /usr/bin/locale to /opt/glibc-2.14/lib/locale/locale-archive

[****@****** bin]# cp /usr/lib/locale/locale-archive /opt/glibc-2.14/lib/locale/locale-archive

Some friends may ask, how do you know that the locale file directory used by /usr/bin/locale is /usr/lib/locale/locale-archive? The answer is simple: use Baidu and it is easy to find.

After the copy is completed, exit the session, log in again, and run the /opt/glibc-2.14/bin/locale command again. The No such file or directory error does not appear, and the previous garbled character problem is also solved.

6. Postscript

The above records how I solved the garbled code problem after manually installing the glibc library in the centos 6.5 environment. The process involved some knowledge about the principles of locale, which I also learned by the way.
By the way, the /opt/glibc-2.14/bin/locale command locale reading path guessed above, and later I did look at the locale.c source code and confirmed that it was indeed read from /opt/glibc-2.14/lib/locale/locale-archive (of course there are other reading locations).

This is the end of this article about how to solve the problem of "No such file or directory" in locale after installing glibc-2.14 on CentOS6.5. For more information about how to solve the problem of garbled Chinese characters after installing glibc, please search for previous articles on 123WORDPRESS.COM or continue to browse the related articles below. I hope you will support 123WORDPRESS.COM in the future!