public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Fiodar Stryzhniou <fedor_qd@mail.ru>
To: gcc-help@gcc.gnu.org
Subject: Missed files in gcc-12.1.0 release
Date: Sat, 4 Jun 2022 15:09:03 +0300	[thread overview]
Message-ID: <e406dc1a-6f49-0e8d-2c12-0f772245ede8@mail.ru> (raw)

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 sources signature is correct:
sha512sum -c sha512.sum
gcc-12.1.0.tar.gz: OK
gcc-12.1.0.tar.gz.sig: OK
gcc-12.1.0.tar.xz: OK

gcc-11.2.0 has these files. Older versions too.
-- 
Fiodar Stryzhniou

             reply	other threads:[~2022-06-04 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04 12:09 Fiodar Stryzhniou [this message]
2022-06-04 20:56 ` Matthew R. Wilson
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=e406dc1a-6f49-0e8d-2c12-0f772245ede8@mail.ru \
    --to=fedor_qd@mail.ru \
    --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).