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] Do not use buildsym.h in some files Date: Fri, 20 Jul 2018 19:44:00 -0000 [thread overview] Message-ID: <da6580e59c5c2c5dda086f9c407688e79377e49e@gdb-build> (raw) *** TEST RESULTS FOR COMMIT da6580e59c5c2c5dda086f9c407688e79377e49e *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: da6580e59c5c2c5dda086f9c407688e79377e49e Do not use buildsym.h in some files A few files no longer need to include buildsym.h. gdb/ChangeLog 2018-07-20 Tom Tromey <tom@tromey.com> * arch-utils.c: Do not include buildsym.h. * mipsread.c: Do not include buildsym.h. * machoread.c: Do not include buildsym.h. * elfread.c: Do not include buildsym.h.
next reply other threads:[~2018-07-20 19:44 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-20 19:44 sergiodj+buildbot [this message] 2018-07-20 19:44 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-07-20 23:32 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-07-21 12:01 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-07-22 8:41 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-07-22 8:46 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-07-22 9:17 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-07-22 9:24 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-07-22 9:36 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-07-22 9:53 ` Failures on Fedora-x86_64-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=da6580e59c5c2c5dda086f9c407688e79377e49e@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).