public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "macro at linux-mips dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/4863] New: MIPS/Linux: ld.so.cache unusable for (n)64/n32 Date: Mon, 30 Jul 2007 13:26:00 -0000 [thread overview] Message-ID: <20070730132628.4863.macro@linux-mips.org> (raw) Hello, The "libc-ports" list does not seem to attract anyone, so I am putting the solution for the problem here so that it does not get lost in the long term. It has been the case with glibc 2.4 and it appears to me that it still is. When built for the (n)64 or presumably the n32 ABI, ld.so is unable to use the cache as it checks for the wrong o32 ID. Here is a fix. Tested for (n)64. 2007-07-23 Maciej W. Rozycki <macro@linux-mips.org> * sysdeps/unix/sysv/linux/mips/dl-cache.h (_DL_CACHE_DEFAULT_ID): New macros for the (n)64 and n32 ABIs. (_dl_cache_check_flags): Define if _DL_CACHE_DEFAULT_ID has been. Please apply. Maciej -- Summary: MIPS/Linux: ld.so.cache unusable for (n)64/n32 Product: glibc Version: 2.4 Status: NEW Severity: normal Priority: P2 Component: ports AssignedTo: roland at gnu dot org ReportedBy: macro at linux-mips dot org CC: glibc-bugs at sources dot redhat dot com GCC build triplet: mips64el-unknown-linux-gnu GCC host triplet: mips64el-unknown-linux-gnu GCC target triplet: mips64el-unknown-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=4863 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2007-07-30 13:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-30 13:26 macro at linux-mips dot org [this message] 2007-07-30 13:28 ` [Bug ports/4863] " macro at linux-mips dot org 2007-10-27 15:39 ` aj at suse dot de 2008-12-07 5:21 ` robert dot zhangle at gmail dot com 2009-03-18 14:45 ` jsm28 at gcc dot gnu dot org
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=20070730132628.4863.macro@linux-mips.org \ --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).