public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Define MPFR_USE_INTMAX_T so that mpfr.h assumes intmax_t is available.
Date: Thu, 30 Nov 2017 01:14:00 -0000 [thread overview]
Message-ID: <7505954411a168f5c5b9adec23eac55b1532fbe6@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7505954411a168f5c5b9adec23eac55b1532fbe6 ***
Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 7505954411a168f5c5b9adec23eac55b1532fbe6
Define MPFR_USE_INTMAX_T so that mpfr.h assumes intmax_t is available.
mpfr.h uses a non-portable test to guess if intmax_t is available and
if API functions using intmax_t should be exposed. Define
MPFR_USE_INTMAX_T to override the non-portable test and always expose
these functions. This fixes the build on platforms where the test
guesses incorrectly.
gdb/ChangeLog:
* target-float.c [HAVE_LIBMPFR]: Define MPFR_USE_INTMAX_T.
next reply other threads:[~2017-11-30 1:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 1:14 sergiodj+buildbot [this message]
2017-11-30 1:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-11-30 3:34 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-11-30 4:05 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-11-30 5:35 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-11-30 6:17 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-11-30 6:35 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-11-30 6:52 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-11-30 16:44 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-30 17:24 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-11-30 18:02 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7505954411a168f5c5b9adec23eac55b1532fbe6@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@sourceware.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).