public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29567] when `dlopen` glibc itself, it needs `__ctype_init`
Date: Wed, 14 Sep 2022 07:03:30 +0000	[thread overview]
Message-ID: <bug-29567-131-5GlobJut7Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29567-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29567

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
I'm afraid this is expected: the dynamic loader from the system libc is not
able to load libc.so.6 from the version you just built. Dynamic loader and
libc.so.6 must come from the exact same build.

You need to run your application with the new dynamic loader, too. Use an
explicit ld.so invocation (see the testrun.sh in the build tree for an
example), or set the loader with the -Wl,--dynamic-linker= option. You may also
have to link to the new glibc startup files,
<https://sourceware.org/glibc/wiki/Testing/Builds#Build100PctNew> has the
details.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-09-14  7:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  8:17 [Bug dynamic-link/29567] New: " linjy0410 at gmail dot com
2022-09-13  9:04 ` [Bug dynamic-link/29567] " fweimer at redhat dot com
2022-09-14  5:28 ` linjy0410 at gmail dot com
2022-09-14  7:03 ` fweimer at redhat dot com [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=bug-29567-131-5GlobJut7Z@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).