From: Eli Zaretskii <eliz@gnu.org>
To: StrawberryTea <look@strawberrytea.xyz>
Cc: 69689@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#69689: 30.0.50; cannot native compile with -flto in native-comp-compiler-options
Date: Sun, 10 Mar 2024 19:47:52 +0200 [thread overview]
Message-ID: <86ttleugfr.fsf@gnu.org> (raw)
In-Reply-To: <87v85ugfh2.fsf@strawberrytea.xyz> (message from StrawberryTea on Sun, 10 Mar 2024 12:32:25 -0500)
> From: StrawberryTea <look@strawberrytea.xyz>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, 69689@debbugs.gnu.org
> Date: Sun, 10 Mar 2024 12:32:25 -0500
>
> Well, I wanted to ask here because I wanted to check if anyone else is
> able to compile elisp files with -flto in native-comp-compiler-options.
> I believe that the error is related to the native-comp branch, as a
> Gentoo developer from the libgccjit mailing list has already confirmed
> that libgccjit is compiled with lto support. The matter at hand is not
> about Emacs's inherent support for -flto, but rather if the native-comp
> branch can compile Elisp using the -flto option.
I don't see how this is a question for us, given the error messages
that you cite in your OP. It clearly says that something is missing
in your GCC/Binutils installation, and therefore libgccjit fails to
run the GCC driver. How can that be a problem with Emacs?
next prev parent reply other threads:[~2024-03-10 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 3:19 bug#69689: 30.0.50; cannot native compile with -flto in native-comp-compiler-options StrawberryTea
2024-03-10 6:24 ` Eli Zaretskii
2024-03-10 17:32 ` StrawberryTea
2024-03-10 17:47 ` Eli Zaretskii [this message]
2024-03-10 21:08 ` Paul Eggert
2024-03-11 13:38 ` Eli Zaretskii
2024-03-12 1:03 ` Paul Eggert
2024-03-15 17:02 ` Andrea Corallo
2024-03-17 18:17 ` StrawberryTea
2024-03-17 22:09 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87zfuwy0gq.fsf@>
2024-03-17 22:12 ` StrawberryTea
2024-04-02 8:56 ` Andrea Corallo
2024-03-12 4:23 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86ttleugfr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69689@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=look@strawberrytea.xyz \
/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).