Re: pcre library linking issues
On Thu, 19 Apr 2012, Aleksandr Miroslav wrote: On Thu, Apr 19, 2012 at 11:28 AM, Lars Eighner wrote: Create a symbolic link in the library so libpcre.so.0 points to libpcre.so.1 Thank you, this worked. It's a temporary measure, so rebuild everything that wants the old library, then remove the link. ___ 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: pcre library linking issues
On Thu, Apr 19, 2012 at 11:28 AM, Lars Eighner wrote: > Create a symbolic link in the library so libpcre.so.0 points to > libpcre.so.1 Thank you, this worked. Alex ___ 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: pcre library linking issues
On Thu, 19 Apr 2012 10:28:43 -0500 (CDT) Lars Eighner wrote: > The old library should have been moved to a compatibility library so > that things that still depended on it could find it. This did not > happen for some reason. Only portupgrade does that by default. It's an option on portmaster, and unsupported by portmanager. ___ 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: pcre library linking issues
>libpcre.so.0 => not found (0x0) > >What can I do to fix this in the meantime? It should have saved the old one as /usr/local/lib/compat/pkg/libpcre.so.0. If it's there, try this so your programs can find it: # ldconfig -m /usr/local/lib/compat/pkg If it's not there, go get it from your distribution media. R's, John ___ 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: pcre library linking issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/12 11:28 AM, Lars Eighner wrote: > On Thu, 19 Apr 2012, Aleksandr Miroslav wrote: > >> I inadvertently updated my PCRE library and in the process broke >> a number of things that depended on the old library. >> > Not the right answer but works: > > Create a symbolic link in the library so libpcre.so.0 points to > libpcre.so.1 > > The old library should have been moved to a compatibility library > so that things that still depended on it could find it. This did > not happen for some reason. Fortunately, it appears that > libpcre.so.1 is (largely) backwards compatible, so much (all?) of > what depended on it will work if fooled by a symbolic link. Some > upgrades will wipe out the link so it may be necessary to recreate > it until things get straightened out. > Another option that works well is the /etc/libmap.conf file: http://www.freebsd.org/cgi/man.cgi?query=libmap.conf Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+QQ60ACgkQ0sRouByUApDj6QCgtKl1kymoGvmKgy/rE1TOCTxg glUAn0/nq+fmmluDLiM3meAjxdgUJsRZ =H3uc -END PGP SIGNATURE- ___ 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: pcre library linking issues
On Thu, 19 Apr 2012, Aleksandr Miroslav wrote: I inadvertently updated my PCRE library and in the process broke a number of things that depended on the old library. Not the right answer but works: Create a symbolic link in the library so libpcre.so.0 points to libpcre.so.1 The old library should have been moved to a compatibility library so that things that still depended on it could find it. This did not happen for some reason. Fortunately, it appears that libpcre.so.1 is (largely) backwards compatible, so much (all?) of what depended on it will work if fooled by a symbolic link. Some upgrades will wipe out the link so it may be necessary to recreate it until things get straightened out. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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"
pcre library linking issues
I inadvertently updated my PCRE library and in the process broke a number of things that depended on the old library. I now have a number of binaries that look like this: /usr/local/bin$ $ ldd gtester gtester: libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x2809) libintl.so.9 => /usr/local/lib/libintl.so.9 (0x28168000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28171000) libpcre.so.0 => not found (0x0) libc.so.7 => /lib/libc.so.7 (0x28267000) libpcre.so.0 => not found (0x0) What can I do to fix this in the meantime? Alex ___ 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"
