public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: "xry111 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: Fri, 12 Apr 2024 18:07:44 +0000	[thread overview]
Message-ID: <bug-113499-35322-EpGUUONBGZ@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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #7 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> (In reply to Richard Biener from comment #2)
> > Re-confirmed.  Can be reproduced both on a glibc 2.31 and glibc 2.38 system
> > with
> 
> It does work with glibc 2.38, so only glibc 2.31 fails this (and possibly
> other OS).

In Glibc 2.34 libdl was merged into libc, thus it only fails with Glibc < 2.34.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-12 18:07 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
2024-04-12 15:22 ` cohenarthur at gcc dot gnu.org
2024-04-12 18:07 ` xry111 at gcc dot gnu.org [this message]
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-EpGUUONBGZ@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).