public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Mahmood Naderan <nt_mahmood@yahoo.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Using non-system glibc
Date: Wed, 27 May 2020 12:53:13 +0000 (UTC)	[thread overview]
Message-ID: <916655802.237517.1590583993055@mail.yahoo.com> (raw)
In-Reply-To: <916655802.237517.1590583993055.ref@mail.yahoo.com>

Hi
How can I use a custom glibc instead of the default system version?
I tried nginx with:


    $ GLIBCDIR=/opt/glibc-2.23-install 
    $ ./configure --with-ld-opt="-Wl,--emit-relocs"
    $ make && make install


But the final binary has no sign of my glibc installation


    $ ldd install/sbin/nginx
            linux-vdso.so.1 =>  (0x00007ffc07d43000)
            libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0a8d2f3000)
            libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0a8d0d6000)
            libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f0a8ce9e000)
            libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f0a8cc2e000)
            libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0a8ca14000)
            libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0a8c64a000)
            /lib64/ld-linux-x86-64.so.2 (0x00007f0a8d4f7000)


Any guess?


Regards,
Mahmood

       reply	other threads:[~2020-05-27 12:53 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 [this message]
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
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=916655802.237517.1590583993055@mail.yahoo.com \
    --to=nt_mahmood@yahoo.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).