unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jacob Faibussowitsch <jacob.fai@gmail.com>
Cc: 57015@debbugs.gnu.org
Subject: bug#57015: 29.0.50; macOS: libgccjit was not found: Homebrew libgccjit 12.1.0
Date: Sat, 06 Aug 2022 18:03:32 +0300	[thread overview]
Message-ID: <83wnblxvln.fsf@gnu.org> (raw)
In-Reply-To: <5F111D5A-02D2-438E-B469-1C602BF8D00E@gmail.com> (message from Jacob Faibussowitsch on Sat, 6 Aug 2022 09:56:27 -0400)

Resending to the list:

> From: Jacob Faibussowitsch <jacob.fai@gmail.com>
> Date: Sat, 6 Aug 2022 09:56:27 -0400
> 
> > E.g., who says that 'readlink' will always be available on macOS?
> 
> 
> It’s not, see here https://stackoverflow.com/questions/7665/how-to-resolve-symbolic-links-in-a-shell-script. Though I suppose it may not be a big deal for emacs to require that coreutils are installed via brew since this libgccjit check is *already* using brew.
> 
> Other alternatives to resolving paths are:
> 
> $ perl -MCwd -e 'print Cwd::abs_path shift’ /path/to/file
> 
> Or
> 
> $ python -c 'import os, sys; print(os.path.realpath(sys.argv[1]))’ /path/to/file
> 
> Both perl and python (in some form) have always come preinstalled on macOS.
> 
> P.S. I couldn’t immediately see how to cc the mailing list, I replied using the “reply via email to” button here https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-08/msg00589.html so please resend this with proper cc if it doesn’t get attached.
> 
> Best regards,
> 
> Jacob Faibussowitsch
> (Jacob Fai - booss - oh - vitch)
> 
> 





       reply	other threads:[~2022-08-06 15:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5F111D5A-02D2-438E-B469-1C602BF8D00E@gmail.com>
2022-08-06 15:03 ` Eli Zaretskii [this message]
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-07  9:57   ` 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-09 15:33 ` 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

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=83wnblxvln.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57015@debbugs.gnu.org \
    --cc=jacob.fai@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).