This is the list of dylibs:
/usr/local/lib/CHBrowserView.dylib
/usr/local/lib/ libgnsdk_musicid_file.dylib
/usr/local/lib/libgnsdk_sdkmanager.dylib
/usr/local/lib/libjson.0.0.1.dylib
/usr/local/lib/libmusicid_osx.dylib< br />/usr/local/lib/libpcre.0.0.1.dylib
/usr/local/lib/libpcrecpp.0.0.0.dylib
/usr/local/lib/libpcreposix.0.0. 0.dylib
For Brew, this is an annoying and conceited error message, assuming that any library in /usr/local/lib is “evil” because Brew doesn’t understand them .
You may have an “old” version that conflicts with something Brew built, but… uh. This will be obvious when the program dies. And if the application tries to uninstall it, then it may also be worse, which also means that when Brew is building it, it will try to connect with the old lib. As long as its arch/version is compatible, this is not a biggie.
This is also obvious when the shared library you deleted cannot be found when you create a pre-brew. And take into account that you may not have a source (or remember how you configure it in the first place).
I strongly recommend keeping the old library.
I just installed homebrew and saw a message from the installation script stating that I should consider removing the following “evil” dylibs because they might break the build. Has anyone done this? If so, will you find out later that you really need them?
This is the list of dylibs:
/usr/local/lib/CHBrowserView.dylib
/usr/local/lib/ libgnsdk_musicid_file.dylib
/usr/local/lib/libgnsdk_sdkmanager.dylib
/usr/local/lib/libjson.0.0.1.dylib
/usr/local/lib/libmusicid_osx.dylib< br />/usr/local/lib/libpcre.0.0.1.dylib
/usr/local/lib/libpcrecpp.0.0.0.dylib
/usr/local/lib/libpcreposix.0.0. 0.dylib
No. If you have something in /usr/local/lib, it’s probably because you built and installed it.
For Brew, this is an annoying and conceited error message, assuming that any library in /usr/local/lib is “evil” because Brew doesn’t understand them .
You may have an “old” version that conflicts with something Brew built, but… uh. This will be obvious when the program dies. And if the application tries to uninstall it, then it may also be worse, which also means that when Brew is building it, it will try to connect with the old lib. As long as its arch/version is compatible, this is not a biggie.
This is also obvious when the shared library you deleted cannot be found when you create a pre-brew. And take into account that you may not have a source (or remember how you configure it in the first place).
I strongly recommend keeping the old library.