[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building bison from master fails: "conflicting types for 'code_get_l

From: Stefano Lattarini
Subject: Re: Building bison from master fails: "conflicting types for 'code_get_leng'"
Date: Tue, 15 May 2012 17:59:42 +0200

On 05/15/2012 11:23 AM, Akim Demaille wrote:
> Could you please try the attached patch?  Also in the
> branch "next" at the moment.
Bootstrapping the 'next' branch fails for me with:

  Don't forget to
    - "include gnulib.mk" from within "lib/Makefile.am",
    - mention "-I m4" in ACLOCAL_AMFLAGS in Makefile.am,
    - mention "m4/gnulib-cache.m4" in EXTRA_DIST in Makefile.am,
    - invoke gl_EARLY in ./configure.ac, right after AC_PROG_CC_STDC,
    - invoke gl_INIT in ./configure.ac.
  running: AUTOPOINT=true LIBTOOLIZE=true autoreconf --verbose --install \
                                                     --no-recursive -I m4
  autoreconf2.50: Entering directory `.'
  autoreconf2.50: running: true
  autoreconf2.50: running: aclocal -I m4 -I m4
  autoreconf2.50: configure.ac: tracing
  autoreconf2.50: configure.ac: not using Libtool
  autoreconf2.50: running: /usr/bin/autoconf --include=m4
  configure.ac:122: error: possibly undefined macro: AC_PROG_GNU_M4
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
  autoreconf2.50: /usr/bin/autoconf failed with exit status: 1

The same happens if I apply your patch on master.  Weird.

More info that might be useful:

  $ autoconf --version
  autoconf (GNU Autoconf) 2.69
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+/Autoconf: GNU GPL version 3 or later
  <http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by David J. MacKenzie and Akim Demaille.
  Autoconf 2.50 chosen by Debian wrapper script.
  For information and tuning advice see autoconf(1).

But the same failure happens with autoconf 2.69 installed from the tarball.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]