I've got Bug #90459, which says libXmu was not identified when compiling on vore (that's sparc, isn't it? not that it's real important).
The autobuild log at http://vore.debian.org/buildlogs/viewmol says: ... cc -c -Wall -I/usr/X11R6/include -DLINUX -I/usr/include -I/usr/include/python1.5 -O6 -fomit-frame-pointer -ffast-math ../coledit.c ... cc -o viewmol ... coledit.o ... -L/usr/lib/python1.5/config -L/usr/local/lib -lpython1.5 -ltiff -lGLU -lGL -L/usr/X11R6/lib -lXm -lXp -lXi -lXext -lXt -lX11 -lpthread -ldb -lutil -ldl -lm input.o: In function findFileType': input.o(.text+0x6d8): the use of tmpnam' is dangerous, better use mkstemp' coledit.o: In function getRGBcolormap': coledit.o(.text+0x2700): undefined reference to XmuLookupStandardColormap' collect2: ld returned 1 exit status make[2]: *** [viewmol_] Error 1 XmuLookupStandardColormap is undefined, and comes from libXmu (supplied by xlibs). Sure enough, there is no -lXmu entry on the linking line. The appropriate solution would, would it not?, be to add -lXmu. But the bit I don't understand is that this same line compiles perfectly fine on my i386 system: ... cc -o viewmol ... coledit.o ... -L/usr/lib/python1.5/config -L/usr/local/lib -lpython1.5 -ltiff -lGLU -lGL -L/usr/X11R6/lib -lXm -lXp -lXi -lXext -lXt -lX11 -lpthread -ldb -lutil -ldl -lm input.o: In function `findFileType': input.o(.text+0x6c7): the use of `tmpnam' is dangerous, better use `mkstemp' make[2]: Leaving directory `/home/drew/projects/viewmol-2.3/source/Linux' ... No complaints about XmuLookupStandardColormap, though the code and the compile line (no -lXmu) are the same. This is weird. It makes sense why it fails on vore. But why does it work on i386? Drew ps Build depends are: debhelper (>> 2.0.0), libtiff3g-dev, mesag-dev, lesstif-dev, libdb3-dev, python-dev, xlibs-dev, docbook-to-man. -- PGP public key available at http://dparsons.webjump.com/drewskey.txt Fingerprint: A110 EAE1 D7D2 8076 5FE0 EC0A B6CE 7041 6412 4E4A
