I am running osx 10.9 mavericks and unfortunately DaVinci Resolve no longer works. I think it has a possibility of working as the error message I get is this:
Dyld Error Message:
Library not loaded: #executable_path/../Libraries/libavdevice.dylib
Referenced from: /Applications/DaVinci Resolve.app/Contents/MacOS/Resolve
Reason: Incompatible library version: Resolve requires version 54.0.0 or later, but libavdevice.dylib provides version 52.0.0
I tried downloading ffmpeg and replacing the dylib but that didn't work. Anybody know how to update it?
I suggest using a package management tool Homebrew or MacPorts. My preference is Homebrew.
Alternatively you could install ffmpeg from source and get all the associated libav libraries
Related
idf.py build consistently fails on my windows install of esp-idf, I installed it using the tools provided in espressif's documentation, here are the logs:
Logs
I tried reinstalling to no avail. Other than that I don't know what to do exactly since it always just worked when I used it on linux
As you are use old SDK version please re-clone new sdk and compile it will work fine.
I suggest you to use V4.4 as this sdk is more stable then V5
I tried to use qicli provided in the Naoqi SDK 2.4.3.28 on MacOS (10.12) but it doesn't start:
dyld: Library not loaded: libboost_date_time.dylib
Referenced from: ..../naoqi-sdk-2.4.3.28-mac64/bin/./qicli
Reason: image not found
Abort trap: 6
Anyone knows how to solve this issue?
There are apparently some broken dependencies in the SDK's binaries.
Would you mind having a go at the script here on pastebin? It should fix the dependencies issue for the 2.4.3 SDK. You need to be either on El Capitan or Sierra, with either Xcode7 or Xcode8 installed.
The steps:
run the fix_naoqi.sh script, giving it the full path to naoqi-bin
(e.g. /bin/naoqi-bin)
install opencv using: brew install homebrew/science/opencv
try now
if any problem (you may have if you already installed another NAOqi SDK): export DYLD_LIBRARY_PATH=""
On Mac OS X, the rlink of NAOqi binaries is not performed properly, so you need to specify manually the DYLD_LIBRARY_PATH and DYLD_FRAMEWORK_PATH accordingly to your installation directory when running a binary:
DYLD_LIBRARY_PATH=<installation_directory>/lib DYLD_FRAMEWORK_PATH=<installation_directory> <installation_directory>/bin/qicli
Upgrading to Mavericks, I appear to have broken my Ruby on Rails development environment, which requires ruby 1.9.3 because of various gem dependencies. Within that app directory, I'm trying to reinstall ruby 1.9.3-p547:
rvm reinstall ruby-1.9.3-p547
I then get an error:
checking whether the C compiler works... no
configure: error: in `/Users/dsfaulkenberry/.rvm/src/ruby-1.9.3-p547':
configure: error: C compiler cannot create executables
Looking at the config.log file (~/.rvm/src/ruby-1.9.3-p547/config.log), I see:
dyld: Library not loaded: /usr/local/opt/cloog-ppl015/lib/libcloog.0.dylib
Referenced from: /usr/local/Cellar/gcc46/4.6.4/gcc/libexec/gcc/x86_64-apple-darwin12.4.0/4.6.4/cc1
Reason: image not found
I can see that other people have encountered issues vis-à-vis upgrading to Mavericks and having c compiler issues, but I can't find any referencing this specific library or what I should do (reinstall gcc? is that even a thing I can do?)
Many solutions mention accepting an XCode license agreement, which I have done, and the problem persists.
Reinstalling gcc46 solved the issue for me:
brew uninstall gcc46 && brew install gcc46
This is kind of an ugly one, but I am stuck so here it goes:
I am writing a dynamic library (henceforth 'mylib.dylib') that uses opencv (highgui and other parts) and is ultimately loaded by ffmpeg (libavfilter). The library compiles just fine. But when I try to dlopen() the dylib from within ffmpeg, I get the following error:
mylib.dylib: dlopen(mylib.dylib, 2): Library not loaded: /usr/local/lib/libpng15.15.dylib
Referenced from: /usr/local/lib/libopencv_highgui.2.3.dylib
Reason: Incompatible library version: libopencv_highgui.2.3.dylib requires version 17.0.0 or later, but libpng15.15.dylib provides version 16.0.0
However, when I run otool -L /usr/local/lib/libpng15.15.dylib I get the following:
/usr/local/lib/libpng15.15.dylib:
/usr/local/lib/libpng15.15.dylib (compatibility version 20.0.0, current version 20.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.0.0)
Last time I checked, 20.0.0 is later than 17.0.0, which is what highgui said it requires.
I thought maybe it was an architecture problem (I am on a Mac running Lion, so I've encountered a lot of problems with i386/x86_64), but running 'file' on all of the libraries revealed that everything (highgui, libpng, mylib) is Mach-O 64-bit dynamically linked shared library x86_64
I thought perhaps there was some other version of libpng hiding on my system somewhere, but the dlopen error specifically points to /usr/local/lib/libpng15.15.dylib
There is obviously something that I am missing here -- admittedly I am no expert on how these dynamic libraries link. So if I forgot to include some pertinent info, please excuse me.
UPDATE
I forgot to mention -- the lib works fine when I run ffmpeg through XCode (no dlopen error) which leads me to believe that it might have something to do with a environment variable that XCode is setting that I am not.
Thanks!
SOLUTION
1. Don't be dumb
I was using MAMP and since I was calling ffmpeg through a php script, it was using its own set of dylibs, which (surprise surprise) included libpng 16.0.0
I had something similar recently after I uninstalled all my MacPorts and installed updated versions. The problem was the version of libpng (1.2 vs 1.4 vs 1.5), not just the compatibility version. I had built OpenCV against libpng 1.4 (which is libpng14). I thought I could just use install_name_tool to make it look at libpng 1.5 (libpng15) instead but that didn't work. I ended up rebuilding OpenCV against the current versions of the library. That worked fine (after I remembered sudo cmake install).
(Some version numbers above might be incorrect but the gist is accurate.)
So either you don't have the version of libpng you originally had when you built OpenCV or it built against a libpng other than the one in /usr/local/lib (like maybe the one in /opt/local/lib). If that's the case you'll need to make sure you're building against the version you want to use. How to do that depends on your build method (MacPorts or cmake). I use cmake for OpenCV and MacPorts for other libraries which is why the two got out of sync on my system.
Just for those who need the code:
cd /Applications/MAMP/Library/lib
mv libpng15.15.dylib libpng15.15.dylib_old
ln -s /usr/X11/lib/libpng15.15.dylib .
I am looking to try out clutter (http://www.clutter-project.org) on an OSX machine (10.6). I installed the toolkit first by setting up required dependencies via macports and then installing clutter from source (with needed osx flags).
When I try to compile any sample code, it succeeds. However, I always get a "ClutterGLX-CRITICAL **: Unable to find suitable GL visual." error.
I tried googling for answers but couldn't find anything useful.
Help!
Thanks.
I saw the same problem on my MacBook using the standard build from MacPorts, but the no_x11 variant worked okay for me. I am also using the universal variant because I'm using the library from a 32-bit app, so this is what my MacPorts command line looked like:
sudo port install clutter +universal +no_x11
You can probably omit the '+universal' if you only want the library built for your default architecture.