public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30100] [patch] add dlmem()
Date: Thu, 09 Feb 2023 19:02:49 +0000 [thread overview]
Message-ID: <bug-30100-131-x6esXEMeWl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30100-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30100
--- Comment #19 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Stas Sergeev from comment #18)
> Still have dozens of failures like this:
>
> FAIL: conform/XPG42/sys/shm.h/linknamespace
> FAIL: conform/XPG42/sys/socket.h/linknamespace
> FAIL: conform/XPG42/sys/time.h/linknamespace
> FAIL: conform/XPG42/sys/timeb.h/linknamespace
> FAIL: conform/XPG42/sys/uio.h/linknamespace
> FAIL: conform/XPG42/sys/wait.h/linknamespace
> FAIL: conform/XPG42/syslog.h/linknamespace
> FAIL: conform/XPG42/termios.h/linknamespace
> FAIL: conform/XPG42/time.h/linknamespace
> FAIL: conform/XPG42/ucontext.h/linknamespace
> FAIL: conform/XPG42/ulimit.h/linknamespace
> FAIL: conform/XPG42/unistd.h/linknamespace
> FAIL: conform/XPG42/utmpx.h/linknamespace
> FAIL: conform/XPG42/wordexp.h/linknamespace
> FAIL: elf/check-abi-libc
>
> Not sure if they are related to my patch or not...
> To be figured out.
Most likely you are issuing a libc function without using its internal alias
(for instance mmap64 instead of __mmap64). The linknamespace.out file will
hint you which symbol is polluting the namespace.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-09 19:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 9:47 [Bug dynamic-link/30100] New: " stsp at users dot sourceforge.net
2023-02-09 9:48 ` [Bug dynamic-link/30100] " stsp at users dot sourceforge.net
2023-02-09 11:51 ` adhemerval.zanella at linaro dot org
2023-02-09 12:17 ` stsp at users dot sourceforge.net
2023-02-09 12:48 ` adhemerval.zanella at linaro dot org
2023-02-09 13:59 ` stsp at users dot sourceforge.net
2023-02-09 14:16 ` adhemerval.zanella at linaro dot org
2023-02-09 14:34 ` stsp at users dot sourceforge.net
2023-02-09 15:14 ` stsp at users dot sourceforge.net
2023-02-09 16:51 ` stsp at users dot sourceforge.net
2023-02-09 16:55 ` adhemerval.zanella at linaro dot org
2023-02-09 16:56 ` adhemerval.zanella at linaro dot org
2023-02-09 17:37 ` stsp at users dot sourceforge.net
2023-02-09 17:58 ` stsp at users dot sourceforge.net
2023-02-09 18:22 ` schwab@linux-m68k.org
2023-02-09 18:29 ` stsp at users dot sourceforge.net
2023-02-09 18:49 ` stsp at users dot sourceforge.net
2023-02-09 18:56 ` stsp at users dot sourceforge.net
2023-02-09 19:00 ` stsp at users dot sourceforge.net
2023-02-09 19:02 ` adhemerval.zanella at linaro dot org [this message]
2023-02-10 8:27 ` stsp at users dot sourceforge.net
2023-02-10 8:30 ` stsp at users dot sourceforge.net
2023-02-10 8:30 ` stsp at users dot sourceforge.net
2023-02-10 9:08 ` stsp at users dot sourceforge.net
2023-02-10 10:04 ` stsp at users dot sourceforge.net
2023-02-10 13:09 ` stsp at users dot sourceforge.net
2023-02-10 13:46 ` adhemerval.zanella at linaro dot org
2023-02-11 17:37 ` stsp at users dot sourceforge.net
2023-02-11 19:08 ` stsp at users dot sourceforge.net
2023-02-11 19:37 ` stsp at users dot sourceforge.net
2023-02-16 13:40 ` stsp at users dot sourceforge.net
2023-03-17 6:41 ` stsp at users dot sourceforge.net
2023-03-17 6:45 ` stsp at users dot sourceforge.net
2023-03-18 18:14 ` stsp at users dot sourceforge.net
2023-03-18 23:30 ` janderson at rice dot edu
2023-03-19 2:14 ` stsp at users dot sourceforge.net
2023-03-20 15:47 ` stsp at users dot sourceforge.net
2023-03-20 16:06 ` stsp at users dot sourceforge.net
2023-03-29 14:45 ` sam at gentoo dot org
2023-05-05 14:29 ` stsp at users dot sourceforge.net
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-30100-131-x6esXEMeWl@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).