bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: Messed up gl_COMPILER_PREPARE_CHECK_DECL
Date: Fri, 10 Jan 2020 17:32:51 -0800	[thread overview]
Message-ID: <a756fe02-debc-e0db-9fd9-ea01c837950f@cs.ucla.edu> (raw)
In-Reply-To: <14916853.LUQoWjy5sj@omega>

On 1/10/20 2:47 PM, Bruno Haible wrote:
> Thanks for the simple-to-reproduce recipe. I've pushed this fix:

Unfortunately even with that fix I still have trouble building Emacs. 
That is, with this recipe:

mkdir d
cd d
git clone https://git.savannah.gnu.org/git/emacs.git
cd emacs
admin/merge-gnulib
./autogen.sh
./configure
make

(same recipe as before, but now with "configure; make" at the end) the 
build now fails this way:

   CC       strtoimax.o
strtoimax.c:44:15: error: redundant redeclaration of ‘strtoll’ 
[-Werror=redundant-decls]
    44 | long long int strtoll (char const *, char **, int);
       |               ^~~~~~~
In file included from ./stdlib.h:36,
                  from strtoimax.c:26:
/usr/include/stdlib.h:200:22: note: previous declaration of ‘strtoll’ 
was here
   200 | extern long long int strtoll (const char *__restrict __nptr,
       |                      ^~~~~~~
make[1]: *** [Makefile:95: strtoimax.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/eggert/src/gnu/emacs/static-checking/lib'
make: *** [Makefile:411: lib] Error 2


The above diagnostic comes because src/config.h contains the line 
"#define HAVE_DECL_STRTOLL 0" which is incorrect for this platform. And 
that incorrect line comes because ac_compile_for_check_decl is used 
before it is set. And this occurs because Emacs's configure.ac's first 
use of AC_CHECK_DECL is executed only on alpha platforms (which my 
platform is not), which means the initialization of 
ac_compile_for_check_decl is skipped.


  reply	other threads:[~2020-01-11  1:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 15:11 Messed up gl_COMPILER_PREPARE_CHECK_DECL Mats Erik Andersson
2020-01-10 20:14 ` Bruno Haible
2020-01-10 21:36   ` Mats Erik Andersson
2020-01-10 22:06   ` Paul Eggert
2020-01-10 22:47     ` Bruno Haible
2020-01-11  1:32       ` Paul Eggert [this message]
2020-01-13 19:02         ` Bruno Haible
2020-01-14  0:38           ` Paul Eggert
2020-01-18 13:14             ` Bruno Haible
2020-01-18 13:34               ` Bruno Haible
2020-01-18 15:31                 ` Mats Erik Andersson
2020-01-18 18:11                   ` Bruno Haible
2020-01-18 22:02                     ` Mats Erik Andersson
2020-01-18 22:19                       ` Bruno Haible
2020-01-18 21:39               ` Paul Eggert
2020-01-18 22:11                 ` Bruno Haible
2020-01-18 22:23                   ` Paul Eggert
2020-01-18 22:32                     ` Bruno Haible
2020-01-18 17:58             ` Bruno Haible

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a756fe02-debc-e0db-9fd9-ea01c837950f@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).