mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Tom Scogland <scogland1@llnl.gov>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: musl@lists.openwall.com, Farid Zakaria <fmzakari@ucsc.edu>,
	Carlos Maltzahn <carlosm@ucsc.edu>
Subject: Re: [musl] Dynamic linking of NEEDED with absolute path differs than that of glibc
Date: Thu, 23 Dec 2021 12:41:48 -0800	[thread overview]
Message-ID: <9DC8B595-1155-4314-9E8D-8009FCBE32B8@llnl.gov> (raw)
In-Reply-To: <e6deb71e-a8ad-0d62-1af0-bc562fd2d3ff@linaro.org>

Certainly, we have no intention of mixing different versions of loader and libc or different libc types.  In fact it’s mainly about making sure we avoid getting incorrectly mixed versions of other libraries due to loading issues.

On 23 Dec 2021, at 3:46, Adhemerval Zanella wrote:

> On 21/12/2021 15:56, Farid Zakaria wrote:
>> ```
>>
>> glibc seems to happily link this and the executable runs.
>> ```
>> ldd ./tests/scratch/replace-add-needed/simple
>> linux-vdso.so.1 (0x00007ffc98d98000)
>> /some-fixed-path/libbar.so (0x00007f269b6d3000)
>> /some-fixed-path/llibfoo.so (0x00007f269b6ce000)
>> /lib/x86_64-linux-gnu/libc.so.6 (0x00007f269b509000)
>> /lib64/ld-linux-x86-64.so.2 (0x00007f269c6e3000)
>> ```
>>
>
> Not sure if this is what you are doing here, but keep in mind that
> mixing glibc dynamic loader and libc with different versions is not
> supported and can break any time.

      reply	other threads:[~2021-12-23 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 18:56 Farid Zakaria
2021-12-22  5:46 ` Markus Wichmann
2021-12-22 13:58   ` Farid Zakaria
2021-12-23 11:46 ` Adhemerval Zanella
2021-12-23 20:41   ` Tom Scogland [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=9DC8B595-1155-4314-9E8D-8009FCBE32B8@llnl.gov \
    --to=scogland1@llnl.gov \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlosm@ucsc.edu \
    --cc=fmzakari@ucsc.edu \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).