public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28455] New: -Wl,--enable-new-dtags doesn't work
Date: Fri, 15 Oct 2021 12:11:18 +0000	[thread overview]
Message-ID: <bug-28455-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28455
           Summary: -Wl,--enable-new-dtags doesn't work
           Product: glibc
           Version: 2.34
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
  Target Milestone: ---

On Linux/x86-64, use -Wl,--enable-new-dtags to build glibc causes

FAIL: dlfcn/bug-dl-leaf
FAIL: elf/constload1
FAIL: elf/global
FAIL: elf/tst-audit10
FAIL: elf/tst-audit11
FAIL: elf/tst-audit12
FAIL: elf/tst-audit14-cmp
FAIL: elf/tst-audit15-cmp
FAIL: elf/tst-audit16-cmp
FAIL: elf/tst-audit4
FAIL: elf/tst-audit5
FAIL: elf/tst-audit6
FAIL: elf/tst-audit7
FAIL: elf/tst-dlmopen-dlerror
FAIL: elf/tst-dlmopen-gethostbyname
FAIL: elf/tst-dlmopen1
FAIL: elf/tst-dlmopen3
FAIL: elf/tst-dlmopen4
FAIL: elf/tst-dlopen-nodelete-reloc
FAIL: elf/tst-nodelete-dlclose
FAIL: elf/tst-single_threaded
FAIL: elf/tst-single_threaded-pthread
FAIL: elf/tst-sonamemove-dlopen
FAIL: elf/tst-sonamemove-link
FAIL: elf/tst-tls-ie-dlmopen
FAIL: elf/unload6
FAIL: nss/tst-nss-test1
FAIL: nss/tst-nss-test2
FAIL: nss/tst-nss-test4
FAIL: nss/tst-nss-test5

It looks like that DT_RUNPATH isn't properly handled.

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

             reply	other threads:[~2021-10-15 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 12:11 hjl.tools at gmail dot com [this message]
2021-10-15 12:16 ` [Bug dynamic-link/28455] " hjl.tools at gmail dot com
2021-10-15 12:48 ` hjl.tools at gmail dot com
2021-10-15 13:32 ` hjl.tools at gmail dot com
2021-10-22 14:53 ` hjl.tools at gmail dot com
2021-10-22 23:27 ` hjl.tools at gmail dot com
2021-10-29 13:30 ` sam at gentoo dot org
2021-12-13 15:32 ` cvs-commit at gcc dot gnu.org
2022-01-03 12:42 ` hjl.tools at gmail dot com
2022-01-04 13:54 ` cvs-commit at gcc dot gnu.org
2022-01-24 13:54 ` cvs-commit at gcc dot gnu.org
2022-01-24 13:55 ` hjl.tools at gmail dot com

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-28455-131@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).