public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/112836] gcc fails when job control is used
Date: Thu, 01 Feb 2024 21:42:41 +0000	[thread overview]
Message-ID: <bug-112836-4-OPYnhSzYeu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112836-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112836

--- Comment #5 from Bruno Haible <bruno at clisp dot org> ---
(In reply to John Paul Adrian Glaubitz from comment #4)
> I tried this patch but it does not address the issue with posix_spawn that I
> am seeing.
> 
> Trying to build gcc from git on Linux sparc64 with glibc 2.37 with the
> following configuration:
> 
> ./configure --enable-languages=c,c++ --disable-bootstrap --disable-multilib
> --disable-nls --host=sparc64-unknown-linux-gnu
> 
> fails with:
> 
> xgcc: fatal error: cannot execute '/home/glaubitz/gcc/build/./gcc/cc1plus':
> posix_spawn: Bad address
> compilation terminated.
> 
> This can be worked around when building with one parallel job (make -j1).

This appears to be a different bug, because
  - it appears under different conditions (parallel make, not Ctrl-Z / 'fg'),
  - the message is different ("posix_spawn: Bad address", not "failed to get
exit status: Interrupted system call").

Could you please register it as a separate bug under
https://gcc.gnu.org/bugzilla/ ?

      parent reply	other threads:[~2024-02-01 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 19:14 [Bug driver/112836] New: " bruno at clisp dot org
2023-12-03 19:17 ` [Bug driver/112836] " bruno at clisp dot org
2023-12-04  6:52 ` [Bug other/112836] " sjames at gcc dot gnu.org
2023-12-04  8:43 ` rguenth at gcc dot gnu.org
2024-02-01 18:21 ` glaubitz at physik dot fu-berlin.de
2024-02-01 21:42 ` bruno at clisp dot org [this message]

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=bug-112836-4-OPYnhSzYeu@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).