sb> Martin Buchholz <martin(a)xemacs.org&gt; writes: sb> Why? If /usr/dt, by your own writings contains X11 libraries and sb> usually, but not always only Motif and/or CDE, why the hell doesn't sb> --x-includes and --x-libraries override it? Has the meaning of X sb> changed? CDE is not X11. It is a software package that requires and extends X. sb> If I tell configure that I don't want any stinking CDE/Motif by sb> an unfortunately large number of options, then what business does it sb> have sticking that directory ahead of others that I have explicitly sb> asked to be put ahead via --x-includes and --x-libraries. Excuse me, sb> but configure is clearly broken in this area. You CAN specify the location of the BASE X11 using --x-includes and --x-libraries. That has nothing to do with whether CDE is used. CDE is not X11. CDE === KDE === GNOME !== X11. Since the CDE libraries use symbols in the X11 libraries, they have to come prior to X11 in the link line. It is an autoconf limitation that there can only be one x-includes directory and only one x-libraries directory, which does not reflect the real world. That is an autoconf design bug, which we could work around. Unfortunately, it is fuzzy exactly what X11 is. sb> A brilliant suggestion. sb> Yes. I couldn't build an XEmacs binary on HP/UX against /usr/contrib sb> X11R6 libraries without manually modifying configure to make /usr/dt sb> go away. I don't believe you. --site-libraries, --site-runtime-libraries and --site-includes allows you to specify directories that ALWAYS get priority (modulo bugs, of course). sb> I have that patch sitting in my incoming queue. I'm almost in enough sb> of a foul mood over this to consider applying it. A patch that would do what, exactly? Does our HP-UX beta community want it? Can you give me an HP-UX account? Martin