From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 77E743858C56; Fri, 12 Apr 2024 15:22:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 77E743858C56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712935345; bh=6k2TUUxOK+FDgN6gsMV2b9UTrQL5GOubPLW6zogCm6A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=J6+1Fsl6omYFsRv6xKPGfgfypOnxph5D7d756wAZssDm97L4sRqhpe5m1ITlW3s1O i+6Wg5o2++09tEmou9Ov1BX3bwIwDF0ghHoQJUWfsFNWbRohwOJhRxqXOaunkOVhuZ kEOE85eW198L6nO/mdJmnJIWvFBY1rKq24bn4DQM= From: "cohenarthur 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: Fri, 12 Apr 2024 15:22:23 +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: cohenarthur 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 #6 from Arthur Cohen --- (In reply to Richard Biener from comment #5) > (In reply to Thomas Schwinge from comment #4) > > If I understood Arthur correctly, GCC/Rust is going to effectively requ= ire > > 'dlopen' (and therefore '--enable-plugin'?), so that means, if the latt= er's > > not available we have to auto-disable Rust language front end if enabled > > '--enable-languages=3Dall' vs. raise a 'configure'-time error if enable= d via > > explicit '--enable-languages=3Drust'? >=20 > 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? >=20 > Being able to dlopen() is something different. No, it does not require this and is rather self contained. Macro expansion needs to be able to dlopen() compiled Rust libraries, which contain a speci= fic type of function our frontend calls as a macro. So we always need to dlopen= (). Is there anything similar in other frontends? If so, how does it work on su= ch platforms which do not support dlopen()? --=20 You are receiving this mail because: You are on the CC list for the bug.=