OS 10.6.3 and LAME .dmg installation bug
Posted: Fri Sep 24, 2010 12:13 am
I believe there is a bug in the installer for LAME when doing it under OS 10.6.3 from the .dmg package.
The installer says that it completed the installation successfully but the file simply disappears. I checked the content of the /usr/ folder from Terminal and there is nothing associated with LAME anywhere in it.
Here's what I did to circumvent the problem and get the mp3 dylib installed:
Downloaded the libmp3lame-osx-universal-3.97.zip file (even though it says that it's for an earlier OS version).
Unzipped it
In the folder that opens up, found the "libmp3lame.dylib" file in path: /package/usr/local/lib/libmp3lame.dylib
Relocated the libmp3lame.dylib file to my desktop
From there I was able to direct the application to the correct location for the file using the File/Export browser (my desktop) and install it.
No response to this post is needed unless what I did to circumvent the problem will cause my machine to irreparably smoke itself. Just a note to the developers to review for a possible bug, and anyone else that might benefit from this experience.
Thank you for developing this apparently great product (comment based on my incomplete trial basis at this point), and as Freeware!!!
The installer says that it completed the installation successfully but the file simply disappears. I checked the content of the /usr/ folder from Terminal and there is nothing associated with LAME anywhere in it.
Here's what I did to circumvent the problem and get the mp3 dylib installed:
Downloaded the libmp3lame-osx-universal-3.97.zip file (even though it says that it's for an earlier OS version).
Unzipped it
In the folder that opens up, found the "libmp3lame.dylib" file in path: /package/usr/local/lib/libmp3lame.dylib
Relocated the libmp3lame.dylib file to my desktop
From there I was able to direct the application to the correct location for the file using the File/Export browser (my desktop) and install it.
No response to this post is needed unless what I did to circumvent the problem will cause my machine to irreparably smoke itself. Just a note to the developers to review for a possible bug, and anyone else that might benefit from this experience.
Thank you for developing this apparently great product (comment based on my incomplete trial basis at this point), and as Freeware!!!