public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rmh at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug linuxthreads/12300] [PATCH] RTLD_SINGLE_THREAD_P used unconditionally but only available on ports/NPTL Date: Wed, 08 Dec 2010 20:12:00 -0000 [thread overview] Message-ID: <bug-12300-131-uuvnYJ6QvA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12300-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=12300 --- Comment #4 from Robert Millan <rmh at gnu dot org> 2010-12-08 19:59:07 UTC --- (In reply to comment #3) > The directories I suggested removing were the sysdeps/unix/sysv/linux > ones, not the other linuxthreads directories in ports that are nominally > applicable to non-Linux targets. Your patch was also for a > sysdeps/unix/sysv/linux directory. Note that as syscall ABI on kFreeBSD is the same as on Linux, sysdep-cancel.h can be implemented by #including the Linux version (this is why I'm patching a sysdeps/unix/sysv/linux directory). > I don't think ports should be a dumping place for dead code someone thinks > might conceivably be useful one day; The missing definition is needed on mipsel-kfreebsd-gnu. Sorry for not making this clear the first time. > I would strongly advise those caring about the other targets to develop > proper POSIX threads implementations for them that use whatever interfaces > are most appropriate for each kernel (while making sure that all the > headers included in generic glibc code present the same interface as the > NPTL versions do, to avoid problems with generic code only working with > NPTL) rather than relying on long-unmaintained code that does not work > well with current libc. You might be able to use parts of the > Linuxthreads code or the NPTL code in such implementations; I don't know. Yeah, I know. Unfortunately manpower doesn't allow this for now (help is welcome). > The CVS repository (:pserver:anoncvs@sources.redhat.com:/cvs/glibc, module > linuxthreads) still appears to exist. Thanks for the pointer. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2010-12-08 19:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-08 17:06 [Bug linuxthreads/12300] New: " rmh at gnu dot org 2010-12-08 17:08 ` [Bug linuxthreads/12300] " joseph at codesourcery dot com 2010-12-08 17:18 ` rmh at gnu dot org 2010-12-08 19:59 ` joseph at codesourcery dot com 2010-12-08 20:12 ` rmh at gnu dot org [this message] 2010-12-09 5:31 ` joseph at codesourcery dot com 2012-02-16 14:28 ` jsm28 at gcc dot gnu.org 2014-02-06 18:25 ` jsm28 at gcc dot gnu.org 2014-06-30 6:22 ` fweimer at redhat 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-12300-131-uuvnYJ6QvA@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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).