unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 57029@debbugs.gnu.org, 57015@debbugs.gnu.org,
	Eli Zaretskii <eliz@gnu.org>,
	Naofumi Yasufuku <naofumi@yasufuku.dev>
Subject: bug#57029: macos cannot build emacs after updated gcc and libgccjit to 12.1
Date: Sun, 07 Aug 2022 14:58:14 +0200	[thread overview]
Message-ID: <87zggg1a8p.fsf_-_@gnus.org> (raw)
In-Reply-To: <CADwFkmkrkexaYa20LScf2G9Ff+FXFQ3=wWaQoe8fbgoxrDKOTA@mail.gmail.com> (Stefan Kangas's message of "Sun, 7 Aug 2022 04:57:57 -0500")

Stefan Kangas <stefankangas@gmail.com> writes:

>> Is it really a problem to use only libgccjit 12.0 and older for the
>> release branch?
>
> I'm afraid that it's a serious problem.

Yes, I think we have to put a fix for this on the release branch, but as
Eli says, it must be safe.  (And this has been a surprisingly difficult
thing to get right -- it seems so simple, but the differences between
brew/Macports/versions of the basic utilities have led to numerous
breakages here.)







  parent reply	other threads:[~2022-08-07 12:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 11:38 bug#57015: 29.0.50; macOS: libgccjit was not found: Homebrew libgccjit 12.1.0 Naofumi Yasufuku
2022-08-06 12:13 ` Eli Zaretskii
2022-08-06 15:13   ` Naofumi Yasufuku
     [not found]     ` <m1les1xrag.fsf@yasufuku.dev>
2022-08-06 16:44       ` Eli Zaretskii
2022-08-06 18:30         ` Naofumi Yasufuku
2022-08-08  6:03         ` bug#57015: bug#57029: macos cannot build emacs after updated gcc and libgccjit to 12.1 Gerd Möllmann
2022-08-08  8:08           ` Andreas Schwab
2022-08-08 12:57             ` Gerd Möllmann
2022-08-07  9:57   ` bug#57015: 29.0.50; macOS: libgccjit was not found: Homebrew libgccjit 12.1.0 Stefan Kangas
2022-08-07 10:24     ` Eli Zaretskii
2022-08-07 10:57       ` Stefan Kangas
2022-08-07 11:32         ` Eli Zaretskii
2022-08-07 12:03           ` Stefan Kangas
2022-08-07 12:55         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 13:14           ` Eli Zaretskii
2022-08-07 13:52             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 14:26             ` Stefan Kangas
2022-08-07 14:32               ` Eli Zaretskii
2022-08-08  6:23               ` bug#57015: bug#57029: macos cannot build emacs after updated gcc and libgccjit to 12.1 Gerd Möllmann
2022-08-07 12:58     ` Lars Ingebrigtsen [this message]
2022-08-09 15:33 ` bug#57015: 29.0.50; macOS: libgccjit was not found: Homebrew libgccjit 12.1.0 Dario Gjorgjevski
2022-08-10 14:42   ` Naofumi Yasufuku
2022-08-10 15:52     ` Eli Zaretskii
2022-08-10 16:14       ` Stefan Kangas
2022-08-11 16:20         ` Eli Zaretskii
2022-08-16 13:28           ` Dario Gjorgjevski
2022-08-16 13:44             ` Eli Zaretskii
2022-08-16 13:58               ` Dario Gjorgjevski
2022-08-16 14:08                 ` Eli Zaretskii
2022-08-16 14:17                   ` Dario Gjorgjevski
2022-08-16 14:32                 ` Stefan Kangas
2022-08-16 15:08                   ` Dario Gjorgjevski
2022-08-16 15:48                     ` Stefan Kangas
2022-08-16 15:52                   ` Eli Zaretskii
2022-08-19  7:24                     ` bug#57015: bug#57029: macos cannot build emacs after updated gcc and libgccjit to 12.1 Gerd Möllmann
2022-08-19  7:38                       ` Eli Zaretskii
2022-08-19  9:05                         ` Gerd Möllmann
2022-09-05 18:43                           ` Lars Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2022-08-07  3:29 ccqpein via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07  6:50 ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zggg1a8p.fsf_-_@gnus.org \
    --to=larsi@gnus.org \
    --cc=57015@debbugs.gnu.org \
    --cc=57029@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=naofumi@yasufuku.dev \
    --cc=stefankangas@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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