public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28132] ABI/VERSION name of the rtld module is different from the module name
Date: Thu, 06 Oct 2022 16:38:07 +0000	[thread overview]
Message-ID: <bug-28132-131-M9u4xGdmmF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28132-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28132

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to H.J. Lu from comment #0)
> Name of ABI/VERSION of the rtld module is ld, which is different from the
> module name.

We use IS_IN(rtld) because the module name is rtld.
We use ld as the ABI/VERSION.

As far as I understand you want the two to match just to make it simpler to
understand.

You posted a patch for this here:
https://patchwork.sourceware.org/project/glibc/patch/20210802042940.932692-1-hjl.tools@gmail.com/

I've commented on why I think this needs generalizing.

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

      reply	other threads:[~2022-10-06 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 22:26 [Bug dynamic-link/28132] New: " hjl.tools at gmail dot com
2022-10-06 16:38 ` carlos at redhat dot com [this message]

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-28132-131-M9u4xGdmmF@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).