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] Build gdb "nat" files in subdirectory Date: Thu, 27 Dec 2018 21:27:00 -0000 [thread overview] Message-ID: <6987262214a204ea3ab857d86a1faf9f4e66f211@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 6987262214a204ea3ab857d86a1faf9f4e66f211 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: 6987262214a204ea3ab857d86a1faf9f4e66f211 Build gdb "nat" files in subdirectory This moves the various "nat" object files into the nat/ subdirectory. This allows for the removal of a pattern rule from the gdb Makefile, which is a small cleanup. I made the configure.nat change in a (semi-) automated way, hopefully meaning that it is more likely to be correct than had I done it by hand. Eventually I would like for the various configure scripts to only mention source files, and let the Makefile compute the object file names. gdb/ChangeLog 2018-12-27 Tom Tromey <tom@tromey.com> * configure.nat (NATDEPFILES): Use nat/ prefix. * Makefile.in (CONFIG_SRC_SUBDIR): Add nat. (%.o: ${srcdir}/nat/%.c): Remove rule. (INIT_FILES): Do not filter out NATDEPFILES.
next reply other threads:[~2018-12-27 21:10 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-27 21:27 sergiodj+buildbot [this message] 2018-12-27 21:28 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-12-28 2:11 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-12-28 2:28 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-12-28 2:36 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-12-28 3:18 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-12-28 3:29 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-12-28 3:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-12-28 4:10 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-12-28 4:15 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-12-28 4:18 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-12-28 4:33 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-12-28 4:54 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-12-28 6:11 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-12-28 6:47 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " sergiodj+buildbot 2018-12-28 7:03 ` Failures on Ubuntu-Aarch64-m64, " 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=6987262214a204ea3ab857d86a1faf9f4e66f211@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).