public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Error Linking LTO programs using GCC6.4
Date: Wed, 27 Sep 2017 23:16:00 -0000	[thread overview]
Message-ID: <59cc266b.8d409d0a.cc500.02e7@mx.google.com> (raw)
In-Reply-To: <CAJygYd2i5i7HWb5Zk2KMyDuLitOM4OjOB4aez9C-_Day+1kZPA@mail.gmail.com>

On Wed, 27 Sep 2017 14:42:43, =?UTF-8?B?5Y+26Zuo6aOe?= wrote:
> This is actually not the same issue at
> https://cygwin.com/ml/cygwin/2017-09/msg00236.html
> 
> In my case, it is caused by latest binutils 2.28 , when using 2.25
> everything is fine (even with gcc-6.4)
> 
> Maybe we should hold back upgrading binutils , or maybe it need a more
> recent version? There seems to be binutils 2.29.1 now

Actually, it is the same issue:

    $ cygcheck -s | grep -e binutils -e gcc
    mingw64-x86_64-binutils                 2.25.0.1.23f238d-1     OK
    mingw64-x86_64-gcc-core                 6.3.0-1                OK
    mingw64-x86_64-gcc-g++                  6.3.0-1                OK

    $ cat z.cpp
    #include <iostream>
    main() {
      std::cout << "cout test\n";
    }

    $ x86_64-w64-mingw32-g++ -static -o z z.cpp
    $ ./z
    cout test

So, with both your post and my post, the issue is fixed by not using:

- binutils 2.28.1
- mingw64-x86_64-binutils 2.28.1
- mingw64-i686-binutils 2.28.1

which leaves the last working version:

- binutils 2.25.0
- mingw64-x86_64-binutils 2.25.0
- mingw64-i686-binutils 2.25.0


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-09-27 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 13:51 叶雨飞
2017-09-27 14:22 ` 叶雨飞
2017-09-27 22:18   ` 叶雨飞
2017-09-27 23:16     ` Steven Penny [this message]
2017-09-28  7:35       ` 叶雨飞
2017-09-27 18:26 ` Steven Penny

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=59cc266b.8d409d0a.cc500.02e7@mx.google.com \
    --to=svnpenn@gmail.com \
    --cc=cygwin@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).