public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Joachim Wuttke <j.wuttke@fz-juelich.de>, bug-binutils@gnu.org
Cc: linux-man@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: elf(5) and ld.so(8): DT_RPATH deprecated - really?
Date: Mon, 22 Apr 2024 06:35:18 +0200	[thread overview]
Message-ID: <ZiXpBp-vigNCwpHx@debian> (raw)
In-Reply-To: <643ad7be-1cf5-491d-bd0c-d87e2b260912@fz-juelich.de>

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

Hi Joachim,

On Fri, Apr 19, 2024 at 08:43:33AM +0200, Joachim Wuttke wrote:
> Pages elf(5) and ld.so(8) say that DT_RPATH is deprecated.

The blames are:

commit 28d979c8c7fbdca65e221eca4e21823735f5db8d
Author: Michael Kerrisk <mtk.manpages@gmail.com>
Date:   Fri Jul 15 12:06:06 2005 +0000

    Mike Frysinger <vapier@gentoo.org>
    tweaked the short description to include definition of 'ELF'
    add ELFOSABI_NONE to the ELFOSABI_ list
    tweak/add more machines to EM_ list for ehdr->e_machine
    fix indenting to be consistent
    tweak the display of the ELF_ST_* macros
    document the Elf_Dyn structure

and

commit 121edebe2e0b36c3cfc306fbf88bfb6d17993b63
Author: Krónos <Krónos@Sāturnus>
Date:   Sun Dec 23 23:36:00 2001 +0100

    man-pages 1.46
    
    Link: <https://www.win.tue.nl/~aeb/ftpdocs/linux-local/manpages.archive/>
    Signed-off-by: Alejandro Colomar <alx@kernel.org>


I also found a few pages talking about it being deprecated:

<https://stackoverflow.com/questions/67131565/how-do-i-set-dt-rpath-or-dt-runpath>
<https://stackoverflow.com/questions/7967848/use-rpath-but-not-runpath>

> This is inconsistent with ld(1), which does not warn that
> --disable-new-dtags is deprecated.

I've added bug-binutils@ to the thread, in case they want to update
their manual to add a deprecation notice.

> And it is not credible. A huge amount of software would
> break down if support for DT_RPATH were ever removed.

Nobody said it would be removed soon.  But it seems people want to
remove it "eventually", with that eventually possibly being in a couple
of centuries, if computers still exist.

But if you have the intention of using it in new software, or keeping it
in existing software, maybe you could give your reasons to those who
deprecated it, so that either you convince them of its usefulness, or
they convince you of not using it.

Have a locely day!
Alex

> Regards, Joachim

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-22  4:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  6:43 elf(5) and ld.so(8): DT_RPATH deprecated - really? Joachim Wuttke
2024-04-22  4:35 ` Alejandro Colomar [this message]
2024-04-22 16:22   ` Joseph Myers
2024-04-22 17:58     ` Alejandro Colomar
2024-04-22 21:08       ` Joachim Wuttke
2024-04-23  7:53       ` [patch] elf.5 and ld.so.8: undeprecate DT_RPATH; explain DT_RPATH vs DT_RUNPATH Joachim Wuttke
2024-05-07 13:12         ` Alejandro Colomar

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=ZiXpBp-vigNCwpHx@debian \
    --to=alx@kernel.org \
    --cc=bug-binutils@gnu.org \
    --cc=j.wuttke@fz-juelich.de \
    --cc=linux-man@vger.kernel.org \
    --cc=vapier@gentoo.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