Didier Verna <verna(a)inf.enst.fr&gt; writes: I know that configure does more that finding the System's defaults. I really think that Martin did a wonderful job implementing this. But in this case it just works wrong. What happens in configure is the following: - it sees that I have not supplied any -with-x-..=... options and that $OPENWINHOME is set but points to the SUN default of /usr/openwin. Therefore it doesn't bother setting the $x_... vars. (probably reasoning that autoconf will later on find this path anyway). - it checks for /usr/X11 (because apparently autoconf doesn't find this on Linux, HP because of a broken install by the vendor) and sets x_... if it finds it. - run the AC macro. This macro doesn't bother doing anything if x_... is set, most importantly it does *not* run xmkmf. As Jan pointed out the (relatively) portable way of finding X is to use xmkmf, which would have worked perfectly in my case, but is never done because of the preemptive Linux/HP fix. I guess running xmkmf should be The Right Thing in your situation as well. You probably have $OPENWINHOME set but presumably have your X11R6.3 xmkmf in your PATH. BTW: Didier you always make me feel stupid for running the Sun supplied stuff, but in many cases I really don't see the need (e.g. cc, Openwin3.6, ...) and our sysadmins are capable of fskcing up even the most simple installation of 'free' replacements :-) And I think *you* would be surprised by the number of people who run *only* the vendor supplied version of everything. :-) Gunnar -- Gunnar Evermann Natural Language Systems Group, University of Hamburg EMail: Gunnar.Evermann(a)nats.informatik.uni-hamburg.de