re: failure during build - Tpo file not found

In May 2009, Jared Nance wrote: >/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. - I.. >-L/usr/local/root/Current/lib/root -I/usr/local/root/Current/ include/root >-lCore -lRIO -lTree -lcint -lPhysics -I/src/stlplus -I/ include -L/lib >-lRATEvent_Darwin-g++ -g -O2 -MT libTra

Re: [scons-users] libtool and scons

Chad Austin wrote: On IRIX, libtool and MIPSPro CC don't get along. To compile standard C++ code, you need the -LANG:std option, but libtool doesn't even pass it down to the actual command line, so your code doesn't compile! This problem and its workaround have, oddly enough, been documented, th

Re: autoconf/configure-based linkage/include paths.

Keith Kyzivat wrote: Ok. I have fixed the problem. It has to do with libtool having a hardwired lib search path of /lib /usr/lib and /usr/local/lib, which in the cross-compile case, is incorrect. I modified the generated libtool script contained in the project dir, modifying the sys_lib_search

RE: When is 1.5 due for release?

I may have run into a libtool problem cross-compiling kaffe. I'll try to check it out in time for it to be fixed for 1.5... -Original Message- From: Robert Boehne To: Nick Hudson Cc: [EMAIL PROTECTED] Sent: 03.03.2003 21:59 Subject: Re: When is 1.5 due for release? Nick, Before April 15

RE: generated libtool on debian/unstable always broken

Hah. I bet it's a quoting problem; it seems newer autotools silently f**ks up on improperly quoted sources that worked fine with older autotools. IMHO this is a usability bug in newer autotools. I believe one or the other of the following patches dealt with this particular problem for one packa

Re: How can I link with libguile?

Bruce Korb wrote: Here are the parameters: 1. I cannot rely on `guile-config'. It is often installed without that script. Is guile-config reliably installed for versions of guile later than some number X? In that case, maybe you could simply require version X or later... I do sympathize

Re: DESTDIR question

version of libtool fix this? Ossama checked a patch in a few months ago that made DESTDIR better supported. I've used it with some success. - Dan -- Dan Kegel Linux User #78045 http://www.kegel.com ___ Libtool mailing list [EMAIL

Re: script to update kaffe-1.0.7 to cvs libtool to allowcross-compiling

ar.gz kaffe-1.0.7-libtool1.4e --------- -- Dan Kegel Linux User #78045 http://www.kegel.com --- kaffe-1.0.7/test/regression/Makefile.am Wed Jun 19 18:41:52 2002 +++ kaffe-1.0.7-libtool1.4e/test/regression/Makefile.am Thu Jan 2 18:23:44 2003 @@ -10,12 +

script to update kaffe-1.0.7 to cvs libtool to allow cross-compiling

Dalibor Topic wrote: --- Dan Kegel <[EMAIL PROTECTED]> wrote: FWIW, the procedure for updating kaffe to use CVS libtool appears to be something like: ... OK, I have this down a bit more solidly now. I'm attaching a shell script which takes a kaffe-1.0.7 source tarball and produces

1.5 alpha release?

a similar question before, but may have posted it to the wrong list. -- Dan Kegel Linux User #78045 http://www.kegel.com ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

re: libtool: -e: command not found

incompoop, so take that with a grain of salt :-) -- Dan Kegel Linux User #78045 http://www.kegel.com ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

next release of libtool? (was: RE: libtool incompatible with current autoconf)

I'll start trying to use cvs head libtool and see if it works for me. - Dan -Original Message- From: Albert Chin On Mon, Dec 23, 2002 at 04:12:46PM -0800, Dan Kegel wrote: > I discovered to my chagrin that I cannot update > kaffe from autoconf2.13 to autoconf2.53. Just update

libtool incompatible with current autoconf

I discovered to my chagrin that I cannot update kaffe from autoconf2.13 to autoconf2.53. In detail, the problem is that converting kaffe to use autoconf2.5x and then running configure causes the following error: configure: configuring in libltdl configure: running /bin/sh '../../kaffe-1.0.7/liblt

.la file semantics? (was: [patch] make libtool1.4d work when cross-compiling)

Dan Kegel wrote: > > The patch > http://www.kegel.com/libtool-cross-2.patch > appears to fix libtool1.4d so it sets sys_lib_search_path_spec properly, > which is probably required for cross-compiling programs that use libtool. > > To test it, I created dumm

[patch] make libtool1.4d work when cross-compiling

The patch http://www.kegel.com/libtool-cross-2.patch appears to fix libtool1.4d so it sets sys_lib_search_path_spec properly, which is probably required for cross-compiling programs that use libtool. To test it, I created dummy cross-compiler mycc and linker myld which are just trivial wrappers

Re: Patch to make libtool support cross-compile

Guido Draheim wrote: > ... you put the patch before the big case-series > for the target-platform, so I guess that the libpath will be > overridden immediately. Only if the case statement below decides to override it. Linux doesn't. Putting it above the case statement is safer because it only cha

Patch to make libtool support cross-compile

As pointed out by H. Lu in October ( http://mail.gnu.org/pipermail/bug-libtool/2001-October/002869.html ) and seconded by Guido ( http://mail.gnu.org/pipermail/bug-libtool/2001-October/002872.html ) libtool improperly searches /lib and /usr/lib when doing a cross-compile, which results in librarie

Re: cross-compiling question: static libraries and binaries to different places?

Guido Draheim wrote: > ... See - the libtool crossgcc support (to which I did > contribute some of the time) can simply ask the cross-gcc > for the local searchpath via `gcc -print-search-dirs` - > this is needed for win32 compiles atleast, and I have a > patch on my disk which generalizes the ide