From: Simon Richter <Simon.Richter@hogyros.de>
To: gcc-help@gcc.gnu.org
Subject: gcc 12: language Makefile fragment and generated files
Date: Mon, 16 Oct 2023 16:03:51 +0900 [thread overview]
Message-ID: <d4884e6e-4928-4646-af47-9bf053c0ecda@hogyros.de> (raw)
Hi,
I see build failures of the Debian gcc 12 packages on machines with a
lot of threads[1]. This package adds in Modula-2 support before
building, and the M2 fragment uses $(generated_files) as a dependency
for the language specific options.
Because $(generated_files) is set after including the fragments, that
doesn't really work, so the dependency is missing, and the M2 frontend
is built before insn-attr-common.h is available.
I'm not sure how to address this best.
My initial approach was be to define "M2_OBJS", which I figured would be
the name that the fragment processing would consult for the list of
extra objects built from gcc/m2/Make-lang.in, and set up proper
dependency tracking for these and include them in the order-only
dependency at the end of gcc/Makefile.in. That didn't work, though.
My two immediate questions:
- how is a language supposed to depend on the target header (it's
i386.h that pulls in insn-attr-common.h)?
- did I understand the purpose of the _OBJS processing correctly?
Simon
[1] https://bugs.debian.org/1053551
reply other threads:[~2023-10-16 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d4884e6e-4928-4646-af47-9bf053c0ecda@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=gcc-help@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).