[Bug: 21.5-b31] [semi-solved] configure does not like my Xaw3d lib
Giacomo Boffi writes:
from config.log:
----------------------------------------------------------------------
configure:16183: checking for Xaw3dComputeBottomShadowRGB in -lXaw3d
configure:16208: gcc -o conftest -Wall -Wno-switch -Wundef
-Wsign-compare -Wno-char-subscripts -Wpacked -Wshadow
-Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes
-Wdeclaration-after-statement -g -O3 -fno-strict-aliasing
-I/usr/include/freetype2 -lXft conftest.c -ltiff -lpng -ljpeg -lz
-lgif -lcompface -lXpm -lXft -lfontconfig -lXrender -lXmu -lXt
-lXext -lX11 -lSM -lICE -lXaw3d -lm 1>&5
conftest.c:121:1: warning: function declaration isn't a prototype
[-Wstrict-prototypes]
conftest.c:123:1: warning: function declaration isn't a prototype
[-Wstrict-prototypes]
/usr/bin/ld: cannot find -ltiff
I hate autoconf....
----------------------------------------------------------------------
in effects, my libtiff is (i-dont-know-why) in
/usr/lib/i386-linux-gnu/libtiff.so.4.3.4
How very ... Debian. *sigh* :-)
i did a brutish
% sudo cp /usr/lib/i386-linux-gnu/libtiff.so.4.3.4 /usr/lib/libtiff.so
% configure ...
and now all is well... but perhaps configure needs a little
adjustment
Would you be willing to try removing the copy of libtiff in /usr/lib,
and building XEmacs with --with-athena=xaw instead of --with-athena=3d?
DON'T DO IT YET! It will waste your time. First let me cook up a
configure patch to test, which should fail before compiling and
linking.
AFAICS, the reason you get as far as checking for Xaw3d is that in our
configure.ac, --with-tiff=yes *assumes* that TIFF can be used, and
doesn't actually test to make sure it is! So I bet that with a
patched configure you'll get a "can't find tiff" error.
You might see if there's a Debian bug open on libtiff.
i feel like i haven't done all of my homeworks before annoying
the
mailing list, sorry
Not your fault at all, it's just that autoconf sucks. It does very
little to help us with the accounting needed to ensure that our
detection code is consistent with the current build configuration, and
nothing to ensure that tests are done properly. Of course we screwed
up in this case by writing bad configure tests, but autoconf could do
a much better job of helping with that.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
But-I-have-a-dirty-mind-ly y'rs,
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta