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] Require ngettext in test of system gettext implementation
Date: Tue, 07 Nov 2017 09:31:00 -0000 [thread overview]
Message-ID: <f3ce9b3a00229e5c6087180a74bf533d0e5201f3@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT f3ce9b3a00229e5c6087180a74bf533d0e5201f3 ***
Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: f3ce9b3a00229e5c6087180a74bf533d0e5201f3
Require ngettext in test of system gettext implementation
If binutils is going to use ngettext, then we'd better arrange for
intl/ to be compiled if the system gettext lacks ngettext.
* configure.ac: Invole AM_GNU_GETTEXT with need_ngettext.
* configure: Regenerate.
* aclocal.m4: Regenerate.
next reply other threads:[~2017-11-07 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 9:31 sergiodj+buildbot [this message]
2017-11-07 9:31 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2017-11-07 9:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-11-07 9:43 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-11-07 9:46 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-11-07 9:47 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-11-07 9:57 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-11-07 10:03 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-11-07 10:03 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-07 10:32 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-11-07 14:58 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-07 15:22 ` Failures on Ubuntu-AArch32-native-gdbserver-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=f3ce9b3a00229e5c6087180a74bf533d0e5201f3@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).