public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] gdbsupport/configure.ac: source development.sh Date: Mon, 16 Mar 2020 00:30:51 -0400 [thread overview] Message-ID: <3d1e5a43cbe1780ea66df0fe091998ee61177899@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 3d1e5a43cbe1780ea66df0fe091998ee61177899 *** commit 3d1e5a43cbe1780ea66df0fe091998ee61177899 Author: Vyacheslav Petrishchev <vyachemail@gmail.com> AuthorDate: Wed Feb 26 12:32:03 2020 +0600 Commit: Simon Marchi <simon.marchi@efficios.com> CommitDate: Thu Mar 5 14:33:17 2020 -0500 gdbsupport/configure.ac: source development.sh [Commit message by Simon Marchi] The GDB build in non-development mode (turn development to false in bfd/development.sh if you want to try) is currently broken: CXXLD gdb /home/smarchi/src/binutils-gdb/gdb/disasm-selftests.c:218: error: undefined reference to 'selftests::register_test_foreach_arch(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, void (*)(gdbarch*))' /home/smarchi/src/binutils-gdb/gdb/disasm-selftests.c:220: error: undefined reference to 'selftests::register_test_foreach_arch(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, void (*)(gdbarch*))' /home/smarchi/src/binutils-gdb/gdb/dwarf2/frame.c:2310: error: undefined reference to 'selftests::register_test_foreach_arch(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, void (*)(gdbarch*))' /home/smarchi/src/binutils-gdb/gdb/gdbarch-selftests.c:168: error: undefined reference to 'selftests::register_test_foreach_arch(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, void (*)(gdbarch*))' /home/smarchi/src/binutils-gdb/gdbsupport/selftest.cc:96: error: undefined reference to 'selftests::reset()' This is because the gdbsupport configure script doesn't source bfd/development.sh to set the development variable. When $development is unset, GDB_AC_SELFTEST defaults to enabling selftests. I don't think the macro was written with this intention in mind, it just happens to be that way. So gdbsupport thinks selftests are enabled, while gdb thinks they are disabled. gdbsupport compiles in code that calls selftests:: functions, which are normally provided by gdb, but gdb doesn't provide them, hence the undefined references. Fix this by sourcing bfd/development.sh in gdbsupport/configure.ac, so that the development variable is set. gdbsupport/ChangeLog: * configure.ac: Added call development.sh. * configure: Regenerate. diff --git a/gdbsupport/ChangeLog b/gdbsupport/ChangeLog index c47bb4ebbb..6bfd676872 100644 --- a/gdbsupport/ChangeLog +++ b/gdbsupport/ChangeLog @@ -1,3 +1,8 @@ +2020-03-05 Vyacheslav Petrishchev <vyachemail@gmail.com> + + * configure.ac: Added call development.sh. + * configure: Regenerate. + 2020-03-05 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com> * .gitattributes: New file. diff --git a/gdbsupport/configure b/gdbsupport/configure index a4871f8d5b..e7a99e3ddf 100755 --- a/gdbsupport/configure +++ b/gdbsupport/configure @@ -6569,6 +6569,9 @@ fi am_cv_prog_cc_stdc=$ac_cv_prog_cc_stdc +# Set the 'development' global. +. $srcdir/../bfd/development.sh + # We require a C++11 compiler. Check if one is available, and if # necessary, set CXX_DIALECT to some -std=xxx switch. diff --git a/gdbsupport/configure.ac b/gdbsupport/configure.ac index 401e16f821..ab71a3cb36 100644 --- a/gdbsupport/configure.ac +++ b/gdbsupport/configure.ac @@ -33,6 +33,9 @@ AC_USE_SYSTEM_EXTENSIONS ACX_LARGEFILE AM_PROG_CC_STDC +# Set the 'development' global. +. $srcdir/../bfd/development.sh + # We require a C++11 compiler. Check if one is available, and if # necessary, set CXX_DIALECT to some -std=xxx switch. AX_CXX_COMPILE_STDCXX(11, , mandatory)
next reply other threads:[~2020-03-16 4:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-16 4:30 gdb-buildbot [this message] 2020-03-16 4:30 ` Failures on Fedora-x86_64-cc-with-index, branch master gdb-buildbot 2020-03-16 4:48 ` Failures on Fedora-i686, " gdb-buildbot 2020-03-16 5:36 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2020-03-16 5:42 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2020-03-16 6:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2020-03-18 5:57 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot 2020-03-18 7:30 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot 2020-03-19 1:10 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-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=3d1e5a43cbe1780ea66df0fe091998ee61177899@gdb-build \ --to=gdb-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).