X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 88DE33858C62
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1673994402;
	bh=AYwEfRKVShLNd9ML5kk1QF0zNJo2GS5kC3qmQKrmydE=;
	h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:From;
	b=ZGFuo0le1J9/dnfX8CQVUFbKmoWkLsvjaDVKLGw1+cTjrWALWFxLhYO6f5UmDxSOE
	AacNwHj1RdR6A4tCGwOzovwl6fhjXHSbT5coe0YFZVrtxX/jxYCTVYN6hAqeDAmgiY
	EkNzZVBV8d6uVSLZQO79uhFj91wy8gpTjsnCPuac=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 7DC8B3858D28
MIME-Version:	1.0
Date:	Tue, 17 Jan 2023 16:25:55 -0600
To:	cygwin AT cygwin DOT com
Subject:	Does i686-w64-mingw32-gcc now use -mno-cygwin by default?
User-Agent:	Roundcube Webmail/1.5.2
Message-ID:	<507e7dfc987741cc10f1b21540fc02a4@crcomp.net>
X-Sender:	mail AT crcomp DOT net
Organization:	CRC
X-AntiAbuse:	This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse:	Primary Hostname - www18.qth.com
X-AntiAbuse:	Original Domain - cygwin.com
X-AntiAbuse:	Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse:	Sender Address Domain - crcomp.net
X-Get-Message-Sender-Via:	www18.qth.com: authenticated_id: mail AT crcomp DOT net
X-Authenticated-Sender:	www18.qth.com: mail AT crcomp DOT net
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Status:	No, score=4.5 required=5.0 tests=BAYES_50, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_DNSWL_LOW,
	SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Level:	****
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Don Kuenz via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Don Kuenz <mail AT crcomp DOT net>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Greetings,

Back in the day i686-pc-mingw32-gcc used the -mno-cygwin flag to break
the implicit link to cygwin1.dll. It enabled developers to release a
standalone binary. In other words, cygwin1.dll did not have to be
installed on the user's PC in order for a standalone binary to run.

i686-pc-mingw32-gcc is no longer available. And i686-w64-mingw32-gcc now
seems to create standalone binaries by default. The binaries run on a
target PC without cygwin1.dll installed.

Can someone confirm i686-w64-mingw32-gcc in its default mode now creates
standalone binaries?

Thank you in advance.

Danke,

-- 
Don, KB7RPU, https://www.qsl.net/kb7rpu
There was a young lady named Bright Whose speed was far faster than 
light;
She set out one day In a relative way And returned on the previous 
night.

-- 
Don Kuenz
307 266 3327 x1

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -