all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
To: Naofumi Yasufuku <naofumi@yasufuku.dev>
Cc: 57015@debbugs.gnu.org
Subject: bug#57015: 29.0.50; macOS: libgccjit was not found: Homebrew libgccjit 12.1.0
Date: Tue, 09 Aug 2022 17:33:31 +0200	[thread overview]
Message-ID: <lyfsi5h1o4.fsf@88665a138777.ant.amazon.com> (raw)
In-Reply-To: <m1r11ty52l.fsf@yasufuku.dev> (Naofumi Yasufuku's message of "Sat, 06 Aug 2022 20:38:58 +0900")

Naofumi Yasufuku <naofumi@yasufuku.dev> writes:

> './configure --with-native-compilation' fails if Homebrew libgccjit is
> updated to 12.1.0.  Attached configure.ac patch fixes this issue.
> I think the same patch should be applied to emacs-28 branch.

As an alternative to your patch and the general approach based on
running `grep` over the output of `brew ls`, one can also use

    % brew ruby -e 'puts "#{:libgccjit.f.lib}/gcc/#{:gcc.f.any_installed_version.major}"'
    /usr/local/opt/libgccjit/lib/gcc/12

for MAC_LIBS, and

    % brew ruby -e 'puts :libgccjit.f.include'
    /usr/local/opt/libgccjit/include

for MAC_CFLAGS.  This will work with both versions 11 and 12 of
Homebrew's `libgccjit`.

Best regards,
Dario





  parent reply	other threads:[~2022-08-09 15:33 UTC|newest]

Thread overview: 39+ 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 ` Dario Gjorgjevski [this message]
2022-08-10 14:42   ` bug#57015: 29.0.50; macOS: libgccjit was not found: Homebrew libgccjit 12.1.0 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
     [not found] <5F111D5A-02D2-438E-B469-1C602BF8D00E@gmail.com>
2022-08-06 15:03 ` bug#57015: 29.0.50; macOS: libgccjit was not found: Homebrew libgccjit 12.1.0 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

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

  git send-email \
    --in-reply-to=lyfsi5h1o4.fsf@88665a138777.ant.amazon.com \
    --to=dario.gjorgjevski@gmail.com \
    --cc=57015@debbugs.gnu.org \
    --cc=naofumi@yasufuku.dev \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.