From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D96483858C98; Mon, 18 Mar 2024 12:33:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D96483858C98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710765184; bh=qruhvtbwZi8rXmkvUSTAq1f27/XIcl1igXwt1iMiwoo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=h8NnyLb81ta4f8PQ+4QhYl+J0oX8ovhth1Wr+o+9n7iA1blbGdS8BPzj3bsS71eik QC9S2uFOasi0TcTTC+tCCy+pp4WOeqvni+ayLadt5xOpPpHJMSJ9IUt+D/SoCvb/Dw iAc1DTTqq6vKelmW2u+NRKPrnZiBtQ0Pl/LpOv6Y= From: "rguenth at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rust X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113499 --- Comment #5 from Richard Biener --- (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=3Dall' vs. raise a 'configure'-time error if enabled = via > explicit '--enable-languages=3Drust'? 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=