I will talk about GlibC installation as a continuation of my Pardus days 1 and 2 articles. If you remember, in my Pardus Days -2 article, I told you that I had problems with RAR files and that I could not open RAR parts because the Glibc 2.4 package was not installed.
Now I will tell you about my Glibc installation.. This setup may seem very simple, but it bothered me a lot, I got error after error, but I finally solved it.. It’s been 3 days since I started using Pardus and now Glibc-2.4 or glibc-2.6 is installed…
First of all, we open the Console.
su root
command. It will ask us for the root password.. We enter the root password.
cd /
command to the main directory.
We will switch from this directory to the /usr/src directory.
cd /usr/src
Let’s open a folder named GNU here.
mkdir gnu
then let’s go inside our gnu folder
cd gnu
TEAkolik gnu #
we came to this directory. Now we will download the tar.gz package we need.
Let’s download the glibc package to our system with the wget command.
wget http://ftp.gnu.org/gnu/glibc/glibc -2.4.tar.gz
TEAkolik gnu # wget http://ftp.gnu.org/gnu/glibc/glibc-2.4.tar.gz
–23:54:33– http ://ftp.gnu.org/gnu/glibc/glibc-2.4.tar.gz
=> `glibc-2.4.tar.gz’
ftp.gnu.org resolving… 140.186.70.20
After downloading, let’s open the package.
tar xzvf glibc-2.4.tar.gz
With this command, we opened our package as a folder.
Now, an important note :
For Glibc installation, we need to open a folder named glibc-build and compile in this folder.
Let’s create our build folder right away.
<
mkdir glibc-build
now let’s go inside the build folder for installation.
TEAkolik gnu # mkdir glibc-build
TEAkolik gnu # ls
glibc-2.4 glibc-2.4.tar.gz glibc-build
cd glibc-build
yes, we’ve created a build for installation right now. we got into your lens. We will run the ./configure command in this folder.
BUT : Glibc has a special case for Configure. We have to specify this folder with the default –prefix in whichever directory the Glibc packages are in on your system.
as standard it can be in /usr/local. But sometimes it can be in a directory such as /usr and sometimes /usr/src …. You need to do whatever your system is.
I will specify –prefix=/usr/local as standard.
When in the build folder
../glibc-2.4/configure –prefix=/usr/local
If you don’t type anything after the –prefi= command, then it does the standard installation.
After this process is finished
compiling with the make command we will do. But before the make command, it is necessary to check. Let’s see if there is any mistake.
make check
If you enter the command. If there is a problem during compilation, it will tell you where there is an error in the last 5 lines, what is the problem.. This way, you won’t mess with the system before installation and compilation, like me
If the make check command does not give error warnings as *** on the bottom line..
You can start the compilation by typing make and pressing enter.
My compilation has started, this process may take a while, friends, all you have to do is wait…
I’ve been waiting for 3 minutes.
biittti
nsswitch.c: 79: error: `LIBNSS_FILES_SO’ undeclared here (not in a function)
make[2]: *** [/usr/src/gnu/glibc-build/nss/nsswitch.o] Error 1
make[2]: Leaving directory `/usr/src/gnu/glibc-2.4/nss’
make[1]: *** [nss/subdir_lib] Error 2
make[1]: Leaving directory `/usr/src/gnu/glibc-2.4′
If you get this error, it means there is a problem.
I saw the error, I’ll try to solve it, we’ll write it again when it’s resolved.. Let’s take it easy.