public inbox for
help / color / mirror / Atom feed
Subject: gdb and binutils branch master updated. 6b91c5417cb082f701fa9fca6d67e3ffb55ff73a
Date: Sat, 03 Jan 2015 22:55:00 -0000	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  6b91c5417cb082f701fa9fca6d67e3ffb55ff73a (commit)
      from  e1e061e77d517f1fcc6678667903b3d84c399323 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------;h=6b91c5417cb082f701fa9fca6d67e3ffb55ff73a

commit 6b91c5417cb082f701fa9fca6d67e3ffb55ff73a
Author: Andrew Pinski <>
Date:   Sat Jan 3 14:54:45 2015 -0800

    [GCC bug #63539]: libgo does not use the newly built objcopy when doing a combined build
    2015-01-03  Andrew Pinski  <>
            * Makefile.def (flags_to_pass): Pass OBJCOPY_FOR_TARGET also.
            * Makefile.tpl (HOST_EXPORTS): Add OBJCOPY_FOR_TARGET.
            (OBJCOPY_FOR_TARGET): New variable.
            * Regenerate.
            * Check for already installed target objcopy.
            Also GCC_TARGET_TOOL on objcopy.
            * configure: Regenerate.


Summary of changes:
 ChangeLog    |   12 +++
 Makefile.def |    1 +  |    5 +
 Makefile.tpl |    4 +
 configure    |  276 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |    2 +
 6 files changed, 300 insertions(+), 0 deletions(-)

gdb and binutils

                 reply	other threads:[~2015-01-03 22:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).