Hi Folks,
On Superbowl Sunday, I had a few hours to attempt compiling
the latest CVS gcc using cc, gnu-make, and the latest CVS autoconf.
That was a no-go.
Here's why I think it relates to autoconf. I pseudo-determined
that it was the cvs autoconf, so I replaced that (2.49d?) with
the 2.13.
| $ at_dir=`echo foo 2/dev/null`
| $ echo at_dir=$at_dir
| at_dir=foo
I don't understand this, it is not consistent with `cd'. Isn't `echo'
a builtin on your shell? Then I would understand.
Hm, what else must be a builtin? exit has to be.
foo=`exit 12 2/dev/null`
bar=`(exit 12) 2/dev/null`
I decided to give autoconf-2.49c a try on Cygwin.
In configuring the libtool package I
cd libtool-1.3.5
autoupdate
autoconf
cd libltdl
autoupdate
autoconf ;# Reports error.
The errors are:
configure.in:109: error: AC_REQUIRE: cannot be used outside of an
m4_defun'd macro
Akim Demaille wrote:
| I decided to give autoconf-2.49c a try on Cygwin.
| In configuring the libtool package I
| cd libtool-1.3.5
| autoupdate
| autoconf
| cd libltdl
| autoupdate
| autoconf ;# Reports error.
|
| The errors are:
|
| configure.in:109: error: AC_REQUIRE:
Akim Demaille wrote:
| /* Define if you have the iconv.h header file. */
| #undef HAVE_ICONV_H"
| /usr/local/bin/m4: configure.in: 462: ERROR: Recursion limit of 250 exceeded, use
-LN to change it
|
|
|
| The
Hello, Robert!
My understanding of the way Autoconf and Automake are supposed to work
was that anything that Autoconf did not recognize would be placed into
the Makefile.in without changes. I have been using VPATH with the
Right, but Autoconf does recognize VPATH. Recognizing VPATH is an
Akim,
I just downloaded a fresh CVS autoconf and did a build on the Ultrix
box.
This time, I was able to do the build in a subdir (builddir != srcdir).
The tail fragment of "make check" follows. Much better - I'll see if I
can install the GNU grep stuff and see if that helps.
Harlan
-
...
