Re: possibly undefined macro: AC_PROG_LIBTOOL (was: (no subject))

2006-06-12 Thread Harlan Stenn
Hi Ralf, > > autoconf 2.59 and libtool 1.5.6. > > > > I'm seeing this on a bunch of different systems > > > autoreconf259: configure.ac: not using Libtool > > configure.ac:10: error: possibly undefined macro: AC_PROG_LIBTOOL > > If this token and others are legitimate, please use m4_patt

possibly undefined macro: AC_PROG_LIBTOOL (was: (no subject))

2006-06-12 Thread Ralf Wildenhues
Hi Harlan, * Harlan Stenn wrote on Mon, Jun 12, 2006 at 08:41:34PM CEST: > > autoconf 2.59 and libtool 1.5.6. > > I'm seeing this on a bunch of different systems > autoreconf259: configure.ac: not using Libtool > configure.ac:10: error: possibly undefined macro: AC_PROG_LIBTOOL > If thi

(no subject)

2006-06-12 Thread Harlan Stenn
autoconf 2.59 and libtool 1.5.6. I'm seeing this on a bunch of different systems (the following is from FreeBSD, but I'm also seeing it on Solaris9 and 10, and some others): ... autoreconf259: configure.ac: not using Libtool configure.ac:10: error: possibly undefined macro: AC_PROG_LIBTOOL

Re: HP-UX hppa64 and gcc

2006-06-12 Thread Daniel Richard G.
Thanks for Cc'ing me on this. On Mon, 2006 Jun 12 01:30:09 -0500, Albert Chin wrote: > > See this thread: > > http://lists.gnu.org/archive/html/bug-libtool/2006-06/msg1.html > > Wow. That compiler is from June 2000! > > http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,

Re: changing compiler flags at configure time

2006-06-12 Thread Ralf Wildenhues
Hi Eric, * Eric Blake wrote on Mon, Jun 12, 2006 at 03:12:33PM CEST: > > CVS head of m4 currently has a macro, ltdl/m4/debug.m4, that attempts to > alter compile-time flags according to whether --enable-debug is passed to > ./configure. However, it uses AC_DISABLE_SHARED and AC_ENABLE_SHARED > i

changing compiler flags at configure time

2006-06-12 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 CVS head of m4 currently has a macro, ltdl/m4/debug.m4, that attempts to alter compile-time flags according to whether --enable-debug is passed to ./configure. However, it uses AC_DISABLE_SHARED and AC_ENABLE_SHARED inside a shell if-then-else to enfo

Re: libtool and MingW, MSVC support

2006-06-12 Thread Roger While
Look at what we have in OpenCOBOL for dynamic loading of modules : #ifdef USE_LIBDL #include #define lt_dlopen(x)dlopen(x, RTLD_LAZY | RTLD_GLOBAL) #define lt_dlsym(x, y) dlsym(x, y) #define lt_dlclose(x) dlclose(x) #define lt_dlerror()dlerror() #define lt_ptr_tvoid * #defin

Re: AW: libtool + MinGW

2006-06-12 Thread Ralf Wildenhues
* Brendon Costa wrote on Mon, Jun 12, 2006 at 10:46:29AM CEST: > Duft Markus wrote: > > > > Do you want to get it to work with the MinGW GCC, or with the MSVC > > toolchain (i.e. cl.exe, link.exe etc...) ? This makes a big > > difference, since libltdl is really useless with the MS toolchain. > >

Re: AW: libtool + MinGW

2006-06-12 Thread Brendon Costa
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Duft Markus wrote: > Hi! > > Do you want to get it to work with the MinGW GCC, or with the MSVC toolchain > (i.e. cl.exe, link.exe etc...) ? This makes a big difference, since libltdl > is really useless with the MS toolchain. > > I think we allrea

Re: libtool + MinGW

2006-06-12 Thread Brendon Costa
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Dessent wrote: > No, your example was flawed because it did not pass -no-undefined, which > means you get static libraries unconditionally. If you fix that, then > libtool builds both shared and static versions of the library, and it > successfu