[Top][All Lists]

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

Re: Cannot configure current cvs checkout

From: Paul Eggert
Subject: Re: Cannot configure current cvs checkout
Date: 26 Apr 2003 22:30:17 -0700
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

Martin MOKREJŠ <address@hidden> writes:

> ar cru libbison.a argmatch.o basename.o dirname.o get-errno.o getopt.o 
> getopt1.o hash.o mbswidth.o quote.o quotearg.o subpipe.o xmalloc.o xstrdup.o 
> xstrndup.o abitset.o bitset.o ebitset.o bitsetv.o bitset_stats.o lbitset.o 
> bitsetv-print.o timevar.o error.o error.o memrchr.o stpcpy.o strnlen.o 
> obstack.o malloc.o realloc.o
> ar: Warning: ignoring second definition of error defined in archive
> ar: Warning: ignoring second definition of error_at_line defined in archive

Thanks for reporting this problem.  It arises because Bison's invokes AC_FUNC_ERROR_AT_LINE twice; once directly, and
once via gl_ERROR.  If you invoke AC_FUNC_ERROR_AT_LINE twice,
"configure" attempts to put error.o in the archive twice, and this is
a mistake on your platform.  Perhaps this is a bug in

Anyway, I fixed the Bison problem by installing the following patch.
Bison never invokes error_at_line directly, only via error.c, so this
fix is the right thing to do even if AC_FUNC_ERROR_AT_LINE is buggy.

2003-04-26  Paul Eggert  <address@hidden>

        * (AC_FUNC_ERROR_AT_LINE): Remove, since gl_ERROR
        invokes it.  We shouldn't invoke it twice because it will attempt
        to put error.o in the archive twice.  This fixes a glitch reported
        by Martin Mokrejs in

---        Wed Mar 12 15:08:06 2003
+++        Sat Apr 26 22:18:22 2003
@@ -101,7 +101,6 @@ AC_CHECK_DECLS([free, getenv, getopt,
                 stpcpy, strchr, strspn, strnlen,
                 malloc, memchr, memrchr])
 AC_REPLACE_FUNCS(strchr strrchr strspn)

reply via email to

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