Hi! At 15 Jan 2004 12:36:38 -0500, Camm Maguire wrote: > This bug affects several packages, so lets take lapack-dev as an > example. In the package itself, the link reads > > liblapack.so -> liblapack.so.2 > > where the latter, provided in the lapack package, reads > > liblapack.so.2 -> liblapack.so.2.0 (a file) > > This is the normal setup. In addition, lapack-dev provides an > *alternative* link
That's OK. > liblapack2.so -> /etc/alternatives/liblapack2.so > > which is set via the alternative mechanism to one of several choices, > e.g. > > /etc/alternatives/liblapack2.so -> /usr/lib/liblapack.so > > The problem is now that ldconfig will be run, and will change these > links. In woody, these links are rewritten to their original values, > and everything works. Could you explain what "original value" is? > In sid, ldconfig rewrites the first link as > follows: > > liblapack.so -> liblapack2.so > > creating a link circle. Where is liblapack.so placed? Could you explain us the complete symlink path? BTW, > > > $ nm -D /usr/lib/liblapack.so > > > nm: /usr/lib/liblapack.so: Too many levels of symbolic links This is Linux kernel VFS limititation, it cannot handle over 5 level symlinks. In this case, what behavior do you want to see? Please explain in detail step-by-step. Regards, -- gotom
