Defines dependent on static/dynamic build

2003-11-24 Thread Bob Friesenhahn
I am faced with building some existing code that wants to have __STATIC__ defined while building a static library, and __DYNAMIC__ defined while building a shared library. Since only libtool knows what it is doing and libtool will make its own decisions, this seems difficult to accomplish using li

No pills, no pumps - Its the Patch mqxjerl

2003-11-24 Thread Candace Rosenberg
> ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

Re: bootstrapping CVS libtool

2003-11-24 Thread Scott James Remnant
On Mon, 2003-11-24 at 17:36, Bob Friesenhahn wrote: > On Mon, 24 Nov 2003, Scott James Remnant wrote: > > > > > I use Autoconf 2.58 and Automake 1.7 (latest Debian packages, basically) > > to bootstrap and it works just fine. > > The top of libtool's bootstrap script says: > > # Helps bootstrapp

Re: bootstrapping CVS libtool

2003-11-24 Thread Bob Friesenhahn
On Mon, 24 Nov 2003, Scott James Remnant wrote: > > > I use Autoconf 2.58 and Automake 1.7 (latest Debian packages, basically) > to bootstrap and it works just fine. The top of libtool's bootstrap script says: # Helps bootstrapping libtool, when checked out from CVS # requires at least GNU autoco

Re: bootstrapping CVS libtool

2003-11-24 Thread Scott James Remnant
On Sat, 2003-11-22 at 16:41, Bob Friesenhahn wrote: > I am trying to get the current CVS libtool properly bootstrapped. The > libtool bootstrap script says that GNU autoconf 2.58 and GNU automake > 1.8 are required. There is no such thing as automake 1.8 yet. I > retrieved a package called autom

Re: bootstrapping CVS libtool

2003-11-24 Thread Bob Friesenhahn
On Mon, 24 Nov 2003, Scott James Remnant wrote: > > > Running configure still does not result in a libtool script so I get > > this error: > > > > /home/bfriesen/src/gnu/libtool' > > CONFIG_FILES= CONFIG_HEADERS= CONFIG_COMMANDS=libtool > > /usr/local/bin/bash ./config.status > > config.status: exe

Re: configuring libltdl

2003-11-24 Thread Bob Friesenhahn
On Mon, 24 Nov 2003, Gary V. Vaughan wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Bob Friesenhahn wrote: > | It seems to me that for packages which embed libtool and use libltdl, > | it is very trivial for the package's configure script to also > | configure libltdl. This is *much

Re: 02-ac-shell-func.patch

2003-11-24 Thread Gary V. Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paolo Bonzini wrote: | 3) Do you want to release a 2.60 for m4 2.0? If so, Gary recently wrote | on the libtool mailing list that you'll have to wait much before m4 | stabilizes on all the OSes on which Autoconf should run. ...before relying on new fea

Re: configuring libltdl

2003-11-24 Thread Gary V. Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bob Friesenhahn wrote: | It seems to me that for packages which embed libtool and use libltdl, | it is very trivial for the package's configure script to also | configure libltdl. This is *much* more efficient time-wise and | space-wise than a recursiv

problem with including purify in a project using libtool on RedHat Linux 8.0

2003-11-24 Thread Rob
hello, ive to find memory leaks in a plugin for a big project called partysip. to manage this ive to compile and link the whole project with a memory detection program. i use a trial version of rational purify. purify is involved in the project by putting "purify" in front of the call to gcc (i