Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] glibc 2.2.5 -> 3.2.1 update probs / sorcery save_libraries

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: julian AT openit.de (Julian v. Bock)
  • To: Source Mage <sm-discuss AT lists.ibiblio.org>
  • Subject: [SM-Discuss] glibc 2.2.5 -> 3.2.1 update probs / sorcery save_libraries
  • Date: Fri, 25 Oct 2002 10:20:27 +0200

Hi

What is the save_libraries function in libsorcery for? I think
this is responsible for the glibc update problems.

save_libraries is called from prepare_install before the make install.
It does the following:

[...]

ldconfig $OLD_LIBS

if [ -z "$LD_LIBRARY_PATH" ]
then export LD_LIBRARY_PATH="$OLD_LIBS"
else export LD_LIBRARY_PATH="$OLD_LIBS:LD_LIBRARY_PATH"
fi

if [ "$SPELL" == "glibc" ] ||
[ "$SPELL" == "glibc-custom" ]; then
ln -sf $OLD_LIBS/ld-$OLD_VERSION.so /lib/ld-linux.so.2
fi

linking $OLD_LIBS/ld-$OLD_VERSION.so to /lib/ld-linux.so.2 is definately
*not* a good idea. this works *only* for the currently executing
subshell, since only this one gets the modified LD_LIBRARY_PATH.

No other shells / programs can execute shared executables since
the old dynamic linker in /lib requires some versioned symbols
found only in the old glibc.

Even if the /lib/ld-* link would be restored after the build this is
not a good idea since in the meantime everything else would be hosed.

Julian




Archive powered by MHonArc 2.6.24.

Top of Page