public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "saifi.khan at nishan dot io" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105467] Dependency file produced by C++ modules causes Ninja errors
Date: Sat, 23 Dec 2023 04:38:48 +0000 [thread overview]
Message-ID: <bug-105467-4-c9NgM55xL1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105467-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105467
Saifi Khan <saifi.khan at nishan dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |saifi.khan at nishan dot io
--- Comment #3 from Saifi Khan <saifi.khan at nishan dot io> ---
(In reply to jpakkane from comment #2)
> It would be preferable to have the default work out of the box than having
> every end user having to add compiler flags to make things work.
>
> Ninja is the most popular underlying build system for modules, having it
> work by default would make things easier for many people.
as an end user, i'd prefer to explicitly add compiler flag instead of getting
pinja, hazel, teson or some such by default !
next prev parent reply other threads:[~2023-12-23 4:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 15:04 [Bug c++/105467] New: " jpakkane at gmail dot com
2023-10-18 1:32 ` [Bug c++/105467] " bugzilla.gcc at me dot benboeckel.net
2023-10-20 19:55 ` jpakkane at gmail dot com
2023-12-23 4:38 ` saifi.khan at nishan dot io [this message]
2023-12-30 14:18 ` jpakkane at gmail dot com
2023-12-30 15:04 ` pinskia at gcc dot gnu.org
2023-12-30 16:34 ` jpakkane at gmail dot com
2023-12-30 18:11 ` pinskia at gcc dot gnu.org
2023-12-30 19:15 ` bugzilla.gcc at me dot benboeckel.net
2023-12-30 19:16 ` bugzilla.gcc at me dot benboeckel.net
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-105467-4-c9NgM55xL1@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).