public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/4507] sysv/linux/i386/sysdep.h problems with asm-preproc that define __i686 Date: Tue, 15 May 2007 13:39:00 -0000 [thread overview] Message-ID: <20070515133850.32165.qmail@sourceware.org> (raw) In-Reply-To: <20070514191751.4507.eggert@gnu.org> ------- Additional Comments From eggert at gnu dot org 2007-05-15 14:38 ------- Created an attachment (id=1839) --> (http://sourceware.org/bugzilla/attachment.cgi?id=1839&action=view) revised __i686 patch, which simply undefs the symbol OK, thanks, I didn't know the symbol couldn't be changed. In that case, Wolf's original patch seems apropos and I have attached it, replacing the incorrect patch. -- What |Removed |Added ---------------------------------------------------------------------------- Attachment #1838 is|0 |1 obsolete| | http://sourceware.org/bugzilla/show_bug.cgi?id=4507 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2007-05-15 13:39 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-14 18:18 [Bug libc/4507] New: " eggert at gnu dot org 2007-05-14 18:18 ` [Bug libc/4507] " eggert at gnu dot org 2007-05-14 19:02 ` drepper at redhat dot com 2007-05-15 13:39 ` eggert at gnu dot org [this message] 2007-05-15 13:41 ` eggert at gnu dot org 2007-11-08 0:00 ` drepper at redhat dot com 2007-12-10 1:01 ` vapier at gentoo dot org 2007-12-19 20:25 ` wbrana at gmail dot com 2008-08-10 15:07 ` wbrana at gmail dot com 2009-12-21 5:05 ` divided dot mind at gmail dot com [not found] <bug-4507-131@http.sourceware.org/bugzilla/> 2012-02-18 0:19 ` jsm28 at gcc dot gnu.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=20070515133850.32165.qmail@sourceware.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).