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/gdb-8.0-branch] Fix gdb 8.0 procfs.c compilation on Solaris Date: Mon, 15 May 2017 12:58:00 -0000 [thread overview] Message-ID: <81aeac9bbd02fc80048e51a1bb67484eb58852dc@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 81aeac9bbd02fc80048e51a1bb67484eb58852dc *** Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> Branch: gdb-8.0-branch Commit: 81aeac9bbd02fc80048e51a1bb67484eb58852dc Fix gdb 8.0 procfs.c compilation on Solaris Prompted by the creation of the gdb 8.0 branch, I tried to build it on x86_64-pc-solaris2.12, but failed: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/procfs.c: In function `target_ops* procfs_target()': /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/procfs.c:186:27: error: invalid conversion from `void (*)(target_ops*, char*, char*, char**, int)' to `void (*)(target_ops*, const char*, const string&, char**, int) {aka void (*)(target_ops*, const char*, const std::__cxx11::basic_string<char>&, char**, int)}' [-fpermissive] t->to_create_inferior = procfs_create_inferior; ^~~~~~~~~~~~~~~~~~~~~~ /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/procfs.c: At global scope: /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/procfs.c:125:13: warning: `void procfs_create_inferior(target_ops*, char*, char*, char**, int)' declared `static' but never defined [-Wunused-function] static void procfs_create_inferior (struct target_ops *, char *, ^~~~~~~~~~~~~~~~~~~~~~ /vol/src/gnu/gdb/gdb-8.0-branch/local/gdb/procfs.c:4529:1: warning: `void procfs_create_inferior(target_ops*, const char*, const string&, char**, int)' defined but not used [-Wunused-function] procfs_create_inferior (struct target_ops *ops, const char *exec_file, ^~~~~~~~~~~~~~~~~~~~~~ This can easily be fixed by the following patch. * procfs.c (procfs_create_inferior): Change prototype to match definition.
next reply other threads:[~2017-05-15 12:58 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-15 12:58 sergiodj+buildbot [this message] 2017-05-15 12:58 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-8.0-branch sergiodj+buildbot 2017-05-15 13:12 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-05-15 13:28 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-05-15 13:28 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-05-15 13:33 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-05-15 13:40 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-05-15 13:54 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-05-15 13:55 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-05-15 14:09 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-05-15 14:10 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-05-15 14:11 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-05-15 14:56 ` 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=81aeac9bbd02fc80048e51a1bb67484eb58852dc@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).