From: <nuncio.bitis@outlook.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Successful build of gcc 12.1 on Linux
Date: Mon, 16 May 2022 18:04:47 +0000 [thread overview]
Message-ID: <MN2PR06MB58876F0C75F2A57BE8F04A4D80CF9@MN2PR06MB5887.namprd06.prod.outlook.com> (raw)
* Output from running srcdir/config.guess. Do not send that file itself, just the one-line output from running it.
* x86_64-pc-linux-gnu
* The output of ‘gcc -v’ for your newly installed gcc. This tells us which version of GCC you built and the options you passed to configure.
* Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20220516 (experimental) (GCC)
* Whether you enabled all languages or a subset of them. If you used a full distribution then this information is part of the configure options in the output of ‘gcc -v’, but if you downloaded the “core” compiler plus additional front ends then it isn’t apparent which ones you built unless you tell us about it.
* No special configurations or settings were used
* If the build was for GNU/Linux, also include:
* The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); this information should be available from /etc/issue.
* Linux Mint 20.3 Una \n \l
* The version of the Linux kernel, available from ‘uname --version’ or ‘uname -a’.
* Linux Jupiter 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
* The version of glibc you used; for RPM-based systems like Red Hat, Mandrake, and SuSE type ‘rpm -q glibc’ to get the glibc version, and on systems like Debian and Progeny use ‘dpkg -l libc6’.
* Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-===============-============-=================================
ii libc6:amd64 2.31-0ubuntu9.9 amd64 GNU C Library: Shared libraries
ii libc6:i386 2.31-0ubuntu9.9 i386 GNU C Library: Shared libraries
--------------------------------------------------------
Jim Parziale
Reading, MA 01867
--------------------------------------------------------
Some people, when confronted with a problem, think "I know, I'll use regular expressions."
Now they have two problems.
reply other threads:[~2022-05-16 18:04 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=MN2PR06MB58876F0C75F2A57BE8F04A4D80CF9@MN2PR06MB5887.namprd06.prod.outlook.com \
--to=nuncio.bitis@outlook.com \
--cc=gcc@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).