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] Allow linking GDB with ncursesw Date: Tue, 26 Sep 2017 17:12:00 -0000 [thread overview] Message-ID: <5007d765ae09c10c7f3b18bb16841b9d2d59e181@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 5007d765ae09c10c7f3b18bb16841b9d2d59e181 *** Author: Matthias Klose <doko@ubuntu.com> Branch: master Commit: 5007d765ae09c10c7f3b18bb16841b9d2d59e181 Allow linking GDB with ncursesw Triggered by https://launchpad.net/bugs/1275210, to be able to cope with UTF-8 characters in gdbtui. Reference: https://sourceware.org/ml/gdb-patches/2017-09/msg00356.html gdb/ChangeLog: 2017-09-26 Matthias Klose <doko@ubuntu.com> * configure.ac: Search ncursesw before ncurses. Check ncursesw/ncurses.h before ncurses/ncurses.h. * gdb_curses.h: Include <ncursesw/ncurses.h> * config.in, configure: Regenerate.
next reply other threads:[~2017-09-26 16:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-26 17:12 sergiodj+buildbot [this message] 2017-09-26 17:15 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2017-09-26 17:35 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-09-26 17:47 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-09-26 17:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-26 17:48 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-09-26 17:48 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-26 18:11 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-09-26 20:58 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-09-26 22:02 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-09-26 22:33 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-26 23:12 ` 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=5007d765ae09c10c7f3b18bb16841b9d2d59e181@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: linkBe 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).