Bug#193838: [Python-Dev] [debian build error]
* Luke Kenneth Casson Leighton <email@example.com> [030521 00:59]:
> On Tue, May 20, 2003 at 11:05:17PM +0200, Matthias Klose wrote:
> > - add /lib to /etc/ld.so.conf before /usr/lib
> > - install the new libgcc1
> > - then upgrade other packages.
> > It seems to be a local problem with your installation, else we had
> > more than one bug report ... I'm downgrading the report to severity
> > important now, tagging it as unreproducible.
> very relieved.
> ... how the hell did /lib not get into ld.so.conf??
> i don't believe i've ever edited ld.so.conf on this system.
doko, please correct me, but according to the manpage of ld.so, neither
/lib nor /usr/lib belong into /etc/ld.so.conf:
The necessary shared libraries needed by the program are
searched for in the following order
o Using the environment variable LD_LIBRARY_PATH
(LD_AOUT_LIBRARY_PATH for a.out programs). Except
if the executable is a setuid/setgid binary, in
which case it is ignored.
o From the cache file /etc/ld.so.cache which contains
a compiled list of candidate libraries previously
found in the augmented library path.
o In the default path /usr/lib, and then /lib.
Indeed, on all machines I checked, /lib was not in /etc/ld.so.conf (nor
was /usr/lib on most machines).
So the real cause for your trouble, Luke, appearently is the presence of
that libgcc1_so file in /usr/lib. AFAICS, adding that /lib line to
ld.so.conf is just a hack to resolve that broken situation on your
Luke, could you run "dpkg -S libgcc |grep so" and send the results ?
Does this list your /usr/lib/libgcc1_s.so.1 file ?