public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: JonY <jon_y@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: [RFU] mingw-w64
Date: Wed, 31 Aug 2011 09:48:00 -0000	[thread overview]
Message-ID: <4E5E0369.50600@users.sourceforge.net> (raw)
In-Reply-To: <20110831091102.GJ30452@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

On 8/31/2011 17:11, Corinna Vinschen wrote:
> On Aug 31 15:15, JonY wrote:
>> Hi,
>>
>> Here's a refresh of the mingw-w64.
>>
>> For the headers and runtime, remove 4075 and 4214, for both i686 and x86_64 archs.
>> Please remove the oldest version for the others.
> 
> Done.  Btw., would you mind to restructure your download directories so
> that they resemble the structure of the Cygwin distro directories?  That
> would reduce the work required to upload your files enormously!
> 

OK, sorry about that, I'll do that next time.

SF is sadly lacking an FTP interface (why don't they have anonymous
read-only sftp?) to make recursive downloading even easier.

>> BTW, is GCC 4.6 for Cygwin anywhere near? :)
> 
> 4.5.3 is near, afaik.
> 

OK, I was wondering how to transition 4.5.x to 4.6.x for mingw-w64 when
the time comes, pthreads-win32 will be removed in favor of winpthreads,
they're not exactly ABI compatible. Right now, only libgomp is using
pthreads-win32.

C++ ABI for 4.6.x has also changed for mingw* (including mingw.org) with
the introduction of thiscall, not sure if this will affect Cygwin itself.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

  reply	other threads:[~2011-08-31  9:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31  7:15 JonY
2011-08-31  9:11 ` Corinna Vinschen
2011-08-31  9:48   ` JonY [this message]
2011-08-31 13:55     ` Charles Wilson
2011-08-31 14:13       ` Corinna Vinschen
2011-09-01  1:46         ` JonY
2011-09-01  2:08       ` JonY
2011-09-01  4:10         ` Charles Wilson
  -- strict thread matches above, loose matches on Subject: below --
2012-06-30 17:09 JonY
2012-07-02  9:23 ` Corinna Vinschen
2012-07-02  9:44   ` JonY
2012-07-02 10:40     ` Corinna Vinschen
2012-03-18 14:06 JonY
2012-03-18 14:12 ` Christopher Faylor
2012-03-18 14:29   ` Christopher Faylor
2011-12-18  4:36 JonY
     [not found] ` <1324242755.56938.YahooMailNeo@web114715.mail.gq1.yahoo.com>
2011-12-18 22:56   ` JonY
2011-12-19  0:42 ` Charles Wilson
2011-12-19 13:25   ` JonY
2011-12-20  9:54     ` Corinna Vinschen
2011-12-20 11:46       ` JonY
2011-12-20 14:19         ` Corinna Vinschen
2011-08-11 11:16 JonY
2011-08-11 12:33 ` Corinna Vinschen
2011-08-11 16:13   ` JonY
2011-08-11 18:28     ` Chris Sutcliffe
2011-08-11 22:36       ` JonY

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=4E5E0369.50600@users.sourceforge.net \
    --to=jon_y@users.sourceforge.net \
    --cc=cygwin-apps@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).