Hi Steve, I am not an Debian expert, so somebody can explain the thing better than me: On 64bit Debian /usr/lib64 is symlinked to /usr/lib, so it should not really matter.
But the Debian installer files have the lib path hardcoded, where to look for the compiled files. These installer files are architecture independent. (The binaries and libs are first created in a sub-directory and when successfull, copied to the package or filesystem.) In your case thedebian installer could not find the temporary files, because they were in lib4 and not in lib. Maybe somebody can explain it better than me, On 6/27/07, Steve Underwood <[EMAIL PROTECTED]> wrote: > Hi all, > > Can anyone tell me what is supposed to happen with the library > directories on x86_64 Debian? There are complaints that spandsp installs > the library in lib64 instead of lib. I only install in lib64 if there > seems to be a lib64 directory on the system. Is there some useless > leftover lib64 on some Debian systems? I have no clear idea have to > reliably detect where to stick the damned thing. > > Steve > > _______________________________________________ > Callweaver-users mailing list > [email protected] > http://lists.callweaver.org/mailman/listinfo/callweaver-users > _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
