Yes, this all started as a project to get Apache244 and tomcat 7 to talk to each other on Windows 7. Rather than installing a grouped package like xampp I decided to install standalone versions. Only issue though is that to get mod_jk (the connector), it seemed I would have to build Apache to get AXPS which didn't seem it was available in their tarballs. This led to the requirement to build apr and apr-util which led to the requirement to build autoconf which needs to have M4. (I think I got that straight).
Thanks I will see if I can set up a Linux VM to do the compiling then, worse comes to worse I will have to install XAMPP Alex -----Original Message----- From: Eric Blake [mailto:ebl...@redhat.com] Sent: Thursday, February 28, 2013 9:26 AM To: Alex Gonzalez Cc: bug-m4@gnu.org Subject: Re: GNU M4 Install On 02/27/2013 10:11 PM, Alex Gonzalez wrote: > Hello, > > on windows 7 - 64 > using CYGWIN 1.7.17-1 > trying to install m4 1.4.16 Why aren't you using the m4 pre-built for cygwin? > > Configured with: ../../../src/gcc-4.6.3/configure > --build=i686-w64-mingw32 --target=i686-w64-mingw32 > --enable-languages=c,c++,fortran --enable-libgomp --enable-lto > --enable-bootstrap --enable-checking=release > --enable-version-specific-runtime-libs --disable-multilib > --disable-nls --disable-win32-registry --disable-werror > --with-pkgversion='gcc-4.6.3 release with patches [build 20121012 by > perlmingw.sf.net]' --with-sysroot=/gccbuild/prefix/mingw32 > --with-gmp=/gccbuild/prefix/mingw32 > --with-mpfr=/gccbuild/prefix/mingw32 > --with-mpc=/gccbuild/prefix/mingw32 > --with-ppl=/gccbuild/prefix/mingw32 > --with-cloog=/gccbuild/prefix/mingw32 --enable-cloog-backend=isl > --with-bugurl=http://mingwfp.znix.com --with-gnu-ld > --prefix=/gccbuild/prefix/mingw32 > --with-local-prefix=/gccbuild/prefix/mingw32 > --with-libiconv-prefix=/gccbuild/prefix/mingw32 Oh, you aren't compiling for cygwin. You're trying to do a cross-compiler build for mingw. In which case, this is not a cygwin question, but a cross-build question related to mingw. Most likely, this is a situation where no one has ever cross-compiled - m4 1.4.16 was released before the 64-bit mingw project took off, so while modern gnulib may be able to cope with this situation, the version of gnulib used at the time of the m4 release obviously does not. It's been ages since I've attempted to do a cross-compile to mingw, but as I need to release m4 1.4.17 sometime anyways to resolve FTBFS on modern glibc, I'll try and do that before making a release. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
