From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/113499] crab1 fails to link when configuring with --disable-plugin
Date: Mon, 18 Mar 2024 12:33:04 +0000 [thread overview]
Message-ID: <bug-113499-35322-IRLN7C5Rno@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113499-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113499
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #4)
> If I understood Arthur correctly, GCC/Rust is going to effectively require
> 'dlopen' (and therefore '--enable-plugin'?), so that means, if the latter's
> not available we have to auto-disable Rust language front end if enabled
> '--enable-languages=all' vs. raise a 'configure'-time error if enabled via
> explicit '--enable-languages=rust'?
Not sure - --enable-plugin is not about dlopen, it's about exporting all
GCCs internal symbols for use by a dlopened shared module. Is the
macro processing requiring this or is it rather self-contained?
Being able to dlopen() is something different.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-18 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 6:55 [Bug rust/113499] New: " rguenth at gcc dot gnu.org
2024-01-19 7:05 ` [Bug rust/113499] " rguenth at gcc dot gnu.org
2024-01-19 7:08 ` rguenth at gcc dot gnu.org
2024-02-09 13:33 ` rguenth at gcc dot gnu.org
2024-02-09 13:35 ` rguenth at gcc dot gnu.org
2024-03-18 11:20 ` tschwinge at gcc dot gnu.org
2024-03-18 12:33 ` rguenth at gcc dot gnu.org [this message]
2024-04-12 15:22 ` cohenarthur at gcc dot gnu.org
2024-04-12 18:07 ` xry111 at gcc dot gnu.org
2024-04-15 6:21 ` rguenth at gcc dot gnu.org
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=bug-113499-35322-IRLN7C5Rno@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
/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.
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).