Public SourceMage Discussion List

[Dufflebunk <dufflebunk AT dufflebunk.homeip.net>]

My guess is that it's there to let the script continue running commands 
when the libs the commands use have been moved (before the new versions 
have been copied in). I don't know much about shared libs though... ctuly 
almost nothing at all about how they work, so take that with a large grain 
of salt.

On Fri, 25 Oct 2002, Julian v. Bock wrote:

> 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
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> 

-- 


Quidquid latine dictum sit, altum sonatur. 
-----------------
PGP public key at 
http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0x3327A9A5
F1