public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Mahmood Naderan <nt_mahmood@yahoo.com>
To: Mahmood Naderan via Libc-help <libc-help@sourceware.org>,
	 Florian Weimer <fweimer@redhat.com>
Subject: Re: Using non-system glibc
Date: Thu, 28 May 2020 06:54:35 +0000 (UTC)	[thread overview]
Message-ID: <435676489.603392.1590648875948@mail.yahoo.com> (raw)
In-Reply-To: <1909951272.395170.1590604665757@mail.yahoo.com>

On the way to use a custom glibc build, I tried to modify the Makefile of the program (nginx) with 


-Wl,--rpath=/opt/glibc-2.23-install -Wl,--dynamic-linker=/opt/glibc-2.23-install/lib/ld-2.23.so

After build and install, I see the following ldd output

$ ldd install/sbin/nginx
        linux-vdso.so.1 =>  (0x00007ffd6c335000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fad02350000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fad02133000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007fad01efb000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fad01c8b000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fad01a71000)
        libc.so.6 => /opt/glibc-2.23-install/libc.so.6 (0x00007fad016d0000)
        /opt/glibc-2.23-install/lib/ld-2.23.so => /lib64/ld-linux-x86-64.so.2 (0x00007fad02554000)



The last line shows that my own glibc build is using system libc. But the lic.so.6 file my program is using, comes from my own glibc build.

So, is that all? Or something is missing? Any advice?


Regards,
Mahmood 


  reply	other threads:[~2020-05-28  6:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <916655802.237517.1590583993055.ref@mail.yahoo.com>
2020-05-27 12:53 ` Mahmood Naderan
2020-05-27 13:05   ` Florian Weimer
2020-05-27 17:47     ` Mahmood Naderan
2020-05-27 18:37       ` Mahmood Naderan
2020-05-28  6:54         ` Mahmood Naderan [this message]
2020-05-28 11:53           ` Florian Weimer
2020-05-28 12:12             ` Mahmood Naderan
2020-05-28 12:16               ` Florian Weimer
2020-05-28 12:31                 ` Mahmood Naderan

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=435676489.603392.1590648875948@mail.yahoo.com \
    --to=nt_mahmood@yahoo.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@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).