X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 6C1843891C11
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1641843517;
	bh=BMnIHhr8qaZ6Cxve2zX8qK2hpMAlNpY6fk+Ymrl/gDU=;
	h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:From;
	b=rLnnHFdmMEpxWrmAdkGC/4HGBozFL2yNoCuGKillkfkcCIdkkhfO5ZfVvVkEU6qWm
	e9GNJC3gbesUqtJg0p9cJFfzS5I9grUz/i6oypG3Z7M3QZCkzLWKpyRf188HtxfAef
	F7kTDuCbjk+eeCtL/ZGds3KxwLXWS9K4+1808p5Y=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 0504A386EC49
Date:	Mon, 10 Jan 2022 11:38:03 -0800 (PST)
X-X-Sender:	jeremyd AT resin DOT csoft DOT net
To:	cygwin AT cygwin DOT com
Subject:	posix_spawn issues on i686
Message-ID:	<alpine.BSO.2.21.2201101132030.11760@resin.csoft.net>
User-Agent:	Alpine 2.21 (BSO 202 2017-01-01)
MIME-Version:	1.0
X-Spam-Status:	No, score=-4.3 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, SPF_HELO_PASS,
	SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) 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:	Jeremy Drake via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Jeremy Drake <cygwin AT jdrake DOT com>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

From https://github.com/msys2/MSYS2-packages/issues/2801

MSYS2 recently rebuilt GNU make 4.3, and I found that after rebuilding, it
broke rather horribly on i686, where any attempt to run a command resulted
in "Invalid argument" errors.  Some debugging revealed that rebuilding
make resulted in it using posix_spawn now instead of vfork.  Passing
--disable-posix-spawn to make's configure script results in a working i686
make.

From the MSYS2 bug report:

"""
For reference, I tried to rebuild "make" in cygwin 32 bit and it has the
same problem:

rebuilding cygport make.cygport all results in a broken make
Adding CYGCONF_ARGS="--disable-posix-spawn" to the cygport file and
rebuilding again results in a good make
A Makefile to reproduce the issue:

all:
	echo hi
"""

In addition, make check fails rather horribly as well.

I know that 32-bit is on the way out, but it is concerning to me that
there is some latent bug lurking in this code path that is apparently not
well exercised.

-- 
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 -