From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Davide Restivo <davide.restivo@yahoo.it>,
45934@debbugs.gnu.org, xgutter@yahoo.it,
Andrea Corallo <akrl@sdf.org>
Subject: bug#45934: native-comp - Dylib ID of ELN files not optimal
Date: Thu, 5 Aug 2021 20:00:19 +0100 [thread overview]
Message-ID: <YQw1Qw58de4nZPaT@idiocy.org> (raw)
In-Reply-To: <87im0ki2lq.fsf@gnus.org>
On Thu, Aug 05, 2021 at 12:54:09PM +0200, Lars Ingebrigtsen wrote:
> Alan Third <alan@idiocy.org> writes:
>
> > I'm not sure about with MacPorts, but with Homebrew it should just be
> > a case of installing libgccjit and configuring as normal.
>
> With Macports, Configuring as normal just gets me clang (masquerading as
> /usr/bin/cc), but I can say "CC=/that/macports/gcc ./configure", but it
> doesn't find the libgccjit stuff.
You don't need to build with gcc to use libgccjit, and in fact you
can't build the GUI with gcc at all.
I finally found the code that works it out for Homebrew. I've never
used MacPorts but I think all you need to do is something similar to
(from configure.ac:3820):
CFLAGS="$CFLAGS -I${BREW_LIBGCCJIT_PREFIX}/include"
LDFLAGS="$LDFLAGS -L${brew_libdir} -I${BREW_LIBGCCJIT_PREFIX}/include"
Where "${BREW_LIBGCCJIT_PREFIX}/include" is where the include files
are and ${brew_libdir} is where the .so files are.
This is relatively easy to automate with Homebrew because we can just
ask it where libgccjit is installed and then work out the paths, but
I don't know about Macports.
> > If it's an Arm mac then I think it requires gcc 11.
> >
> > I don't know why the Mac community tends towards maintaining huge
> > scripts and/or lists of configure flags for building Emacs, because in
> > my experience they're not required, but it does seem to be the norm.
>
> Yeah, building on Macos is almost as trivial as on Debian (at least with
> clang), but there's all these really convoluted scripts out there...
>
> My hope was that it was as simple to build with the Macports gcc, too,
> but... apparently not? (I'd rather not install Homebrew, too, on this
> laptop -- that just sounds too confusing.)
I'm sure it must be easy enough. Homebrew is a bit of a pain in the
backside because it intentionally leaves many installed packages
unavailable so as not to interfere with the normal macOS install. I
was under the impression that Macports was a simpler set-up.
--
Alan Third
next prev parent reply other threads:[~2021-08-05 19:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDAEF3DD-6B4E-4ED9-A7B8-8FB4F236DF42.ref@yahoo.it>
2021-01-17 10:13 ` bug#45934: native-comp - Dylib ID of ELN files not optimal davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-17 12:36 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-17 16:48 ` davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-17 20:06 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-23 16:13 ` davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-24 19:37 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-28 21:59 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-29 7:09 ` Eli Zaretskii
2021-01-29 8:52 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-30 8:18 ` davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-11 16:00 ` xgutter--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-30 12:32 ` Lars Ingebrigtsen
2021-08-02 14:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-04 6:55 ` Lars Ingebrigtsen
2021-08-04 18:11 ` Alan Third
2021-08-05 10:54 ` Lars Ingebrigtsen
2021-08-05 19:00 ` Alan Third [this message]
2021-08-06 10:49 ` Lars Ingebrigtsen
2021-08-06 16:37 ` Alan Third
2021-08-07 9:52 ` Lars Ingebrigtsen
2021-08-07 9:57 ` Lars Ingebrigtsen
2021-08-07 10:25 ` Lars Ingebrigtsen
2021-08-07 13:11 ` Alan Third
2021-08-09 12:20 ` Lars Ingebrigtsen
2021-08-22 17:18 ` Davide Restivo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-22 19:40 ` Davide Restivo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-22 21:18 ` Alan Third
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=YQw1Qw58de4nZPaT@idiocy.org \
--to=alan@idiocy.org \
--cc=45934@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=davide.restivo@yahoo.it \
--cc=larsi@gnus.org \
--cc=xgutter@yahoo.it \
/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).