#67663 closed defect (fixed)
neovim @0.9.1: Library not loaded: /opt/local/lib/libmsgpackc.2.dylib
| Reported by: | jrabinow | Owned by: | reneeotten (Renee Otten) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | raimue (Rainer Müller), l2dy (Zero King), judaew (Vadym-Valdis Yudaiev), reneeotten (Renee Otten) | |
| Port: | neovim, msgpack-c |
Description
$ port installed neovim The following ports are currently installed: neovim @0.9.1_0 (active) $ nvim dyld[91470]: Library not loaded: /opt/local/lib/libmsgpackc.2.dylib Referenced from: <916692AD-B038-3EBD-BD78-83B3AB4DCFEC> /opt/local/bin/nvim Reason: tried: '/opt/local/lib/libmsgpackc.2.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libmsgpackc.2.dylib' (no such file), '/opt/local/lib/libmsgpackc.2.dylib' (no such file), '/usr/local/lib/libmsgpackc.2.dylib' (no such file), '/usr/lib/libmsgpackc.2.dylib' (no such file, not in dyld cache) Abort trap: 6 [Exit 134 (ABRT)]
The following workaround allows neovim to be run again
$ sudo port install msgpack-c $ cd /opt/local/lib $ umask 022 $ sudo ln -s libmsgpack-c.2.dylib libmsgpackc.2.dylib
Change History (6)
comment:1 Changed 11 months ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | raimue l2dy judaew reneeotten added |
|---|---|
| Port: | neovim msgpack-c added |
| Summary: | neovim launch failure → neovim @0.9.1: Library not loaded: /opt/local/lib/libmsgpackc.2.dylib |
comment:2 Changed 11 months ago by ryandesign (Ryan Carsten Schmidt)
| Port: | msgpack-cpp added |
|---|
This breaking change is mentioned in the release notes, both for msgpack-c and msgpack-cpp—which I see was also updated, so I suspect it and the ports that depend on it are in the same situation.
comment:3 follow-up: 4 Changed 11 months ago by reneeotten (Renee Otten)
| Port: | msgpack-cpp removed |
|---|
My bad - sorry… I did (attempt to) check the library name but failed to notice the “dash”… I think it should be compatible but there are so few ports that actually depend on it that a revbump of those might be easiest. I’ll try to take a look tonight.
comment:4 Changed 11 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to reneeotten:
there are so few ports that actually depend on it
True. Don't forget to include the (few) ports that depend on msgpack (rather than msgpack-c or msgpack-cpp).
comment:5 Changed 11 months ago by reneeotten (Renee Otten)
| Owner: | set to reneeotten |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:6 Changed 11 months ago by ryandesign (Ryan Carsten Schmidt)
Note: See
TracTickets for help on using
tickets.
Looks like the problem is that the msgpack-c port was updated from 4.0.0 to 6.0.0 a couple days ago and its library name changed from libmsgpackc.2.dylib (without the dash) to libmsgpack-c.2.dylib (with a dash). Therefore, all ports that link with this library need to have their revisions increased to rebuild them.
Alternately, if the new with-dash library is actually binary compatible with the old without-dash library, the msgpack-c port could create the symlink you mentioned to avoid the need to rebuild everything.