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 undefined reference to bfd_link_plugin_object_p during link
Date: Fri, 24 Jun 2016 17:34:00 -0000	[thread overview]
Message-ID: <08ce1d723ea3360a8ae52a4a4bd395ec984563eb@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 08ce1d723ea3360a8ae52a4a4bd395ec984563eb ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 08ce1d723ea3360a8ae52a4a4bd395ec984563eb

fix undefined reference to bfd_link_plugin_object_p during link

When configured with the default options, GDB currently fails to link,
due to an undefined reference to bfd_link_plugin_object_p, coming from
elflink.c:

    #ifdef BFD_SUPPORTS_PLUGINS
           || (abfd->plugin_format == bfd_plugin_unknown
              && bfd_link_plugin_object_p (abfd))
    #endif

This is because BFD_SUPPORTS_PLUGINS is always defined. It is its value
that determines whether plugin support is enabled or not.

bfd/ChangeLog:

        * elflink.c: Check the value of BFD_SUPPORTS_PLUGINS rather
        than its existance.


             reply	other threads:[~2016-06-24 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 17:34 sergiodj+buildbot [this message]
2016-06-24 17:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 17:36 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-06-24 18:18 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-06-25 13:26 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-06-25 13:30 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-06-25 14:31 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-06-25 21:39 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-06-25 22:03 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-07-16  5: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=08ce1d723ea3360a8ae52a4a4bd395ec984563eb@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: link
Be 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).