I just discovere something weird. As usual I rebuild every stable pkgsrc
branch by updating via pkg_comp. I just wanted to run graphics/geeqie
for the first time after I did that, and I got this error message:
(geeqie:23541): Clutter-CRITICAL **: Unable to initialize Clutter: Failed to
dynamically open the GL library "libGL.so.1"
and geeqie failed to run.
Now indeed I don't have such library but I do have libGL.so.2 from X in
the base system. I also noticed at some point that MesaLib wasn't
compiled any more. I thought that apparently nothing needed it any more.
However, after I manually installed graphics/MesaLib, geeqie worked
again.
Looking at grapics/clutter, it has the x11 option turned on:
.../pkgsrc/graphics/clutter$ make show-options
Any of the following general options may be selected:
introspection Enable GObject Introspection support.
x11 Enable X11 support.
These options are enabled by default:
x11
These options are currently enabled:
x11
You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or PKG_OPTIONS.clutter.
"options.mk" contains this part:
.if !empty(PKG_OPTIONS:Mx11)
PLIST.x11= yes
CONFIGURE_ARGS+= --enable-x11-backend
CONFIGURE_ARGS+= --with-imagebackend=gdk-pixbuf
CONFIGURE_ARGS+= --enable-xinput
BUILDLINK_API_DEPENDS.MesaLib+= MesaLib>=7.0
.include "../../graphics/MesaLib/buildlink3.mk"
.include "../../x11/libX11/buildlink3.mk"
.include "../../x11/libXdamage/buildlink3.mk"
.include "../../x11/libXfixes/buildlink3.mk"
.include "../../x11/libXcomposite/buildlink3.mk"
.include "../../x11/libXi/buildlink3.mk"
.include "../../graphics/gdk-pixbuf2/buildlink3.mk"
so one would expect that MesaLib and a bunch more things would be
required. But, to my surprise,
.../pkgsrc/graphics/clutter$ make show-depends
gdk-pixbuf2>=2.26.5nb2:../../graphics/gdk-pixbuf2
glib2>=2.34.0:../../devel/glib2
atk>=2.6.0:../../devel/atk
pango>=1.36.0nb1:../../devel/pango
cairo-gobject>=1.12.16:../../graphics/cairo-gobject
cogl>=1.14.0:../../graphics/cogl
json-glib>=0.14.2nb3:../../textproc/json-glib
doesn't show that!
On the other hand, somewhere there *is* that dependency, since something
in clutter seemingly does want to load that shared library. (Maybe it
wasn't auto-removed in my build environment and that could have
triggered it??)
Does anyone else see this?
-Olaf.
--
___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for
\X/ rhialto/at/xs4all.nl -- 'this bath is too hot.'
Attachment:
pgp9IFJL0eIht.pgp
Description: PGP signature