Re: pkg/45212: Cannot build x11/libXext due to a bad dependency on xextproto

["Jeremy C. Reed" <reed%reedmedia.net@localhost>]

The following reply was made to PR pkg/45212; it has been noted by GNATS.

From: "Jeremy C. Reed" <reed%reedmedia.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/45212: Cannot build x11/libXext due to a bad dependency on
 xextproto
Date: Wed, 3 Aug 2011 18:25:36 -0500 (CDT)

 > checking pkg-config is at least version 0.9.0... yes
 > checking for XEXT... configure: error: Package requirements (xproto >= 
 > 7.0.13 x11 >= 1.1.99.1 xextproto >= 7.0.99.2) were not met:
 > 
 > Requested 'xextproto >= 7.0.99.2' but version of XExtProto is 7.0.5
 > 
 > Consider adjusting the PKG_CONFIG_PATH environment variable if you
 > installed software in a non-standard prefix.
 > 
 > Alternatively, you may set the environment variables XEXT_CFLAGS
 > and XEXT_LIBS to avoid the need to call pkg-config.
 > See the pkg-config man page for more details.
 > 
 > *** Error code 1
 
 
 I assume X11_TYPE is default native.
 
 So a workaround may be setting X11_TYPE=modular in mk.conf.
 
 But if we are building modular libxext (and maybe any "modular-xorg" 
 component) we should default to force use of the modular dependencies 
 (like pkgsrc's xextproto). When does it make sense to mix and match the 
 X11 dependencies?