From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 20E1B1382C5 for ; Tue, 19 Jan 2021 06:58:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4DD1FE0880; Tue, 19 Jan 2021 06:58:04 +0000 (UTC) Received: from atfriesa01.ssi-schaefer.com (atfriesa01.ssi-schaefer.com [193.186.16.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id DE10CE0880 for ; Tue, 19 Jan 2021 06:58:03 +0000 (UTC) IronPort-SDR: AXqlR6O+A/PqTqkERTxqwkmEHzHByyoxMvUWpNs4uuWzIu9qFXlztSF9riCR37qNWBHZs0rZmU tg1h12ZQbQ+q60Tjvstdn1vwinMuGOUCo/hXJeNB4hmTafol4+JlFT2gOXnTbb+EQAm+1+KRU9 /latsYwsBsQkQio8//96awoznfydhSWrQRLOCQprlrUyOJ7KMKbC5rbemJtb2ZL0pkvOFRDu53 gEBFtL+dpK6innNNGyVA/SZjLqUA7AMeV9Al5S9NrHJX6PxFS9wI3AkW0eg86LV/eDJG+njh2r r0k= X-IronPort-AV: E=Sophos;i="5.79,358,1602540000"; d="scan'208,217";a="74999079" X-IPAS-Result: =?us-ascii?q?A2HhBACKgQZg/+shHKxihXmFeJFSlCCIHQsBAQEBAQEBA?= =?us-ascii?q?QEJIwwEAQEChEgCgXImOBMCAwEBCwEBAQUBAQEBAQYDAQIChk4Mg1WBBwEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEWAg1UaAEBAQECASNKEQsLBBQqAgJJAQ00gwyCZ?= =?us-ascii?q?i+uK3aBMoVagy6BIB0GgTiGdgGGQDWBTT+EKj6FC4JMgmAEgWWCBhCBW4EVk?= =?us-ascii?q?nSIe5wELAeCeoEXBQuICJJbgyqfQI8ihwCIS0qRYYR7gW2Be00jgzoRPhkNl?= =?us-ascii?q?yaFRYEqAgYKAQEDCYxtAQE?= Received: from samail03.wamas.com (HELO mailhost.salomon.at) ([172.28.33.235]) by atfriesa01.ssi-schaefer.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Jan 2021 07:58:01 +0100 Received: from friw0843.wamas.com ([172.28.53.109]) by mailhost.salomon.at with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.77) (envelope-from ) id 1l1kxk-0005Nf-VF for gentoo-alt@lists.gentoo.org; Tue, 19 Jan 2021 07:58:01 +0100 Message-ID: <1611039480.3306.10.camel@ssi-schaefer.com> Subject: Re: [gentoo-alt] Future of x64-cygwin, x86-winnt? From: Martin Oberzalek To: gentoo-alt@lists.gentoo.org Date: Tue, 19 Jan 2021 07:58:00 +0100 In-Reply-To: References: <1610946285.5859.16.camel@ssi-schaefer.com> Content-Type: multipart/alternative; boundary="=-dyuHrrOEAzkRGF4EOtob" X-Mailer: Evolution 3.26.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-alt@lists.gentoo.org Reply-to: gentoo-alt@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply Mime-Version: 1.0 X-Archives-Salt: 6633ccdf-48c7-4f3d-9efb-9262cc5b4e6c X-Archives-Hash: 86dae82ccbb6ffb89ad2aa1618274ea6 --=-dyuHrrOEAzkRGF4EOtob Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Hi Fabian, Am Montag, den 18.01.2021, 09:48 +0100 schrieb Fabian Groffen: > On 18-01-2021 06:04:45 +0100, Martin Oberzalek wrote: > > > So, the inevitable question: who needs x64-cygwin/x86-winnt, > Ok, I thought *-winnt targets were native Windows code, apparently WSL > is too? (I'm just learning here, I guess.) You are right, *-winnt is windows native and might be important when compiling on WSL via a compiler wrapper like parity/or other helper tool with eg: visual studio > > But now we are using actual cygwin versions and our fork of gentoo. Currently this is only working > > with the developer release of the cygwin.dll. What I can do is: testing the gentoo prefix stack with > > this upcomming new cygwin release (when its released) and give some feedback. If I can get it working I would update > > > > https://wiki.gentoo.org/wiki/Prefix/Cygwin > > I'm trying to understand what this means. I'm sure/certain the current > tree doesn't work for Cygwin. This means I anticipate you'll have to > patch/fix a lot of packages for it. Would it be more useful to use an > overlay for Cygwin instead? I agree, maybe this would be a good solution. Greetings, Martin --=-dyuHrrOEAzkRGF4EOtob Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit 
Hi Fabian,

Am Montag, den 18.01.2021, 09:48 +0100 schrieb Fabian Groffen:



On 18-01-2021 06:04:45 +0100, Martin Oberzalek wrote:





So, the inevitable question: who needs x64-cygwin/x86-winnt, 









Ok, I thought *-winnt targets were native Windows code, apparently WSL
is too?  (I'm just learning here, I guess.)



You are right, *-winnt is windows native and might be important when
compiling on WSL via a compiler wrapper like parity/or other helper tool with eg: visual studio  





But now we are using actual cygwin versions and our fork of gentoo. Currently this is only working
with the developer release of the cygwin.dll. What I can do is: testing the gentoo prefix stack with 
this upcomming new cygwin release (when its released) and give some feedback. If I can get it working I would update

https://wiki.gentoo.org/wiki/Prefix/Cygwin



I'm trying to understand what this means.  I'm sure/certain the current
tree doesn't work for Cygwin.  This means I anticipate you'll have to
patch/fix a lot of packages for it.  Would it be more useful to use an
overlay for Cygwin instead?



I agree, maybe this would be a good solution.

Greetings, Martin

--=-dyuHrrOEAzkRGF4EOtob--