fxscintilla installs the following .so and sym links: /usr/lib64/libfxscintilla-1.6.so -> libfxscintilla-1.6.so.18.1.1 /usr/lib64/libfxscintilla-1.6.so.18 -> libfxscintilla-1.6.so.18.1.1 /usr/lib64/libfxscintilla-1.6.so.18.1.1 When building dev-ruby/fxruby it tries to link to /usr/lib64/libfxscintilla.so without the -1.6 and so fails. One can easily "fix" this by adding the sym link manually: ln -sf libfxscintilla-1.6.so libfxscintilla.so but obviously this needs to be fixed. Either fxscintilla should install the sym link or fxruby should link against libfxscintilla-1.6.so. I'm not sure who to blame here since I'm not familiar with either package. This does seem to have come up with the recent ruby upgrades. Reproducible: Always
ping?
Same here. I guess there is no need to slot fxscintilla.
This is a left-over from the days when fxscintilla was supposed to support multiple fox versions. The behavior changed in fxscintilla-2.28.0 to only link against the most recent fox. Can you please try with a newer version? I will file a stable request shortly, they have been too long in ~arch anyway.
(In reply to Matti Bickel from comment #3) > This is a left-over from the days when fxscintilla was supposed to support > multiple fox versions. The behavior changed in fxscintilla-2.28.0 to only > link against the most recent fox. > > Can you please try with a newer version? I will file a stable request > shortly, they have been too long in ~arch anyway. ~arch fxruby (1.6.28) links fine only against ~arch x11-libs/fxscintilla (3.3.5) and fails against stable (might need some dep tuning to make it clear). Otherwise looks fine.
I've just removed anything but fxscintilla-3.3.5, so this should be fine now.
