public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/6441] Value of slibdir changes after reconfigure for 64-bit targets Date: Wed, 15 Feb 2012 21:53:00 -0000 [thread overview] Message-ID: <bug-6441-131-hdog2qvtkZ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-6441-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=6441 Joseph Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinskia at gcc dot gnu.org AssignedTo|roland at gnu dot org |unassigned at sourceware | |dot org --- Comment #3 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-15 21:52:32 UTC --- I don't see why this would be specific to MIPS and not appear on other architectures such as x86_64. If it appears on x86_64 then this should be marked a libc bug; otherwise it would be good to explain why it doesn't appear on x86_64. In either case the patch should be resubmitted since even if it's somehow ports-specific it may well make sense to fix it in libc. -- 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 parent reply other threads:[~2012-02-15 21:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-6441-131@http.sourceware.org/bugzilla/> 2012-02-15 21:53 ` jsm28 at gcc dot gnu.org [this message] 2012-07-12 0:01 ` [Bug libc/6441] " pinskia at gcc dot gnu.org 2014-07-17 14:37 ` cvs-commit at gcc dot gnu.org 2015-08-27 22:03 ` [Bug build/6441] " jsm28 at gcc dot gnu.org 2008-04-22 1:55 [Bug libc/6441] New: " anemet at caviumnetworks dot com 2008-04-22 22:59 ` [Bug ports/6441] " drepper 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-6441-131-hdog2qvtkZ@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).