The paths are hard coded and once compiled into a lib/binary, and have nothing to do with the environment which is correct.
BillK On Sun, 2004-02-08 at 23:08, Arne Vogel wrote: > William Kenworthy wrote: > From your ldd output, I don't see why your /usr/bin/python should use > hard coded paths; when I run ldd /usr/bin/python, I get: > That doesn't look so different from your ldd's output, except for > linux-gate.so.1, which is required by libgcc_s.so.1, the relocation > addresses (I guess? ldd's docs don't mention this) and that your > libgcc_s.so.1 resolves to the old gcc's path (and this is the only > important difference). > -- [EMAIL PROTECTED] mailing list
