mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jean-Marc Pigeon <jmp@safe.ca>
To: musl@lists.openwall.com
Subject: Re: perl native musl, ldd
Date: Thu, 02 Apr 2015 14:17:36 -0400	[thread overview]
Message-ID: <551D87C0.4010409@safe.ca> (raw)
In-Reply-To: <20150402161837.GA6817@brightrain.aerifal.cx>

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

On 04/02/2015 12:18 PM, Rich Felker wrote:
> On Thu, Apr 02, 2015 at 11:53:19AM -0400, Jean-Marc Pigeon wrote:
>> Hello,
>>
>>
>> I compiled perl (native, under gcc-musl) and I have
>> a non expected result with ldd.
>>
>> Example: (with a musl system tree chroot)
>> bash=4/3# cd /usr/lib/perl5/5.20.2/auto/IPC/SysV/
>> bash-4.3# ldd SysV.so
>> 	ldd (0x7f5d60dd2000)
>> 	libc.so => ldd (0x7f5d60dd2000)
>> Error relocating SysV.so: Perl_croak: symbol not found
>> Error relocating SysV.so: Perl_sv_setiv: symbol not found
>> Error relocating SysV.so: Perl_sv_2pv_flags: symbol not found
>> Error relocating SysV.so: Perl_av_store: symbol not found
>> etc.
>>
>> While with glibc (with a glibc system tree chroot)
>> bash-4.3# cd /usr/lib/perl5/5.20.2/auto/IPC/SysV
>> bash-4.3# ldd SysV.so
>> 	linux-vdso.so.1 (0x00007fff09556000)
>> 	libc.so.6 => /lib64/libc.so.6 (0x00007f25be856000)
>> 	/lib64/ld-linux-x86-64.so.2 (0x00007f25bee00000)
>>
>> I am puzzled about those "Error relocating"
>> native (within musl) perl make didn't return error,
>> so I am assuming everything went well.
>>
>> Advices...? hints? do we have a real problem
>> with musl ldd or I goofed somehow?
> 
> Hmm, it seems like glibc ldd does not (or at least does not always)
> report symbols that can't be resolved. What seems to be happening is
> that the above symbols are intended to be provided by the main program
> (the perl interpreter) loading SysV.so rather than resolved via
> library dependencies.
> 
> I hadn't really considered using ldd on .so files, only on main
> programs where this would not be an issue.
> 
> If someone can help determine exactly what glibc ldd's behavior is
> here (does it always ignore missing symbols? or only for .so files,
> and if so, how does it distinguish .so file from main program?) it
> should be easy to make musl's behavior match.
> 

I am using a packager using ldd to establish
dependencies list.



-- 

A bientôt
===========================================================
Jean-Marc Pigeon                        E-Mail: jmp@safe.ca
SAFE Inc.                             Phone: (514) 493-4280
  Clement, 'a kiss solution' to get rid of SPAM (at last)
     Clement' Home base <"http://www.clement.safe.ca">
===========================================================


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3903 bytes --]

  reply	other threads:[~2015-04-02 18:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 15:53 Jean-Marc Pigeon
2015-04-02 16:18 ` Rich Felker
2015-04-02 18:17   ` Jean-Marc Pigeon [this message]
2015-04-02 18:48     ` u-wsnj
2015-04-02 20:40       ` Jean-Marc Pigeon
2015-04-02 20:48         ` Laurent Bercot
2015-04-02 21:08         ` Nathan McSween
2015-04-02 21:09         ` u-wsnj
2015-04-02 21:26         ` Rich Felker
2015-04-02 21:34         ` Szabolcs Nagy
2015-04-03  0:57           ` Jean-Marc Pigeon
2015-04-03  1:18             ` bug? in musl libc failed to preserve ownership for Jean-Marc Pigeon
2015-04-03  2:15               ` Rich Felker

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=551D87C0.4010409@safe.ca \
    --to=jmp@safe.ca \
    --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).