-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LC_RPATH was gone and thus vulkan supported mpv won't start... #13628
Comments
possibly a meson problem? |
i can reproduce the exact same problem. |
Yes, the three of them seems to similar with my problem. Should I have to contact with meson development team? |
Oh, really? Is it come from meson/ninja or install script? Anyway result of |
you can probably open a new issue on the meson issue tracker, though since it has probably already been reported it might be closed. |
seems like it was fixed 3 days ago for now we need to wait for a new release, it will probably be in 1.4.1. |
That's fine to hear. I will wait for next release of meson (1.4.1). Thanks for information... |
meson 1.4.1 has been released and on my end the issue has been fixed. if there are still problems feel free to open a new issue or let me know. |
I've got a similar issue with meson version 1.5.1. This time, two of LC_RPATH exists, but LC_RPATH of /usr/local/lib and LC_RPATH of /usr/local/vulkan/lib have gone... I think these two LC_RPATH should be exists because they exists |
seems like only this commit was added to the previous related code. you probably need to report it to meson. |
I have filed new issue at meson project: mpv won't start with meson install -C build command #13534 Please correct if needed... |
Important Information
Provide following Information:
mpv version
0.37.0-476-g9ac791c329
macOS Version
14.3.1
Source of the mpv binary or bundle
git hub
If known which version of mpv introduced the problem
Not sure
Possible screenshot or video of visual glitches
Since it's a start up issue, there's no screen shot
If you're not using git master or the latest release, update.
Releases are listed here: https://github.com/mpv-player/mpv/releases
Reproduction steps
just run the command
mpv ~/Desktop/video.mp4
Try to reproduce your issue with --no-config first. If it isn't reproducible
with --no-config try to first find out which option or script causes your issue.
Describe the reproduction steps as precise as possible. It's very likely that
the bug you experience wasn't reproduced by the developer because the workflow
differs from your own.
Expected behavior
mpv plays video correctly.
Actual behavior
./mpv ~/Desktop/video.mp4
dyld[13569]: Library not loaded: @rpath/libshaderc_shared.1.dylib
Referenced from: <784E33B7-9C21-3F41-B3BB-7E904A912210> /Volumes/mpv_compile/bin/mpv
Reason: no LC_RPATH's found
Abort trap: 6
After investigation, I found the following:
I am using disk image named mpv_compile, and installing related files into it.
Executable file mpv which is placed in /Volumes/mpv_compile/mpv/build works fine.
The above have LC_RPATH. I checked it with
otool -l | grep -A2 LC_RPATH
Executable file mpv which is placed in /Volumes/mpv_compile/bin, which is created by the command
meson install -C build
does not work.The above does not have LC_RPATH at all. Very funny...
Log file
No log file.
Make a log file made with -v -v or --log-file=output.txt, attach it to
the issue, and replace this text with a link to it.
If you use the Bundle, a default log is created for your last run at
~/Library/Logs/mpv.log. You can jump to that file via the
Help > Show log File… menu.
Without the log file, this issue will be closed for ignoring the issue template.
In the case of a crash, please provide the macOS Crash Report (Backtrace).
Sample files
Sample files needed to reproduce this issue can be attached to the issue
(preferred), or be uploaded to https://0x0.st/ or similar sites.
(Only needed if the issue cannot be reproduced without it.)
Do not use garbage like "cloud storage", especially not Google Drive.
Since it's a start up issue, there's no sample files
The text was updated successfully, but these errors were encountered: