public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cz.finn.cz at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/110710] LTO linker on Windows creates an invalid Makefile Date: Tue, 18 Jul 2023 09:13:27 +0000 [thread overview] Message-ID: <bug-110710-4-HqR0IeL7g6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110710-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110710 --- Comment #5 from Jan Nárovec <cz.finn.cz at gmail dot com> --- We are using GNU/make (which is a superset of POSIX make, I don't know, whether it makes some difference) with SHELL=cmd.exe. If GCC intends to support only POSIX shells, it is OK for us (we will condsider using WSL) and you can close this issue as invalid.
next prev parent reply other threads:[~2023-07-18 9:13 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-18 6:14 [Bug lto/110710] New: " cz.finn.cz at gmail dot com 2023-07-18 6:18 ` [Bug lto/110710] " pinskia at gcc dot gnu.org 2023-07-18 6:22 ` pinskia at gcc dot gnu.org 2023-07-18 6:34 ` cz.finn.cz at gmail dot com 2023-07-18 6:39 ` pinskia at gcc dot gnu.org 2023-07-18 9:13 ` cz.finn.cz at gmail dot com [this message] 2024-02-13 2:16 ` amy at amyspark dot me 2024-03-14 16:13 ` peter0x44 at disroot dot org 2024-03-14 16:15 ` peter0x44 at disroot dot org 2024-03-14 16:15 ` peter0x44 at disroot dot org 2024-03-14 16:25 ` peter0x44 at disroot dot org 2024-03-15 14:49 ` peter0x44 at disroot dot org 2024-03-26 20:37 ` peter0x44 at disroot dot org 2024-03-26 22:45 ` peter0x44 at disroot dot org 2024-03-29 11:11 ` egallager at gcc dot gnu.org 2024-05-02 10:42 ` cvs-commit at gcc dot gnu.org 2024-05-02 10:43 ` cvs-commit at gcc dot gnu.org 2024-05-02 10:43 ` rguenth 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-110710-4-HqR0IeL7g6@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).