unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 57029@debbugs.gnu.org, 57015@debbugs.gnu.org,
	dario.gjorgjevski@gmail.com, stefankangas@gmail.com,
	naofumi@yasufuku.dev
Subject: bug#57029: macos cannot build emacs after updated gcc and libgccjit to 12.1
Date: Fri, 19 Aug 2022 10:38:21 +0300	[thread overview]
Message-ID: <831qtcfzte.fsf@gnu.org> (raw)
In-Reply-To: <m2fshshf10.fsf_-_@Mini.fritz.box> (message from Gerd Möllmann on Fri, 19 Aug 2022 09:24:27 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Stefan Kangas <stefankangas@gmail.com>,  57029@debbugs.gnu.org,
>   57015@debbugs.gnu.org,  dario.gjorgjevski@gmail.com,
>   naofumi@yasufuku.dev
> Date: Fri, 19 Aug 2022 09:24:27 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > We could, but that won't help our users.
> 
> Any objections to a fix in master?

Not on master, no.  My problem is what to do with the release branch.
If you think the solution based on Ruby is fine and safe, please
install that on the release branch (and it will be soon merged to
master).

Otherwise, which of the other solutions proposed here and in related
discussions do you recommend that is safe enough for the release
branch?

Thanks.





  reply	other threads:[~2022-08-19  7:38 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
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 [this message]
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=831qtcfzte.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57015@debbugs.gnu.org \
    --cc=57029@debbugs.gnu.org \
    --cc=dario.gjorgjevski@gmail.com \
    --cc=gerd.moellmann@gmail.com \
    --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).