Re: Debugging subversion compile failure for 64bit platform.

2007-12-13 Thread [EMAIL PROTECTED]
> > > Which `./libtool --version'? > > ltmain.sh (GNU libtool) 1.5.2 (1.1220.2.60 2004/01/25 12:25:08) > > That's way old. Please don't report bugs against such old versions, > rather, if that libtool was generated by subversion's configure, then > please complain to the subversion people that

Re: Debugging subversion compile failure for 64bit platform.

2007-12-13 Thread Ralf Wildenhues
* [EMAIL PROTECTED] wrote on Thu, Dec 13, 2007 at 04:39:44PM CET: > > > Which `./libtool --version'? > ltmain.sh (GNU libtool) 1.5.2 (1.1220.2.60 2004/01/25 12:25:08) That's way old. Please don't report bugs against such old versions, rather, if that libtool was generated by subversion's config

Re: Debugging subversion compile failure for 64bit platform.

2007-12-13 Thread [EMAIL PROTECTED]
Hi Ralf, > Which `./libtool --version'? ltmain.sh (GNU libtool) 1.5.2 (1.1220.2.60 2004/01/25 12:25:08) > Typically you can work around this using > ./configure CC='cc -m64 -xarch=...' CXX='CC -m64 -xarch=...' > >but AFAIK all such instances are fixed in 1.5.24. Right now I'm trying to work a

Re: Debugging subversion compile failure for 64bit platform.

2007-12-13 Thread Ralf Wildenhues
Hello Igor, * [EMAIL PROTECTED] wrote on Thu, Dec 13, 2007 at 03:25:03PM CET: > > However the compilation of the swig-* components fails, as libtool is > dropping the -m64 flag somewhere. Which `./libtool --version'? Typically you can work around this using ./configure CC='cc -m64 -xarch=...'