- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't think this is a bug. The script setup the runtime enviroment for Intel compiler built binaries since our libraries are located in the system default lib directory. Note that you would see the same issue with the default system lib.
intels-mac-pro:~ ale$ otool -L libstdc++.6.dylib
otool: can't open file: libstdc++.6.dylib (No such file or directory)
intels-mac-pro:~ ale$ otool -L /usr/lib/libstdc++.6.dylib
/usr/lib/libstdc++.6.dylib:
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
intels-mac-pro:~ ale$ otool -L libimf.dylib
otool: can't open file: libimf.dylib (No such file or directory)
intels-mac-pro:~ ale$ otool -L /opt/intel/composerxe-2011.1.122/compiler/lib/libimf.dylib
/opt/intel/composerxe-2011.1.122/compiler/lib/libimf.dylib:
libimf.dylib (compatibility version 0.0.0, current version 0.0.0)
libintlc.dylib (compatibility version 1.0.0, current version 1.11.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.3)

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page