/usr/local/lib/compat and /usr/local/lib/compat/pkg
The other night I spent some frustrating time discovering that after updating from 7.2 to 8.1, for some reason some of the libraries in /usr/local/lib/compat/pkg were 32 bit on my 64 bit system which was causing several of my binaries to generate unsupported filesystem layout errors. I ended up copying the ones from /usr/local/lib/compat into /usr/local/lib/compat/pkg which seemed to fix the problem. Will this solution end up hurting me? Was there an official pathname change to phase out the pkg directory at some point that might warrant updating all of my packages (which I forgot to do)? -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org http://www.netmusician.org j...@netmusician.org mailto:j...@netmusician.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /usr/local/lib/compat and /usr/local/lib/compat/pkg
In the last episode (Oct 21), Joe Auty said: The other night I spent some frustrating time discovering that after updating from 7.2 to 8.1, for some reason some of the libraries in /usr/local/lib/compat/pkg were 32 bit on my 64 bit system which was causing several of my binaries to generate unsupported filesystem layout errors. I ended up copying the ones from /usr/local/lib/compat into /usr/local/lib/compat/pkg which seemed to fix the problem. Did you also do a 32- 64-bit migration at some point? You probably should have moved everything in /usr/local/lib/compat to /usr/local/lib32 then to avoid problems. 32-bit apps shouldn't look for their shlibs in /usr/local/lib on a 64-bit system. You can manually move any remaining ones by using the file command to identify 32-bit files, then moving them (or removing them if you have no 32-bit apps anymore). -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /usr/local/lib/compat and /usr/local/lib/compat/pkg
Dan Nelson wrote: In the last episode (Oct 21), Joe Auty said: The other night I spent some frustrating time discovering that after updating from 7.2 to 8.1, for some reason some of the libraries in /usr/local/lib/compat/pkg were 32 bit on my 64 bit system which was causing several of my binaries to generate unsupported filesystem layout errors. I ended up copying the ones from /usr/local/lib/compat into /usr/local/lib/compat/pkg which seemed to fix the problem. Did you also do a 32- 64-bit migration at some point? You probably should have moved everything in /usr/local/lib/compat to /usr/local/lib32 then to avoid problems. 32-bit apps shouldn't look for their shlibs in /usr/local/lib on a 64-bit system. You can manually move any remaining ones by using the file command to identify 32-bit files, then moving them (or removing them if you have no 32-bit apps anymore). Nope, there was never a 32 - 64 bit migration or vice versa. However, doing a: file /usr/local/lib/compat/pkg/libcrypt.so.4 indicated that several of these libraries in compat/pkg were i386 rather than amd64. -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org http://www.netmusician.org j...@netmusician.org mailto:j...@netmusician.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
