public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bug-reports.delphin at laposte dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/105819] New: GCC 12.1.0 Make failed - Compiled with GCC 4.9.4 and under Mac OS X lion - I
Date: Thu, 02 Jun 2022 08:56:20 +0000	[thread overview]
Message-ID: <bug-105819-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105819

            Bug ID: 105819
           Summary: GCC 12.1.0 Make failed - Compiled with GCC 4.9.4 and
                    under Mac OS X lion - I
           Product: gcc
           Version: 12.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bug-reports.delphin at laposte dot net
  Target Milestone: ---

Created attachment 53070
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53070&action=edit
config.log

Summary : although GCC 11.3.0 was built successfully, GCC 12.1.0 failed in
Make.
So, this is a possible regression, although investigation should be made by GCC
developers. Only compilation by GCC 4.9.4 (built with my Mac computer), not
tested by further GCC compilers such as GCC 65x or by LLVM/Clang.
So, not built nor installed..

OS Mac OS X Lion (10.7.5).
Compiler used : GCC 4.9.4 (built with your source code).
Microprocessor : Intel Core 2 Duo (x86_64).

Binutils : provided by Apple.

Kind regards,

Enclosed : 3 files : 1/ config.log, 2/ my-configure.log (displaying what
configure does), 3/ my-make .log.

             reply	other threads:[~2022-06-02  8:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  8:56 bug-reports.delphin at laposte dot net [this message]
2022-06-02  8:57 ` [Bug other/105819] " bug-reports.delphin at laposte dot net
2022-06-02  8:58 ` bug-reports.delphin at laposte dot net
2022-06-02  9:27 ` jakub at gcc dot gnu.org
2022-06-02  9:41 ` jakub at gcc dot gnu.org
2022-06-09  8:47 ` bug-reports.delphin at laposte dot net
2022-06-09  9:11 ` redi at gcc dot gnu.org
2022-06-09  9:15 ` pinskia at gcc dot gnu.org
2022-06-09  9:18 ` jakub at gcc dot gnu.org
2022-06-09  9:20 ` jakub at gcc dot gnu.org
2022-06-14  8:38 ` bug-reports.delphin at laposte dot net
2022-09-16 15:43 ` bug-reports.delphin at laposte dot net
2022-09-16 16:31 ` redi at gcc dot gnu.org
2022-09-16 16:33 ` redi at gcc dot gnu.org
2022-09-17 10:51 ` bug-reports.delphin at laposte dot net
2023-05-03 20:22 ` redi at gcc dot gnu.org
2023-05-03 20:31 ` [Bug other/105819] comma `,` in directory name causes build to fail redi at gcc dot gnu.org
2023-05-15 16:35 ` bug-reports.delphin at laposte dot net

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-105819-4@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).