From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: posix_spawn issues on i686
Date: Tue, 11 Jan 2022 11:07:27 +0100 [thread overview]
Message-ID: <Yd1W3753GnkC8398@calimero.vinschen.de> (raw)
In-Reply-To: <alpine.BSO.2.21.2201101132030.11760@resin.csoft.net>
On Jan 10 11:38, Jeremy Drake via Cygwin wrote:
> >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.
Can you create a simple, self-contained testcase in plain C?
Thanks,
Corinna
next prev parent reply other threads:[~2022-01-11 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 19:38 Jeremy Drake
2022-01-11 10:07 ` Corinna Vinschen [this message]
2022-01-11 18:45 ` Jeremy Drake
2022-01-11 21:08 ` Ken Brown
2022-01-12 10:41 ` Corinna Vinschen
2022-01-12 11:24 ` Corinna Vinschen
2022-01-12 16:32 ` Ken Brown
2022-01-12 21:25 ` Jeremy Drake
2022-01-14 9:15 ` Corinna Vinschen
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=Yd1W3753GnkC8398@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).