Hi, On Wed, Feb 01, 2017 at 08:48:50AM -0600, Christopher Stone wrote: > Here's the warning/failure notice: > > ------------------------------------------------------------------------------------------- > Warning: found dylibs in your /usr/local/lib directory. These are known to > cause problems. We'd recommend you remove them. > Checking for dylibs in /usr/local/lib... [FAILED] > ------------------------------------------------------------------------------------------- > > Here are the related files: > > ------------------------------------------------------------------------------------------- > > /usr/local/lib/ > > ├── libosxfuse.2.dylib -> libosxfuse_i64.2.dylib > ├── libosxfuse.dylib -> libosxfuse_i64.dylib > ├── libosxfuse.la -> libosxfuse_i64.la > ├── libosxfuse_i32.2.dylib > ├── libosxfuse_i32.dylib -> libosxfuse_i32.2.dylib > ├── libosxfuse_i32.la > ├── libosxfuse_i64.2.dylib > ├── libosxfuse_i64.dylib -> libosxfuse_i64.2.dylib > ├── libosxfuse_i64.la > └── pkgconfig > ├── fuse.pc -> osxfuse.pc > └── osxfuse.pc > > 1 directory, 11 files > > ------------------------------------------------------------------------------------------- > > I have the FUSE for OS X (OSXFUSE) Preference Pane on my system, and > believe ExpanDrive and perhaps one or two more utilities use it.
Those likely ship osxfuse. > The thing I find most odd about this are all the symlinks. That's normal. This is a fairly standard library setup. > Is this in fact a problem I should address? This can be a problem when you build ports that use osxfuse. You can use trace mode (port -t ...) when you suspect it is a problem. -- Clemens
