Skip to main content
Fixed English, removed unnecessary bullet point, clarified important warning.
Source Link

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install

Following this process, You'llyou'll be able to build glibc 2.14 but It might not working unless it's exposedyou will need to programtell the compiler where to look for which you are upgrading glibc.

Below are the ways you can expose the glibc to your program.

  1. LD_LIBRARY_PATH=/opt/glibc-2.14/lib

    export LD_LIBRARY_PATH.

    LibraryThe library is exposed during your current login session.

  2. You can permanently link your new glibc version like so, but please read the WARNING below:

    ln -sf /opt/glibc-2.14/glibc-2.14.so /lib/libc.so.6.

    Since libc.so.6 is just a symbolic link. Executing above command will make the link pointing towards new glibc library. But this step is not recommended since there are many programs in Linux which are dependent on older version will stop behaving expectedly.

  3. Don't play with glibc, it will break your Linux system. Not to mention, Linux is self destructive. Be careful.

Since libc.so.6 is just a symbolic link. Executing the above command will make the link point towards the new glibc library. However this step is not recommended since there are many programs in Linux which depend on older versions and will stop working.

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install

Following this process, You'll be able to build glibc 2.14 but It might not working unless it's exposed to program for which you are upgrading glibc.

Below are the ways you can expose the glibc to your program.

  1. LD_LIBRARY_PATH=/opt/glibc-2.14/lib

    export LD_LIBRARY_PATH.

    Library is exposed during your current login session.

  2. ln -sf /opt/glibc-2.14/glibc-2.14.so /lib/libc.so.6.

    Since libc.so.6 is just a symbolic link. Executing above command will make the link pointing towards new glibc library. But this step is not recommended since there are many programs in Linux which are dependent on older version will stop behaving expectedly.

  3. Don't play with glibc, it will break your Linux system. Not to mention, Linux is self destructive. Be careful.

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install

Following this process, you'll be able to build 2.14 but you will need to tell the compiler where to look for glibc.

Below are the ways you can expose the glibc to your program.

  1. LD_LIBRARY_PATH=/opt/glibc-2.14/lib

    export LD_LIBRARY_PATH.

    The library is exposed during your current login session.

  2. You can permanently link your new glibc version like so, but please read the WARNING below:

    ln -sf /opt/glibc-2.14/glibc-2.14.so /lib/libc.so.6.

Since libc.so.6 is just a symbolic link. Executing the above command will make the link point towards the new glibc library. However this step is not recommended since there are many programs in Linux which depend on older versions and will stop working.

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install

Following this process, You'll be able to build glibc 2.14 but It might not working unless it's exposed to program for which you are upgrading glibc.

Below are the ways you can expose the glibc to your program.

  1. LD_LIBRARY_PATH=/opt/glibc-2.14/lib

    export LD_LIBRARY_PATH.

    Library is exposed during your current login session.

  2. ln -sf /opt/glibc-2.14/glibc-2.14.so /lib/libc.so.6.

    Since libc.so.6 is just a symbolic link. Executing above command will make the link pointing towards new glibc library. But this step is not recommended since there are many programs in Linux which are dependent on older version will stop behaving expectedly.

  3. Don't play with glibc, it will break your Linux system. Not to mention, Linux is self destructive. Be careful.

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install

Following this process, You'll be able to build glibc 2.14 but It might not working unless it's exposed to program for which you are upgrading glibc.

Below are the ways you can expose the glibc to your program.

  1. LD_LIBRARY_PATH=/opt/glibc-2.14/lib

    export LD_LIBRARY_PATH.

    Library is exposed during your current login session.

  2. ln -sf /opt/glibc-2.14/glibc-2.14.so /lib/libc.so.6.

    Since libc.so.6 is just a symbolic link. Executing above command will make the link pointing towards new glibc library. But this step is not recommended since there are many programs in Linux which are dependent on older version will stop behaving expectedly.

  3. Don't play with glibc, it will break your Linux system. Not to mention, Linux is self destructive. Be careful.

Source Link
mikel
  • 91
  • 1
  • 4

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install