From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 60768 invoked by alias); 11 Feb 2016 03:24:25 -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 60759 invoked by uid 89); 11 Feb 2016 03:24:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.3 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*RU:sk:BAY004-, Hx-spam-relays-external:sk:BAY004-, H*r:sk:BAY004-, 3.6 X-HELO: BAY004-OMC1S8.hotmail.com Received: from bay004-omc1s8.hotmail.com (HELO BAY004-OMC1S8.hotmail.com) (65.54.190.19) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA256 encrypted) ESMTPS; Thu, 11 Feb 2016 03:24:24 +0000 Received: from BAY169-W11 ([65.54.190.59]) by BAY004-OMC1S8.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 10 Feb 2016 19:24:22 -0800 X-TMN: [V5foSOZUMpd8Lh99+jG6Q+UHTxbLWz7EGEWHGAYuPF4=] Message-ID: From: Tony Kelman To: "cygwin@cygwin.com" Subject: RE: [ANNOUNCEMENT] Assorted MinGW-w64 toolchain libraries and tools Date: Thu, 11 Feb 2016 03:24:00 -0000 In-Reply-To: <56BBDCBE.2050208@cygwin.com> References: ,<56BBDCBE.2050208@cygwin.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00154.txt.bz2 > Not MinGW applications, unless they are Cygwin-hosted tools used for > cross-compiling (which I think we have pretty well covered). Not even things like rustc, node.js, or julia which cannot be compiled as cygwin-linked applications (rust might be possible but I don't think anyone has tried recently) but can be compiled as mingw applications? Or are you suggesting those should remain distributed via their own channels rather than cygwin-packaged now that a few of the mingw libraries they depend on are starting to be included in the distro (and the remainder could be added). Seeing the cross-compiled libraries become available removes some of the need people may have to use a certain popular Cygwin fork, which does have quite a few mingw applications packaged as well. > LLVM/Clang version bumps are time-consuming to get right. I actually > looked at 3.6, but MCJIT did not work OOTB with PE/COFF targets. I'll > have to see what the story is with 3.7. Understandable. 3.8 is in RC right now so maybe try building the release_38 branch if you get to it soon, otherwise wait a few weeks. I'm trying to figure out how to cross-build mingw llvm via cmake now that they've deprecated autotools (it's still there in 3.8 with a warning, but has been deleted on trunk which will become 3.9). I'll check your i686-libgit2 package soon, but I suspect it may be affected by https://github.com/libgit2/libgit2/issues/3342 and need to be built with -mincoming-stack-boundary=3D2 -Tony =20=09=09=20=09=20=20=20=09=09=20=20 -- 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