Changes between Initial Version and Version 1 of Ticket #55828, comment 6


Ignore:
Timestamp:
Feb 16, 2018, 2:56:02 AM (6 years ago)
Author:
rpspringuel (Fr. Samuel Springuel)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #55828, comment 6

    initial v1  
    11> then allow File type: Dynamic Libraries *dylibs
    22
    3 This step is what made things work.  Without it behavior was the same as before.  Looking more closely, it seems that `/opt/local/lib/libmp3lame.dylib` is a symlink to `/opt/local/lib/libmp3lame.0.dylib` which, as noted in the log @kencu posted, is what actually gets loaded (the lines are the same in my log now).  So it seems that Audacity is having trouble following the symlink.  Why it would have trouble now, but not before, I have no idea.  Further, even though I selected `/opt/local/lib/libmp3lame.dylib` the library location now points specifically to `/opt/local/lib/libmp3lame.0.dylib` which means once it stopped forcing the filename to `libmp3lame.dylib` it could (and did) follow the symlink.  Again, no idea why this change in behavior.
     3This step is what made things work.  Without it behavior was the same as before.  Looking more closely, it seems that `/opt/local/lib/libmp3lame.dylib` is a symlink to `/opt/local/lib/libmp3lame.0.dylib` which, as noted in the logs @kencu and @RJVB posted, is what actually gets loaded (the lines are the same in my log now).  So it seems that Audacity is having trouble following the symlink.  Why it would have trouble now, but not before, I have no idea.  Further, even though I selected `/opt/local/lib/libmp3lame.dylib` the library location now points specifically to `/opt/local/lib/libmp3lame.0.dylib` which means once it stopped forcing the filename to `libmp3lame.dylib` it could (and did) follow the symlink.  Again, no idea why this change in behavior.
    44
    55Numbers in the position of that `0` usually relate to the version number, thus allowing multiple versions to exist side-by-side (with the symlink pointing to the "default"), but LAME reports itself to be in version 3.100 so I'm not sure if that applies in this situation.