public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Peter Foley <pefoley2@pefoley.com>
To: cygwin-patches@cygwin.com
Subject: Update toplevel files from gcc
Date: Mon, 21 Mar 2016 16:44:00 -0000	[thread overview]
Message-ID: <CAOFdcFNPgJrf3KcNaOvmoT+Aj3Gp46w=ob=okPT0vwJ4TvMTCg@mail.gmail.com> (raw)

When building a cross compiler targeting cygwin, the target objcopy
binary wasn't properly picked up.
It appears that a fix for this has been commited to the gcc tree
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=fc740d700395d97b6719e8a0e64f75d01ab0d8fd

A patch to copy the updated Makefile.def, Makefile.tpl and
configure.ac from gcc and regenerate Makefile.in and configure is
1.4M, so too large to send to the mailing list.

Would it be possible for someone to sync the latest toplevel files from gcc?

Thanks,

Peter Foley

             reply	other threads:[~2016-03-21 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 16:44 Peter Foley [this message]
2016-03-21 19:26 ` Corinna Vinschen
2016-03-21 20:05   ` Peter Foley
2016-03-23 10:41     ` Corinna Vinschen
2016-03-23 12:58       ` Peter Foley

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='CAOFdcFNPgJrf3KcNaOvmoT+Aj3Gp46w=ob=okPT0vwJ4TvMTCg@mail.gmail.com' \
    --to=pefoley2@pefoley.com \
    --cc=cygwin-patches@cygwin.com \
    /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).