The m4 versions are the same, 1.4.10 on both machines. The package in its current form isn't released, there are older versions available. If I try to rebuild an older version from scratch (e.g. rerun aclocal, autoheader, libtoolize, automake, and autoconf on it,) I get a useless configure script for that as well. It has to be something environment/executable related. Here's the output of running configure with sh -x. I attached all the request files. I can ask about posting this version on the list. Our software eventually makes it to open source --- this isn't yet ready for release though. I really appreciate the help, I'm totally stumped. Chris On 10/1/07, Ralf Wildenhues <Ralf.Wildenhues@xxxxxx> wrote: > Hello Chris, > > * Chris Inacio wrote on Mon, Oct 01, 2007 at 04:36:29PM CEST: > > > > We use autoconf for our software on multiple hosts, although in > > general, we tend to develop on Mac OS X. I have two Mac OS X machines > > which I can the autoconf packages (autoconf, automake, and libtool,) > > from MacPorts. I have two Mac OS X machines, each running the latest > > 10.4.10. The problem is that on one of the machines, for the exact > > same software package, autoconf builds a useless configure script, > > while on the other machine it works fine. > > Do the m4 versions on the machines differ? Can you post a link to the > package, or to the two configure scripts and the configure.ac file? > Is the broken configure script empty? If not, run it like > sh -x configure > > and post the output (preferably packed with bzip2 or gzip). > > Thanks, > Ralf >
Attachment:
autohelp.tar.bz2
Description: BZip2 compressed data
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
