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 regression/106956] New: GCC 12.2.0 & Mac OS X Lion : make failed
Date: Fri, 16 Sep 2022 15:38:44 +0000	[thread overview]
Message-ID: <bug-106956-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106956
           Summary: GCC 12.2.0 & Mac OS X Lion : make failed
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bug-reports.delphin at laposte dot net
  Target Milestone: ---

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

Summary : building GCC v. 12.2.0 under Mac OS X Lion (10.7.x) failed when Make,
although ./configure passed. Hereafter some details about the compilation
(make) process, with enclosed three log (text) files.

OS X : Lion (10.7.x : last version - combo downlaod and installation)
Compiler used : GCC v. 6.5.x (please read teh config.log file), built under OS
X Lion with YOUR code source.

Results :
- configure worked, but make failed ;
- regression compared to the last version of GCC compiled under the same
conditions (namely, 11.3.0) ;
- make error with GCC 12.1.0 : I issued an error for this).

Remark : GCC 12.2.0 (and 12.1.0) should be kindly reviewed why this is a
regression in the compilation process.

For all IT developers and scientists using GCC for their work.
Kind regards !

             reply	other threads:[~2022-09-16 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 15:38 bug-reports.delphin at laposte dot net [this message]
2022-09-16 15:39 ` [Bug regression/106956] " bug-reports.delphin at laposte dot net
2022-09-16 15:40 ` bug-reports.delphin at laposte dot net
2022-09-16 16:31 ` redi at gcc dot gnu.org

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-106956-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).