public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugzilla.gcc at me dot benboeckel.net" <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, 30 Dec 2023 19:16:33 +0000 [thread overview]
Message-ID: <bug-105467-4-uaq6K54Ao0@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
--- Comment #9 from Ben Boeckel <bugzilla.gcc at me dot benboeckel.net> ---
> unless autoconf/automake started relying on the non-GNU `fdep` [1] project.
Gah, editing gone awry. This was about Fortran module support in
autoconf/autotools, not C++ module support (they have similar build graph
strategies required).
prev parent reply other threads:[~2023-12-30 19:16 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
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 [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-105467-4-uaq6K54Ao0@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).