Re: Problems checking out branch-1-5

Albert Chin <[EMAIL PROTECTED]> writes: > I have CVS 1.11.5: > $ cvs -d:pserver:[EMAIL PROTECTED]:/var/cvs login > $ cvs -d:pserver:[EMAIL PROTECTED]:/var/cvs co -rbranch-1-5 libtool > cvs [server aborted]: received abort signal It also fails for me, but it seems to work fine from subversion

Re: running 'libtool gdb foo' from emacs

Ted Irons <[EMAIL PROTECTED]> writes: > Any way of running gdb on an uninstalled > binary from emacs? Typing 'libtool gdb program' at the 'Run gdb prompt' should work, except that emacs sends '-fullname' to gdb which the libtool gdb wrapper doesn't understand. It should be fixable in either gud

Re: make check failures

fix below (relative to cvs libtool) seems to fix the problem for me. /assar 2001-09-13 Assar Westerlund <[EMAIL PROTECTED]> * ltdl.m4 (AC_LTDL_DLLIB): call dlopen with arguments so the test does not fail due to a prototy

Re: Fwd: from debian-mentors: libtool relink fails due overriden prefix

"Wesley W. Terpstra" <[EMAIL PROTECTED]> writes: > I know you people don't care at all about debian packaging, but thought that > perhaps libtool has a mechanism for dealing with situations like this. It might have or it might just be that I misunderstand your problem or the exact details of how

ranlib'ing static libraries?

example OpenBSD/i386. Any comments? /assar 2000-08-13 Assar Westerlund <[EMAIL PROTECTED]> * ltconfig.in: add back ranlib calls for static libraries if there is a ranlib Index: ltconfig.in === RCS file: /ho

Re: ultrix, cache_file and ksh

Pavel Roskin <[EMAIL PROTECTED]> writes: > Hello, Assar! Hi, Pavel. > if test -n "$cache_file" && test -r "$cache_file" && test -f \ > "$cache_file"; then > > Please check that it works for your ksh. Yeah, that works fine. Please commit that change and thanks for your help. /assar

ultrix, cache_file and ksh

I'm having problems using libtool-current on Ultrix 4.4 ltconfig re-execs ksh if it did not like the echo in the current shell (/bin/sh in my case), and the Ultrix ksh seems to dislike doing . /dev/null Is the following patch the right way of solving/working around this? /assar Index: ltconfig

Re: installation of .la-files and linking against installed libraries

I wrote: > "Gary V. Vaughan" <[EMAIL PROTECTED]> writes: > > It has been working forever! > > > > libtool --mode=link gcc -o foo bar.c -L/usr/local/lib -lbaz > > Aha, I did /usr/local/lib/libbaz.la and then I got the > not-obvious-to-me error: > > /usr/local/lib/.libs/libbaz.a not found But,

Re: installation of .la-files and linking against installed libraries

"Gary V. Vaughan" <[EMAIL PROTECTED]> writes: > It has been working forever! > > libtool --mode=link gcc -o foo bar.c -L/usr/local/lib -lbaz Aha, I did /usr/local/lib/libbaz.la and then I got the not-obvious-to-me error: /usr/local/lib/.libs/libbaz.a not found Thanks. /assar

installation of .la-files and linking against installed libraries

Hi. Two questions: 1. Why are the *.la files installed? The comment says: # Install the pseudo-library for information purposes. 2. How do you link against an installed library? As far as I can tell, there's no support of doing that. And it would seem to me that libtool is the ideal