From: Tony Kelman <tony@kelman.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] Assorted MinGW-w64 toolchain libraries and tools
Date: Thu, 11 Feb 2016 03:24:00 -0000 [thread overview]
Message-ID: <BAY169-W114D538CCAD0DCF90FB2E5A7A80@phx.gbl> (raw)
In-Reply-To: <56BBDCBE.2050208@cygwin.com>
> 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=2
-Tony
--
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
next prev parent reply other threads:[~2016-02-11 3:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:51 Yaakov Selkowitz
2016-02-10 20:35 ` Tony Kelman
2016-02-11 0:58 ` Yaakov Selkowitz
2016-02-11 3:24 ` Tony Kelman [this message]
2016-02-11 3:25 ` Tony Kelman
2016-02-14 20:02 ` Tony Kelman
2016-02-14 21:43 ` Yaakov Selkowitz
2016-02-15 5:54 ` Ismail Donmez
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=BAY169-W114D538CCAD0DCF90FB2E5A7A80@phx.gbl \
--to=tony@kelman.net \
--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).