From: "Matthew R. Wilson" <mwilson@mattwilson.org>
To: gcc-help@gcc.gnu.org
Subject: Re: Missed files in gcc-12.1.0 release
Date: Sat, 4 Jun 2022 13:56:52 -0700 [thread overview]
Message-ID: <20220604205652.77k6ymskpnoemvro@mattwilson.org> (raw)
In-Reply-To: <e406dc1a-6f49-0e8d-2c12-0f772245ede8@mail.ru>
On 06.04.2022 15:09, Fiodar Stryzhniou wrote:
>I encounter error while building gcc-12.1.0. There two file missed
>probably in path gcc-12.1.0/gcc: version.c and version.h.
>
>There maybe more missed files. I don't know how check.
>
>gcc-11.2.0 has these files. Older versions too.
What steps are you using to build gcc, and what error, specifically, are
you getting?
The gcc/version.c and gcc/version.h files aren't missing from the source
distribution, they were intentionally removed:
<https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=e3a682f4197f9f39808febfd1862e722d7675d34>
-Matthew
next prev parent reply other threads:[~2022-06-04 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 12:09 Fiodar Stryzhniou
2022-06-04 20:56 ` Matthew R. Wilson [this message]
2022-06-05 8:50 ` Re[2]: " fedor_qd
2022-06-06 12:48 ` Jonathan Wakely
2022-06-06 17:04 ` Re[2]: " Fiodar
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=20220604205652.77k6ymskpnoemvro@mattwilson.org \
--to=mwilson@mattwilson.org \
--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).