From: Earnie B. <ear...@ya...> - 2002-04-04 12:55:14
|
Jean le Roux wrote: > > On Thu, Apr 04, 2002 at 06:47:33AM -0500, Earnie Boyd wrote: > > Jean le Roux wrote: > > > > > > I then proceeded to bootstrap my own project, which is where this > > > saga resumes :( > > > > > > # autoconf > > > configure.in:18: error: possibly undefined macro: AC_PROG_LIBTOOL > > > configure.in:20: error: possibly undefined macro:AC_LIBTOOL_WIN32_DLL > > > configure.in:21: error: possibly undefined macro: AC_LIBTOOL_DLOPEN > > > > > > > Uhm, this isn't an MSYS problem. Did you execute aclocal before > > autoconf? > > Yeah, it is off the MSys path, but i caught a thread about "comunity > building" earlier today.. so I thought I'd give it a try ;) > I didn't mean we shouldn't discuss it here. :) > I did indeed run aclocal before. By bootstrap does > > libtoolize --ltdl --force --copy > cd libltdl > aclocal -I /usr/local/share/aclocal > cd .. > aclocal -I /usr/local/share/aclocal > autoheader > automake --foreign --add-missing --copy > autoconf > > > > > > > Where are these macros?! Surely they are provided by autoconf &| m4. > > > > > > > Most of these should exist. The ones that don't are the argz.h header > > and the AC_FUNC_FORK, you'll need to provide these. As I read these > > warnings, you've not set up properly. You mention that autoconf > > installed in /usr/local/share/bin, but automake installed in > > /usr/local/bin. The triplet autotools need the same parent directory > > and it doesn't appear that you have that. > > the different install paths where with installing it under MSys. The > current installation that i'm using to bootstrap my project, is from > a RH7.2 box. > > I'm mosty concerned with these macros: > > configure.in:20: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL > configure.in:21: error: possibly undefined macro: AC_LIBTOOL_DLOPEN > configure.in:22: error: possibly undefined macro: AC_LIB_LTDL > configure.in:23: error: possibly undefined macro: AM_PROG_LIBTOOL > > because aclocal -I/usr/local/share/aclocal --verbose gives me > ... > Found macro AC_LIBTOOL_WIN32_DLL in /usr/local/share/aclocal/libtool.m4: 1530 > ... > > for example. So with the other three aswell. > > I realise this is not an MSys issue (yet) and will take the > discussion to the libtool list if you so desire. I figured that some > other folk on this might have the same pain though, since I ran into > it while trying to port code. > No, let's keep the discussion here until we determine that in fact it's not environment related. I'll download ActiveState's perl today. Do you have a good URL to do that? > *with 'yet' I mean it might become more regularly discussed here once > the autotools are provided (touch wood) :) > :) Hopefully soon. It sounds as if I need to modify my strategy to provide autotools with ActiveState perl dependency then do the MinGW build of perl. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |