Avoid la files.

Hi All! I have a quick question about libtool: What can I break, if I fool libtool into thinking that there are no .la files for any library on the command line? The background: We have a bunch of software (about 1000 libraries) which are linked (shared) together in one executable. If manually li

Re: Avoid la files.

Hello Markus, Thanks for the report. * Duft Markus wrote on Thu, Dec 13, 2007 at 10:34:16AM CET: > > I have a quick question about libtool: What can I break, if I fool > libtool into thinking that there are no .la files for any library on the > command line? > > The background: We have a bunch

RE: Avoid la files.

Hello! W32 was the fastest with 40 minutes, a x86_64 linux that i tried as well took about 50 minutes before we canceled ;o( I'm not sure if i can easily put in HEAD, we use 1.5.24. Would it be enough to get HEAD built somewhere, and bootstrap only the last component with it (leave all libraries

Debugging subversion compile failure for 64bit platform.

Hi folks, I have been trying to compile subversion on Sun Solaris 10 Update 4, with Sun Studio 12, for 64 bit Sparc. The compilation for subversion as such works, almost out of the box, aside from some minor linking quirks, which can be fixed with the setting of LDFLAGS and others etc, pp. Howev

Re: Debugging subversion compile failure for 64bit platform.

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=...'

Re: Debugging subversion compile failure for 64bit platform.

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: Avoid la files.

* Duft Markus wrote on Thu, Dec 13, 2007 at 11:27:34AM CET: > > I'm not sure if i can easily put in HEAD, we use 1.5.24. Would it be > enough to get HEAD built somewhere, and bootstrap only the last > component with it (leave all libraries untouched)? Yes. > Maybe we can try on a linux box, w32

Re: Debugging subversion compile failure for 64bit platform.

* [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: Avoid la files.

On Thu, 13 Dec 2007, Ralf Wildenhues wrote: Maybe we can try on a linux box, w32 won't work, since i don't have my patches ported for HEAD ;o( Yes, that should be sufficient. I can't tell you yet whether it would help, though, as I'm not yet sure about the actual problem cause. Something t

Re: Mac OS X 10.2.8 HEAD test failures.

Ralf Wildenhues wrote: > Hi Peter, > > * Peter O'Gorman wrote on Tue, Dec 11, 2007 at 05:11:47PM CET: >> Ralf Wildenhues wrote: >> >>> That's a bug, thanks for catching. Does it work if _LT_CHECK_BUILDDIR >>> is only m4_require'd? >>> >>> I assume if that's fixed, there will still be more issues.

Re: Debugging subversion compile failure for 64bit platform.

> > > 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: Avoid la files.

Good Morning ;) Ralf Wildenhues wrote: > * Duft Markus wrote on Thu, Dec 13, 2007 at 11:27:34AM CET: >> >> I'm not sure if i can easily put in HEAD, we use 1.5.24. Would it be >> enough to get HEAD built somewhere, and bootstrap only the last >> component with it (leave