You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Jani Averbach <ja...@jaa.iki.fi> on 2005/01/03 20:04:17 UTC
make swig-py won't compile
Hello,
I tried to compile python bindings, but hit the following error:
svn trunk @ 12575
SWIG Version 1.3.21
Python 2.3.4
libtool ltmain.sh (GNU libtool) 1.5.2 (1.1220.2.60 2004/01/25 12:25:08)
make swig-py
/bin/sh /home/jaa/tmpfs/build/trunk/libtool --silent
--mode=compile x86_64-pc-linux-gnu-gcc -pthread -fno-strict-aliasing
-DNDEBUG -fPIC -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
-D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE
-I/home/jaa/tmpfs/build/trunk/subversion/bindings/swig
-I/home/jaa/tmpfs/build/trunk/subversion/include -I//usr/lib/swig1.3
-DSVN_SWIG_VERSION=103021
-I/home/jaa/tmpfs/inst/apr-0.9/include/apr-0-I/home/jaa/tmpfs/inst/apr-util-0.9/include/apr-0
-I/opt/db/4.2.52/include
-I/home/jaa/tmpfs/build/trunk/subversion/bindings/swig
-I/home/jaa/tmpfs/build/trunk/subversion/include -I//usr/lib/swig1.3
-DSVN_SWIG_VERSION=103021 -I/home/jaa/tmpfs/inst/apr-0.9/include/apr-0
-I/home/jaa/tmpfs/inst/apr-util-0.9/include/apr-0
-I/opt/db/4.2.52/include -I/usr/include/python2.3
-I/home/jaa/tmpfs/build/trunk/subversion/bindings/swig/python/libsvn_swig_py
-prefer-pic -c -o subversion/bindings/swig/python/svn_client.lo
subversion/bindings/swig/python/svn_client.c
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
make: *** [subversion/bindings/swig/python/svn_client.lo] Error 1
The make swig-pl works ok.
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: make swig-py won't compile
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-01-03 12:57-0800, Justin Erenkrantz wrote:
> 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.
>
Thanks Justin!
I added following to the top level Makefile
SWIG_PY_COMPILE = --tag=CXX ...
SWIG_PY_LINK = --tag=CXX ...
and it worked.
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] libtool with --tag=XXX (Was: make swig-py won't compile)
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-01-04 23:42-0800, Justin Erenkrantz wrote:
>
> $(SHELL) is generally only needed if the script isn't executable. It's a
> generally safe assumption that APR will have the executable bit set. However,
> and more importantly, APR comes with a variety of libtool replacements that
> aren't shell scripts, but real C executables. So, a $(SHELL) prefix for them
> would be invalid and wouldn't work.
>
Thanks about clarification!
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] libtool with --tag=XXX (Was: make swig-py won't compile)
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Tue, Jan 04, 2005 at 09:32:01PM -0700, Jani Averbach wrote:
> On 2005-01-04 17:18-0800, Justin Erenkrantz wrote:
> >
> > Looks good. I tweaked it slightly (removed the $(SHELL) part for
> > apr-libtool code path) and committed it in r12591. Thanks! -- justin
> >
> Thanks Justin!
>
> I am not objecting what you did, but would like to know better, so:
>
> AC_PROG_LIBTOOL will expand (at least here) to
> $(SHELL) $(top_builddir)/libtool
> and we are using a same kind of form for SVN_LIBTOOL.
>
> Why don't we use $(SHELL) for apr's libtool? I thought that using an
> explicit shell for it would be a good thing to do, at least because of
> consistency, if not otherwise?
$(SHELL) is generally only needed if the script isn't executable. It's a
generally safe assumption that APR will have the executable bit set. However,
and more importantly, APR comes with a variety of libtool replacements that
aren't shell scripts, but real C executables. So, a $(SHELL) prefix for them
would be invalid and wouldn't work.
FWIW, the experimental libtool option is mainly in place so that I don't have
to use GNU libtool: speeds my builds up by a factor of 2 or more... -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] libtool with --tag=XXX (Was: make swig-py won't compile)
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-01-04 17:18-0800, Justin Erenkrantz wrote:
>
> Looks good. I tweaked it slightly (removed the $(SHELL) part for
> apr-libtool code path) and committed it in r12591. Thanks! -- justin
>
Thanks Justin!
I am not objecting what you did, but would like to know better, so:
AC_PROG_LIBTOOL will expand (at least here) to
$(SHELL) $(top_builddir)/libtool
and we are using a same kind of form for SVN_LIBTOOL.
Why don't we use $(SHELL) for apr's libtool? I thought that using an
explicit shell for it would be a good thing to do, at least because of
consistency, if not otherwise?
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] libtool with --tag=XXX (Was: make swig-py won't
compile)
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Tuesday, January 4, 2005 2:23 PM -0700 Jani Averbach <ja...@jaa.iki.fi>
wrote:
> 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.
Looks good. I tweaked it slightly (removed the $(SHELL) part for
apr-libtool code path) and committed it in r12591. Thanks! -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
[PATCH] libtool with --tag=XXX (Was: make swig-py won't compile)
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-01-03 12:57-0800, Justin Erenkrantz wrote:
> --On Monday, January 3, 2005 1:52 PM -0700 Jani Averbach <ja...@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
Re: make swig-py won't compile
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Monday, January 3, 2005 1:52 PM -0700 Jani Averbach <ja...@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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: make swig-py won't compile
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-01-03 12:13-0800, Justin Erenkrantz wrote:
> --On Monday, January 3, 2005 1:04 PM -0700 Jani Averbach <ja...@jaa.iki.fi>
> wrote:
>
> >libtool: compile: unable to infer tagged configuration
> >libtool: compile: specify a tag with `--tag'
> >make: *** [subversion/bindings/swig/python/svn_client.lo] Error 1
>
> This is the known libtool bug where it gets confused if the 'cc' isn't gcc.
> Fix that and it'll work. Or, change your version of libtool. -- justin
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.
And I still get the same (starting from clean tree):
$ ./autogen.sh
buildcheck: checking installation...
buildcheck: autoconf version 2.59 (ok)
buildcheck: autoheader version 2.59 (ok)
buildcheck: libtool version 1.5.10 (ok)
Copying libtool helper: /usr/share/aclocal/libtool.m4
Creating build-outputs.mk...
Creating svn_private_config.h.in...
Creating configure...
You can run ./configure now.
...
./configure --prefix=/home/jaa/tmpfs/inst/trunk
--with-apr=/home/jaa/tmpfs/inst/apr-0.9/bin/apr-config \
--with-apr-util=/home/jaa/tmpfs/inst/apr-util-0.9/bin/apu-config \
--with-pic --with-swig --enable-javahl \
--with-junit=/opt/junit/3.8.1/junit.jar
make
make install
make swig-py
...
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
Any others ideas what might be wrong?
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: make swig-py won't compile
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Monday, January 3, 2005 1:04 PM -0700 Jani Averbach <ja...@jaa.iki.fi>
wrote:
> libtool: compile: unable to infer tagged configuration
> libtool: compile: specify a tag with `--tag'
> make: *** [subversion/bindings/swig/python/svn_client.lo] Error 1
This is the known libtool bug where it gets confused if the 'cc' isn't gcc.
Fix that and it'll work. Or, change your version of libtool. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org