From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88944 invoked by alias); 27 Sep 2017 22:30:40 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 88796 invoked by uid 89); 27 Sep 2017 22:30:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=GCC6.4, gcc6.4, Linking, 26Zuo6aOe X-HELO: mail-oi0-f43.google.com Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Sep 2017 22:30:14 +0000 Received: by mail-oi0-f43.google.com with SMTP id n82so13930250oib.8 for ; Wed, 27 Sep 2017 15:30:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:to:references:subject :user-agent; bh=fT/8BiYp9cGaKVtSvrNrN0gacLY1YBK4uki3V49WEaU=; b=aaX/1ND/BrvJ1ZGUheE8QPFtRC6AIjcaQXM7FYD3Z5Bb3L9KeLLoxp/77TGlytaLnt 1nm/8SOclWWNu2BbZbzMgmT2o7AEaR/8qVOUlnvePKMIono3/WfSARsM8tSzMuMCBXZN Tly5iLI+W8FFoA+k1Jq9tOG89s0JHNOylbYrucAP+o3Bp9A8HHnTRIXdrM6ATHhdfuXP +607iBx44DVaL6C1zTddLX9atSS70fKDj7mbp22EON/ZkX7e8BnpItdFMPH3qw97naMD M7MT13ALvkHLin7oFrL3i6buP/ujYxhroCqHzz3u9ABpJ90u9hZuMkMvXIuMKonVw8OJ PIfg== X-Gm-Message-State: AMCzsaX4/pPOgRh4E5NfKtRPLhSBgviAPQ47SYxnpUUWDMdk6vdSwzWw GDoP3GYWgs6buR1aZAb7lw2QEg== X-Google-Smtp-Source: AOwi7QC8vlSyNrK0LOOEJraY0IBBFfW62PR+UwZWWlFgxeoJjoz4l8a/NHRn5a8xUSUFCSzj2GN+lg== X-Received: by 10.157.16.37 with SMTP id h34mr138992ote.469.1506551404369; Wed, 27 Sep 2017 15:30:04 -0700 (PDT) Received: from rZo ([2605:6000:9fc0:56:3c14:e5c4:5a0e:92]) by smtp.gmail.com with ESMTPSA id n13sm23619ote.29.2017.09.27.15.30.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Sep 2017 15:30:03 -0700 (PDT) Message-ID: <59cc266b.8d409d0a.cc500.02e7@mx.google.com> Date: Wed, 27 Sep 2017 23:16:00 -0000 From: Steven Penny X-Google-Original-From: Steven Penny To: cygwin@cygwin.com References: Subject: Re: Error Linking LTO programs using GCC6.4 Content-Type: text/plain; charset=utf8; format=flowed User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst) X-SW-Source: 2017-09/txt/msg00290.txt.bz2 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 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