Opened 2 years ago
Last modified 2 years ago
#65298 assigned defect
kid3 @3.9.1: included libkid3-core.dylib "seems to be referenced using a relative path"
Reported by: | GregJGitHub | Owned by: | judaew (Vadym-Valdis Yudaiev) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.2 |
Keywords: | bigsur x86_64 | Cc: | |
Port: | kid3 |
Description
$ port install kid3
==> fails w/ a 1 broken file
$ port -s install kid3
==> fails w/ a broken file
$ port -d -y rev-upgrade
==> (log is attached)
Attachments (1)
Change History (4)
Changed 2 years ago by GregJGitHub
Attachment: | kid3_@3.9.1_BigSur_broken-file.txt added |
---|
comment:1 Changed 2 years ago by jmroot (Joshua Root)
Cc: | judaew@… removed |
---|---|
Owner: | set to judaew |
Status: | new → assigned |
comment:2 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
This is presumably an internal library used by the program. If the program works, then presumably this isn't really a problem and can be ignored (by the user). It would still be a good idea (for the maintainer) to fix it to appease rev-upgrade.
comment:3 Changed 2 years ago by judaew (Vadym-Valdis Yudaiev)
Hi Ryan,
I would like to correct this mistake, but I do not know exactly how. The port
tells me that I can use install_name_tool for it, but I don't know exactly how to use it in this case. Do you have any suggestions?
Could not open libkid3-core.dylib: Error opening or reading file (referenced from /Applications/MacPorts/kid3.app/Contents/MacOS/libkid3-gui.dylib) libkid3-core.dylib seems to be referenced using a relative path. This may be a problem with its canonical library name and require the use of install_name_tool(1) to fix.
Note: See
TracTickets for help on using
tickets.
terminal log of "$ port -d -y rev-upgrade" & "$ port -s install kid3"