libX11 and libXext (at least) fail using prefix on make install

2011-06-21 Thread Garry Iglesias
Hi, Sorry if this problem has already been mentioned, but I couldn't find any question nor bug about it... I'm building a libX11 and libXext as static libraries in a local tree as third party dependencies of a framework I'm working on. It's been working like a charm for 3 years, but I recently

Re: libX11 and libXext (at least) fail using prefix on make install

2011-06-21 Thread Dan Nicholson
On Mon, Jun 20, 2011 at 3:12 AM, Garry Iglesias garry.igles...@gmail.com wrote: Hi, Sorry if this problem has already been mentioned, but I couldn't find any question nor bug about it... I'm building a libX11 and libXext as static libraries in a local tree as third party dependencies of a

Re: libX11 and libXext (at least) fail using prefix on make install

2011-06-21 Thread Gaetan Nadon
On Tue, 2011-06-21 at 03:46 -0700, Dan Nicholson wrote: On Mon, Jun 20, 2011 at 3:12 AM, Garry Iglesias garry.igles...@gmail.com wrote: Hi, Sorry if this problem has already been mentioned, but I couldn't find any question nor bug about it... I'm building a libX11 and libXext as

Intel Pineview G: xlogo/xpdf/gv paint into windows dragged over them

2011-06-21 Thread Alexander Kurz
Hi Folks, I am facing some 2D rendering problems on my new Intel Atom D525 / Pineview G / GMA3150 box. Certain X-applications paint patterns in windows dragged over them. e.g.: dragging an xterm sidewise over xpdf creates some barcode-patterns in xterm, dragging xterm over xlogo paints

[ANNOUNCE] xkbcomp 1.2.2

2011-06-21 Thread Daniel Stone
Hi, This is an semi-urgent bugfix release for the two commits of mine, which fix a particularly bad failure in the compat code. If you had a SymInterpret definition (i.e. to map a keysym to an action, as used for VT switch and others) with an unknown keycode, every key that wasn't already mapped

[ANNOUNCE] xkbcomp 1.2.3

2011-06-21 Thread Daniel Stone
Hi, Well, this is embarassing. There was a pretty bad problem with the 1.2.2 release, which quite effectively crushed Any+AnyOfOrNone(All) interp mappings, in that xkeyboard-config actually relied on an explicit Any+AnyOfOrNone(All) mapping to function. 1.2.3 builds on the previous 1.2.2 fix to

Re: [ANNOUNCE] xkbcomp 1.2.2

2011-06-21 Thread Daniel Stone
Hi, On Tue, Jun 21, 2011 at 02:17:30PM +0100, Daniel Stone wrote: This is an semi-urgent bugfix release for the two commits of mine, which fix a particularly bad failure in the compat code. If you had a SymInterpret definition (i.e. to map a keysym to an action, as used for VT switch and

[ANNOUNCE] xkbcomp 1.2.2

2011-06-21 Thread Daniel Stone
Hi, This is an semi-urgent bugfix release for the two commits of mine, which fix a particularly bad failure in the compat code. If you had a SymInterpret definition (i.e. to map a keysym to an action, as used for VT switch and others) with an unknown keycode, every key that wasn't already mapped

[ANNOUNCE] xkbcomp 1.2.3

2011-06-21 Thread Daniel Stone
Hi, Well, this is embarassing. There was a pretty bad problem with the 1.2.2 release, which quite effectively crushed Any+AnyOfOrNone(All) interp mappings, in that xkeyboard-config actually relied on an explicit Any+AnyOfOrNone(All) mapping to function. 1.2.3 builds on the previous 1.2.2 fix to

Re: [ANNOUNCE] xkbcomp 1.2.2

2011-06-21 Thread Daniel Stone
Hi, On Tue, Jun 21, 2011 at 02:17:30PM +0100, Daniel Stone wrote: This is an semi-urgent bugfix release for the two commits of mine, which fix a particularly bad failure in the compat code. If you had a SymInterpret definition (i.e. to map a keysym to an action, as used for VT switch and