Den 2009-08-11 07:42 skrev Dave Korn:
Well, I did really want to make it a test of nothing other than the -bindir
functionality, in fact it's more or less just a test of the corner cases for
func_relative_path! Using -rpath seems to work as far as supplying an input
value for $install_libdir
Peter Rosin wrote:
I think the new file tests/win32.at has a too generic name. And what if
some non-win32 platform needs this? I think the test should be named
tests/bindir.at (or inst-bindir.at) since that is what is tested.
How about pe-dll.at?
You also enable the code in ltmain for
Peter Rosin wrote:
Den 2009-08-11 08:50 skrev Dave Korn:
Peter Rosin wrote:
I think the new file tests/win32.at has a too generic name. And what if
some non-win32 platform needs this? I think the test should be named
tests/bindir.at (or inst-bindir.at) since that is what is tested.
How
Charles Wilson wrote:
So, here's the revised function (w/o the varname uglification):
*) func_dirname $tlibdir
tlibdir=${func_dirname_result}
if test x$tlibdir = x ; then
# Have to descend all the way to the root!
Thanks to Chuck and Peter for their comments, here's the respun patch, also
with documentation.
libtool/ChangeLog:
* Makefile.am (TESTSUITE_AT): Add pe-dll-inst-bindir.at.
* libltdl/config/general.m4sh (func_relative_path): New function.
* libltdl/config/ltmain.m4sh
Oops. Forgot to change the test names when I renamed win32.at; fixed in this
revision. Tests run to completion this time, with no regressions.
libtool/ChangeLog:
* Makefile.am (TESTSUITE_AT): Add pe-dll-inst-bindir.at.
* libltdl/config/general.m4sh (func_relative_path): New
When generating the preloaded module glue code libtool generates invalid
prototypes without argument lists. When compiling with slightly fascist
compiler options (-Wstrict-prototypes) this has the effect of causing
gcc to print gazillions of warnings when the final libtool call is done
-- for each
Hi Folks,
I want to instrument apache 2.0 with IBM Purify Plus.
Given that Apache 2.0 uses libtool and the compilation and linking
happens in separate phases, we need to include purify in the link line
for the instrumentation to be successful.
Can anybody tell me which file has to be modified
On Wed, Aug 5, 2009 at 8:04 PM, John Wohlbier johnwohlb...@gmail.comwrote:
I'm using libtool in a project where I'm compiling code for the cell
processor. The cell requires different compilers to be used on sources
compiled for the PowerPC core (PPU) and the synergistic processing unit
(SPU).
Hello Joseph,
* Joseph Garvin wrote on Wed, Aug 05, 2009 at 11:32:31PM CEST:
I read a description of libtool's versioning here:
http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
What's confusing to me is that this way of handling versioning doesn't seem
to
Ralf Wildenhues ralf.wildenh...@gmx.de - Tue, 11 Aug 2009 19:34:09
+0200
Hello Michel,
* Michel Briand wrote on Thu, Aug 06, 2009 at 12:46:00AM CEST:
Personally I've always seen interface as a contract.
A contract between a library writer and library user.
Yes.
Why does libtool want to
* Michel Briand wrote on Tue, Aug 11, 2009 at 07:53:50PM CEST:
Yes non-Linux system will have a different scheme. But if libtool wants
to help I'm sure a little more documentation could easier the task :).
# create shared lib
mylib_la_LDFLAGS = -version-info $(MYLIB_LTVERSION)
This last
Hello Pankaj,
please keep the mailing list in Cc:, and don't top-post; thank you.
* Agrawal, Pankaj wrote on Tue, Aug 11, 2009 at 08:39:36PM CEST:
However, I am running still into troubles trying to use purify with
apache that uses libtool.
/bin/bash
Michel Briand wrote:
This last variable is crafted
crafted? This is your mistake.
to reflect the usual versioning. I.e. if
I want the version to 1.22.5,
Why? Why do you CARE what the internal ABI version number is? It's just
a tag; you shouldn't care WHAT it is, only that it changes ONLY
Hello John,
* John R. Cary wrote on Tue, Aug 04, 2009 at 03:35:41PM CEST:
libtool uses LD_RUN_PATH on Linux to pass the runtime
link dirs.
Unfortunately, OpenMPI's mpicxx ignores the envvar, does
not pass it through to g++.
I'm not sure I understand. libtool exports this environment
Charles Wilson libt...@cwilson.fastmail.fm - Tue, 11 Aug 2009
14:50:33 -0400
Michel Briand wrote:
This last variable is crafted
crafted? This is your mistake.
to reflect the usual versioning. I.e. if
I want the version to 1.22.5,
Why? Why do you CARE what the internal ABI version number
Hi Ralf,
If I use the below two commands, it still doesn't work. I have pasted an
error snapshot.
./configure --disable-shared CC=gcc
make CCLD='purify gcc'
* Agrawal, Pankaj wrote on Tue, Aug 11, 2009 at 09:36:01PM CEST:
If I use the below two commands, it still doesn't work. I have pasted an
error snapshot.
Thanks.
./configure --disable-shared CC=gcc
make CCLD='purify gcc'
/kassa04/softwares/agrpa02/httpd-2.2.12/srclib/apr/libtool --silent
Hello John,
* John R. Cary wrote on Fri, Aug 07, 2009 at 11:49:39PM CEST:
I am trying to use libtool to make a static executable:
/bin/sh ../libtool --tag=CXX --mode=link g++ -g -O2 -pipe -Wall
-Wno-unused-static -o uecxxst ../uebase/uedge.o libuecxxst.la
Michel Briand wrote:
Thank you, but, sorry, I'm not convinced. Remember what I said a
few mails ago: that's all of interface contract = same concept as
your...
Does anyone uses 10 or 16 to refer to their ABI ? Hum... So those
numbers have to be managed somewhere...
Yes. Here are a few
The whole story is that I never wanted to use libtool in the first
place.
And, now, I know why :).
___
http://lists.gnu.org/mailman/listinfo/libtool
Sorry for my last post : too quick answer :))
Charles Wilson cyg...@cwilson.fastmail.fm - Tue, 11 Aug 2009 16:45:58
-0400
Michel Briand wrote:
Thank you, but, sorry, I'm not convinced. Remember what I said a
few mails ago: that's all of interface contract = same concept as
your...
Does
On Wed, 12 Aug 2009, Michel Briand wrote:
I've looked into many OSS and found in Makefile.am only 2 cases :
- version-info 1:0:0 (the guys there didn't want to bother with
libtool versioning apparently... ;))
- version-info with the X.Y.Z version back crafted to make
the soname version
On Wed, 12 Aug 2009, Michel Briand wrote:
Please give me the way to learn those ABI number you cite.
I've looked into many OSS and found in Makefile.am only 2 cases :
- version-info 1:0:0 (the guys there didn't want to bother with
libtool versioning apparently... ;))
- version-info with the
Michel Briand wrote:
libavutil49-0.4.9-3.pre1.8994.2plf2008.0
ABI=49, pkgver=0.4.9
Please give me the way to learn those ABI number you cite.
libavutil49-0.4.9-stuff
^^
is usually used by the distribution (Red Hat? Debian?) to indicate that
* Vincent Torri wrote on Wed, Aug 12, 2009 at 12:33:47AM CEST:
if i'm not mistaken, you can compute le libtool versioning from the
version of the software. If the version of the software is X.Y.Z,
the libtool version can be computed with : (X+Y).Z.Y
No, it can not, for two reasons: 1) the
On Wed, 12 Aug 2009, Ralf Wildenhues wrote:
* Vincent Torri wrote on Wed, Aug 12, 2009 at 12:33:47AM CEST:
if i'm not mistaken, you can compute le libtool versioning from the
version of the software. If the version of the software is X.Y.Z,
the libtool version can be computed with :
* Vincent Torri wrote on Wed, Aug 12, 2009 at 07:15:16AM CEST:
On Wed, 12 Aug 2009, Ralf Wildenhues wrote:
* Vincent Torri wrote on Wed, Aug 12, 2009 at 12:33:47AM CEST:
if i'm not mistaken, you can compute le libtool versioning from the
version of the software. If the version of the
On Wed, 12 Aug 2009, Ralf Wildenhues wrote:
* Vincent Torri wrote on Wed, Aug 12, 2009 at 07:15:16AM CEST:
On Wed, 12 Aug 2009, Ralf Wildenhues wrote:
* Vincent Torri wrote on Wed, Aug 12, 2009 at 12:33:47AM CEST:
if i'm not mistaken, you can compute le libtool versioning from the
version
The apache source tar is available at
http://httpd.apache.org/download.cgi. Please download the Unix source
for v2.2.13.
-Original Message-
From: Ralf Wildenhues [mailto:ralf.wildenh...@gmx.de]
Sent: Wednesday, 12 August 2009 1:31 AM
To: Agrawal, Pankaj
Cc: libtool@gnu.org
Subject: Re:
30 matches
Mail list logo
