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] Fix gdb 8.1 Solaris compilation Date: Fri, 22 Sep 2017 09:29:00 -0000 [thread overview] Message-ID: <4fa7574eecb9a92ef40f77de572541e402a2749e@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 4fa7574eecb9a92ef40f77de572541e402a2749e *** Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> Branch: master Commit: 4fa7574eecb9a92ef40f77de572541e402a2749e Fix gdb 8.1 Solaris compilation I just tried to compile gdb trunk on Solaris 11.4 (formerly 12), and failed for a couple of reasons: * In file included from /usr/include/python2.7/Python.h:128:0, from /vol/src/gnu/gdb/gdb/dist/gdb/python/python-internal.h:94, from /vol/src/gnu/gdb/gdb/dist/gdb/python/py-instruction.h:23, from /vol/src/gnu/gdb/gdb/dist/gdb/python/py-instruction.c:21: /usr/include/python2.7/ceval.h:67:0: error: ignoring #pragma no_inline [-Werror=unknown-pragmas] #pragma no_inline(PyEval_EvalFrameEx) ^ New in Solaris 11.4: <python2.7/ceval.h> uses a Studio-only #pragma. I've disabled the warning in warnings.m4. * /vol/src/gnu/gdb/gdb/dist/gdb/ser-pipe.c: In function int pipe_open(serial*, const char*): /vol/src/gnu/gdb/gdb/dist/gdb/ser-pipe.c:77:9: error: pid_t vfork() is deprecated (declared at /usr/include/unistd.h:659) [-Werror=deprecated-declarations] pid = vfork (); ^ /vol/src/gnu/gdb/gdb/dist/gdb/ser-pipe.c:77:16: error: pid_t vfork() is deprecated (declared at /usr/include/unistd.h:659) [-Werror=deprecated-declarations] pid = vfork (); ^ Since Solaris 11, vfork () is marked deprecated in <unistd.h>. cf. vfork(2): The vfork() and vforkx() functions are deprecated. Their sole legiti- mate use as a prelude to an immediate call to a function from the exec family can be achieved safely by posix_spawn(3C) or posix_spawnp(3C). Again, I've disabled the warning. * /vol/src/gnu/gdb/gdb/dist/gdb/cli/cli-cmds.c: In function void shell_escape(const char*, int): /vol/src/gnu/gdb/gdb/dist/gdb/cli/cli-cmds.c:750:14: error: pid_t vfork() is deprecated (declared at /usr/include/unistd.h:659) [-Werror=deprecated-declarations] if ((pid = vfork ()) == 0) ^ /vol/src/gnu/gdb/gdb/dist/gdb/cli/cli-cmds.c:750:21: error: pid_t vfork() is deprecated (declared at /usr/include/unistd.h:659) [-Werror=deprecated-declarations] if ((pid = vfork ()) == 0) ^ Same problem. * /vol/src/gnu/gdb/gdb/dist/gdb/procfs.c: In function void procfs_init_inferior(target_ops*, int): /vol/src/gnu/gdb/gdb/dist/gdb/procfs.c:4380:30: error: START_INFERIOR_TRAPS_EXPECTED was not declared in this scope gdb_startup_inferior (pid, START_INFERIOR_TRAPS_EXPECTED); ^ defined in nat/fork-inferior.h, need to include that header /vol/src/gnu/gdb/gdb/dist/gdb/procfs.c: In function void procfs_create_inferior(target_ops*, const char*, const string&, char**, int): /vol/src/gnu/gdb/gdb/dist/gdb/procfs.c:4605:38: error: fork_inferior was not declared in this scope NULL, NULL, shell_file, NULL); ^ likewise /vol/src/gnu/gdb/gdb/dist/gdb/procfs.c: In function void procfs_info_proc(target_ops*, const char*, info_proc_what): /vol/src/gnu/gdb/gdb/dist/gdb/procfs.c:5124:20: error: argv was not declared in this scope for (char *arg : argv) ^ Typo, should be built_argv instead! * Undefined first referenced symbol in file fork_inferior(char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char**, void (*)(), void (*)(int), void (*)(), char const*, void (*)(char const*, char* const*, char* const*)) procfs.o startup_inferior(int, int, target_waitstatus*, ptid_t*) fork-child.o ld: fatal: symbol referencing errors collect2: error: ld returned 1 exit status make[2]: *** [Makefile:2249: gdb] Error 1 Need to add fork-inferior.o to NATDEPFILES. With the changes below, I can build gdb on sparcv9-sun-solaris2.11 and amd64-pc-solaris2.11 and a simple smoke test (gdb/gdb gdb/gdb) works.
next reply other threads:[~2017-09-22 9:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-22 9:29 sergiodj+buildbot [this message] 2017-09-22 9:30 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2017-09-22 9:37 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-09-22 9:46 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-09-22 10:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-22 13:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-22 14:13 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-22 14:13 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-09-22 14:17 ` 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=4fa7574eecb9a92ef40f77de572541e402a2749e@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).