On Tue, Oct 23, 2012 at 12:54:57PM +0200, Jörn Clausen wrote: > > Take a look at config.log, why exactly the check fails. > > Perhaps it's the same xextproto problem, but this time in the buildlink3.mk. > > Sort of... > > configure:12740: checking pkg-config is at least version 0.9.0 > configure:12743: result: yes > configure:12754: checking for CAIRO > configure:12761: $PKG_CONFIG --exists --print-errors "cairo >= 1.8.10" > Package xextproto was not found in the pkg-config search path. > Perhaps you should add the directory containing `xextproto.pc' > to the PKG_CONFIG_PATH environment variable > Package 'xextproto', required by 'Xext', not found > configure:12764: $? = 1 > configure:12777: $PKG_CONFIG --exists --print-errors "cairo >= 1.8.10" > Package xextproto was not found in the pkg-config search path. > Perhaps you should add the directory containing `xextproto.pc' > to the PKG_CONFIG_PATH environment variable > Package 'xextproto', required by 'Xext', not found > configure:12780: $? = 1 > > configure:12807: error: Package requirements (cairo >= 1.8.10) were not met: > > I didn't expect such a difference between the terminal output and the > contents of config.log. pkg-config is sneaky that way. > Anyway, adding a reference to > "../../x11/xextproto/buildlink3.mk" helped here as well. I've since added it to libXext/bl3.mk, so the problem should now be gone. Thomas