public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/109898] 'make install -j' sometimes corrupts 'dir' file for .info files due to parallel 'install-info' calls Date: Fri, 19 May 2023 09:29:21 +0000 [thread overview] Message-ID: <bug-109898-4-99OxAjaX60@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109898-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109898 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- That seems to be new in Make 4.4, because the manual for Make 4.3 says: '.NOTPARALLEL' If '.NOTPARALLEL' is mentioned as a target, then this invocation of 'make' will be run serially, even if the '-j' option is given. Any recursively invoked 'make' command will still run recipes in parallel (unless its makefile also contains this target). Any prerequisites on this target are ignored.
next prev parent reply other threads:[~2023-05-19 9:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-17 20:40 [Bug other/109898] New: " slyfox at gcc dot gnu.org 2023-05-18 6:23 ` [Bug other/109898] " rguenth at gcc dot gnu.org 2023-05-18 8:36 ` redi at gcc dot gnu.org 2023-05-18 19:35 ` slyfox at gcc dot gnu.org 2023-05-19 9:29 ` redi at gcc dot gnu.org [this message] 2023-05-19 9:52 ` jakub at gcc dot gnu.org
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-109898-4-99OxAjaX60@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: linkBe 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).