unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Build failure in gettimeofday
Date: Wed, 16 Sep 2020 17:41:58 +0300	[thread overview]
Message-ID: <83r1r17phl.fsf@gnu.org> (raw)
In-Reply-To: <3a0bcac5-7a7a-6334-03d3-57d32086b886@gmx.at> (message from martin rudalics on Wed, 16 Sep 2020 10:21:56 +0200)

> Cc: emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Wed, 16 Sep 2020 10:21:56 +0200
> 
> Thank you.  A -O0 -g3 build succeeds now but a -O3 build currently
> fails thusly:
> 
> In file included from ../../src/emacs.c:68:0:
> ../../src/bignum.h:25:17: fatal error: gmp.h: No such file or directory
>   #include <gmp.h>
>                   ^
> compilation terminated.
> make[1]: *** [emacs.o] Error 1

??? How did the -O0 build get past this problem?  Header file
inclusion doesn't depend on optimizations.  Are you sure you have a
clean working tree, devoid of stale object files?

Anyway, it sounds like you don't have GMP installed?  In that case,
running configure is supposed to create lib/gmp.h, and the above
inclusion in bignum.h is supposed to find it.  It works for me on a
system where there's no libgmp.  Do you have lib/gmp.h?  If you do,
then perhaps this is a compiler bug: it should be able to find that
file, because the compiler switches include "-I../lib".

If you don't have lib/gmp.h, then your tree is mis-configured somehow.

Or maybe this is another aspect of our less-than-ideal support for
out-of-tree builds.

> but I doubt that these can be relevant.  Any clues?  A couple of
> warnings from the -O0 build just in case they could hint at anything.
> 
>    CC       menu.o
> ../../src/xdisp.c: In function 'move_it_in_display_line_to':
> ../../src/xdisp.c:9557:10: warning: unknown conversion type character 't' in format [-Wformat=]
>            IT_CHARPOS (*it));
>            ^
> ../../src/xdisp.c:9557:10: warning: too many arguments for format [-Wformat-extra-args]
> ../../src/xdisp.c: In function 'move_it_to':
> ../../src/xdisp.c:9925:8: warning: unknown conversion type character 't' in format [-Wformat=]
>          move_trace ("move_it: from %td\n", IT_CHARPOS (*it));
>          ^
> ../../src/xdisp.c:9925:8: warning: too many arguments for format [-Wformat-extra-args]
> ../../src/xdisp.c:9928:8: warning: unknown conversion type character 't' in format [-Wformat=]

That's because of your ancient version of GCC.  You will have to live
with this.

> ../../src/data.c: In function 'bignum_arith_driver':
> ../../src/data.c:2821:9: warning: assignment from incompatible pointer type [enabled by default]
>     accum = &mpz[0];
>           ^
> ../../src/data.c:2843:13: warning: assignment from incompatible pointer type [enabled by default]
>         accum = &mpz[0];
>               ^

That's the usual noise with GCC 4.x when compiling mini-gmp.  I
reported this as a bug, but no one wants to fix it, so I guess us
providing mini-gmp is just a lip service, and you are advised to
install libgmp if you are annoyed enough by these warnings.



  reply	other threads:[~2020-09-16 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09  8:44 Build failure in gettimeofday martin rudalics
2020-09-09 14:34 ` Eli Zaretskii
2020-09-14  8:10   ` martin rudalics
2020-09-14 16:19     ` Eli Zaretskii
2020-09-15  8:06       ` martin rudalics
2020-09-15 15:13         ` Eli Zaretskii
2020-09-16  8:21           ` martin rudalics
2020-09-16 14:41             ` Eli Zaretskii [this message]
2020-09-17  8:14               ` martin rudalics
2020-09-17 13:42                 ` Eli Zaretskii
2020-09-18  7:48                   ` martin rudalics
2020-09-18  8:03                     ` Eli Zaretskii
2020-09-18  8:18                       ` martin rudalics
2020-09-18  8:25                         ` Eli Zaretskii

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83r1r17phl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).