[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
pkg/39621: wm/metacity configure fails - missing xdamage (NetBSD 3.0 XFree86)
>Synopsis: wm/metacity configure fails - missing xdamage (NetBSD 3.0
>Arrival-Date: Wed Sep 24 08:45:01 +0000 2008
>Originator: Robert Elz
>Release: NetBSD 4.0_STABLE (pkgsrc current within 12 hours)
Prince of Songkla University
System: NetBSD jade.coe.psu.ac.th 4.0_STABLE NetBSD 4.0_STABLE
(JADE-1.696-20080517) #9: Fri May 23 18:55:13 ICT 2008
wm/metacity seems to need something called xdamage.pc
As best I can tell, the Xfree86 supplied with NetBSD 3.0
(or netbsd-3 anything) does not have such an entity.
I do see it in netbsd-4 and current (inckluding Xorg).
metacity used to compile OK on NetBSD 3, so I am guessing
it is probably still possible to make it happen.
This one is annoying, in that although I have no desire to ever
actually use this window manager, it is a requirement for
building lots of other gnome stuff, which would be useful
to have - as best I can tell, and as it should, all the gnome
applications work find with any window manager (any I have tried,
which admittedly is not a huge set).
Attempt to build wm/metacity on NetBSD 3. I do that using
pkg_comp with libkver and NetBSD 3.0 sets (including Xfree86)
Expect to see ...
checking for METACITY... configure: error: Package requirements (gtk+-2.0 >= 2.1
0.0 pango >= 1.2.0 gconf-2.0 >= 1.2.0 libstartup-notification-1.0 >= 0.7 xcompos
ite >= 0.2 xfixes xrender xdamage xcursor) were not met:
No package 'xdamage' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables METACITY_CFLAGS
and METACITY_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
*** Error code 1
Needless to say, no simple path modification is going to
find a file which seems to not exist (and since NetBSD 3.0
is released, it is never going to exist there).
Work out why metacity needs xdamage (now, when it apparently
did not before) and add an option (or something) to avoid it.
Or, make an xdamage package that metacity could depend upon,
which would install whatever it is that is really needed for
systems that don't have it.
Or, just perhaps (as a workaround) remove metacity as a
dependancy from as much as possible, so at least other things
Main Index |
Thread Index |