Jim Myhrberg

@CsBigDataHub That error is weird. It seems like a invalid argument was passed to the `dirname` command. I'm not super familiar with the exact code in the configure script used...

@CsBigDataHub That script should be irrelevant to your issue. It is added to the built Emacs.app after the normal build process has completed, while in your case you're not even...

@CsBigDataHub I think your issue might have been temporary and caused by libgccjit renaming `libgccjit.so` to `libgccjit.dylib` in version 11.3.0. From what I can gather, Emacs' configure script would have...

@DJManas thats not a bad idea. I'll try and have the build script do that automatically when I have some free time :)

Apologies, I haven't gotten around to properly documenting it. It's a bit involved, but below are some very brief instructions that hopefully will help. First, you'll need a paid for...

Right, yeah. It seems M1 machines refuse to run unsigned code altogether. On Intel-based Macs it seems to be aware of what binaries were built locally, so they're automatically trusted....

Apologies for not getting back to you sooner. Have you had any luck solving this? I'm afraid I've not seen this issue before, and I haven't been able to think...

Hmm, it seems the configure script runs this to determine if gnutls is available: ``` pkg-config --exists --print-errors 'gnutls >= 2.12.2' ``` On success it'll return a exit code of...

@smithwinston is still is an issue for you? Did you manage to get it working?

It looks like harfbuzz and cairo support for macOS is rather recent. Last I looked into it about a year ago it was not possible. However emacs-plus supports it as...