mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
Cc: musl@lists.openwall.com
Subject: Re: BUG: $ORIGIN does not seem to work
Date: Sat, 27 Jan 2018 20:26:21 +0100	[thread overview]
Message-ID: <20180127192621.GJ4418@port70.net> (raw)
In-Reply-To: <df7394c5-217b-809b-f51b-918093cc037e@petroprogram.com>

* Stefan Fröberg <stefan.froberg@petroprogram.com> [2018-01-27 18:20:27 +0200]:
> Szabolcs Nagy kirjoitti 27.01.2018 klo 13:07:
> > * Stefan Fröberg <stefan.froberg@petroprogram.com> [2018-01-27 01:50:21 +0200]:
> >> My ldd is just symbolic link inside musl chroot environment, to
> >> /lib/ld-musl-x86_64.so.1
> >> and it's symbolic link to /lib/libc.so
> >>
> >> Here is readelf output of that test program
> >> readelf -d x
> >>
> >> Dynamic section at offset 0xe10 contains 24 entries:
> >>   Tag        Type                         Name/Value
> >>  0x0000000000000001 (NEEDED)             Shared library: [libcrypto.so.1.1]
> >                                                             ^^^^^^^^^^^^^^^^
> > this looks like the wrong library version
> >
> > if you had straced the ldd output you would have seen
> > that musl tries to open lib/libcrypto.so.1.1, but you
> > probably only have lib/libcrypto.so.1.0.0 based on the
> > glibc ldd output below.
> No, that ldd was run inside, pure, chrooted musl environment. No glibc
> inside.

this does not matter

> These are the only libcrypto* files inside that chroot environment:
> 
>  ls -lah /usr/lib/libcrypto.*
> -rw-r--r--    1 0        0           5.0M Dec 17 00:24 /usr/lib/libcrypto.a
> lrwxrwxrwx    1 0        0             16 Dec 17 00:24
> /usr/lib/libcrypto.so -> libcrypto.so.1.1
> -rwxr-xr-x    1 0        0           3.0M Jan 26 12:58
> /usr/lib/libcrypto.so.1.1
> 

like i said, you linked the wrong library, try to link
the right one. again, if you run the ldso under strace
the problem will be obvious and we dont have to waste time.

you should also strace ld to see what gets linked,
if it's /usr/lib/libcrypto... then that's wrong.
(instead of strace you can use -Wl,--trace)


  parent reply	other threads:[~2018-01-27 19:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 13:39 Stefan Fröberg
2018-01-26 14:21 ` Szabolcs Nagy
2018-01-26 23:50   ` Stefan Fröberg
2018-01-27 11:07     ` Szabolcs Nagy
2018-01-27 16:20       ` Stefan Fröberg
2018-01-27 16:42         ` Rich Felker
2018-01-27 17:14           ` Stefan Fröberg
2018-01-27 19:26         ` Szabolcs Nagy [this message]
2018-01-27 22:07           ` Stefan Fröberg
2018-01-28  0:54             ` Szabolcs Nagy
2018-02-07 17:35               ` Rich Felker
2018-02-07 20:28                 ` Szabolcs Nagy
2018-01-26 16:34 ` Rich Felker
2018-01-26 21:28   ` Stefan Fröberg

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=20180127192621.GJ4418@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    --cc=stefan.froberg@petroprogram.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).