Karl> Maybe we should try explicitly building with xaw3d/nextaw, Karl> or whatever and see if it works then. We have, and it does. I have done it on Debian potato, Jan Vronnhof on RedHat (I believe), both with Xaw3d, and Daniel Pittman has done it on his system with neXtaw or whatever it's called. This is currently correctly done automatically on Debian "potato" systems by ./configure (XEmacs 21.2.25 and up), when invoked as ./configure ... --with-widgets=athena --with-athena=3d ... (or with `--with-athena=next' or whatever). In this case there is no ambiguity, because the linker insists on libXaw3d. AFAIK both Jan and Daniel used similar commands with success. This may be unacceptable for you as Debian maintainer, of course; it basically forces your "customers" to install xaw3d whether they want to or not. You can enforce that with a dependency, of course. But I think you should go take a look at http://www.best.com/~falconer/Widgets/#summary and try the various widget sets and decide which one you like best before enforcing such a dependency. Note that the Ed Falk widgets we use may or may not work with any given Athena clone (and probably don't). For personal use, Stefanie should test whether that works, if not, tell us (1) where the Xaw3d headers and libraries are installed (2) any aliases (eg, via symlinks) that point to them (3) whether this is a standard installation from a widespread distribution or a homebrew configuration (4) the output of 'ldconfig -p | fgrep -i xaw', and whether /etc/ld.so.conf is a standard installation or contains homebrew elements. (All linux-specific terms, I'm afraid, translate to the relevant OS. ;-) -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

Stefanie> On Wed, Dec 29, 1999 at 13:00:19 +0900, Stephen Stefanie> J. Turnbull wrote: Stefanie> (1) They are in /usr/X11R6/lib The headers are in /usr/X11R6/include/<where>? Stefanie> (2) any aliases (eg, via symlinks) that point to them Stefanie> As I said before: there is a symlink Stefanie> stefanie＠diabolo[/usr/X11R6/lib]>dir libXaw3d.so Stefanie> lrwxrwxrwx 1 root root 16 Dec 19 02:29 libXaw3d.so -> libneXtaw.so.6.1* Arggh. I don't see how we can detect this right if there are binary incompatibilities between Xaw3d and neXtaw. I would imagine you're getting Xaw3d headers and the libneXtaw routines. Blooey! Stefanie> (3) I'm running a RedHat 6.1 without big changes. The Stefanie> neXt-libs are from the package: Stefanie> neXtaw-0.5.1p2-glibc.tar.gz *.tar.gz? Not *.rpm? If it's not an RPM from the main RedHat distribution, I don't see how we can promise to support it; we'd have to consider it homebrew. Did the package make the above confusing symlink, or did you? Stefanie> (4) the output of 'ldconfig -p | fgrep -i xaw' Stefanie> stefanie＠diabolo[~]>ldconfig -p | fgrep -i xaw Stefanie> libXaw3d.so.6 (libc6) => /usr/X11R6/lib/libXaw3d.so.6 Is this a link to the above-mentioned libneXtaw.so.6.1, or is it the real libXaw3d? There usually is a family of libraries lib.so, lib.so.N, lib.so.N.M, the less specific of which should be links to lib.so.N.M. If the middle cases is different, you're asking for trouble. What does `ldd xemacs' say about what the xemacs binary wants to link to? Stefanie> libXaw3d.so.6 (ELF) => /usr/i486-linux-libc5/lib/libXaw3d.so.6 Stefanie> libXaw3d.so (libc6) => /usr/X11R6/lib/libXaw3d.so Stefanie> libXaw.so.6 (libc6) => /usr/X11R6/lib/libXaw.so.6 Stefanie> libXaw.so.6 (libc5) => /usr/i486-linux-libc5/lib/libXaw.so.6 Stefanie> libXaw.so (libc6) => /usr/X11R6/lib/libXaw.so -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."