On 2005-01-03 12:57-0800, Justin Erenkrantz wrote:
> --On Monday, January 3, 2005 1:52 PM -0700 Jani Averbach <jaa@jaa.iki.fi>
> wrote:
>
> >Updated libtool to the version 1.5.10, checked that
> >/usr/bin/cc is gcc and checked that I have not set any CC
> >etc. env. variables.
>
> Your output had:
>
> /bin/sh /home/jaa/tmpfs/build/trunk/libtool --silent
> --mode=compile x86_64-pc-linux-gnu-gcc ...
>
> Python looks to have been compiled with that compiler. I actually think a
> downgrade of libtool would fix it. The libtool folks have done some awful
> things in trying to 'infer' the configuration that it should use that seems
> to have been done only recently. You can also add '--tag=CXX' to the
> SWIG_PY_COMPILE line in Makefile and that might work.
>
> No clue if they plan on fixing their bugs... -- justin
Hello,
I made a patch which will cause that our configure will drive libtool
with --tag=XXX if libtool suppors it. I have a feeling that I am quite
far away from home, so if someone with autoconf+libtool-fu could
review, or test on some not so Gnu/Linuxize machine, that would be nice.
BR, Jani
Log:
Use --tag=XXX for libtool, if it supports it. This should fix these
kind of libtool's warnings:
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
* configure.in
(LIBTOOL,SVN_LIBTOOL): construct same kind of machinery with
experimental-libtool than without (use $(SHELL) in any case).
(sh_libtool): New helper variable, this is runnable from configure
(SVN_LT_CCTAG, SVN_LT_CXXTAG): New substitute variables for
Makefile.in
* Makefile.in
(LTFLAGS): use SVN_LT_CCTAG here
(LTCXXFLAGS): new, use SVN_LT_CXXTAG here
(COMPILE_JAVAHL_CXX) = Use LTCXXFLAGS here, it was LTFLAGS
(LINK_JAVAHL_CXX): ditto
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 4 22:24:51 2005