public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "decimal at us dot ibm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2671] On powerpc the order of parameters in weak_alias is significant Date: Thu, 18 May 2006 15:00:00 -0000 [thread overview] Message-ID: <20060518150022.6134.qmail@sourceware.org> (raw) In-Reply-To: <20060517171248.2671.malitzke@metronets.com> ------- Additional Comments From decimal at us dot ibm dot com 2006-05-18 15:00 ------- For future reference it is not very helpful to put a patch in that the patch program cannot process unmodified. Additionally you had extra spaces in front of __bind in the line +weak_alias ( __bind, bind) I was able to edit your patch and both insert it into a comment and attach it without problem. I suggest you resolve the problem on your end before you attempt to submit other patches. Do you have any testcase beyond the build issues you saw? -- http://sourceware.org/bugzilla/show_bug.cgi?id=2671 ------- 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:[~2006-05-18 15:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-17 17:12 [Bug libc/2671] New: " malitzke at metronets dot com 2006-05-17 17:26 ` [Bug libc/2671] " malitzke at metronets dot com 2006-05-17 18:01 ` decimal at us dot ibm dot com 2006-05-17 18:13 ` malitzke at metronets dot com 2006-05-17 18:18 ` malitzke at metronets dot com 2006-05-17 18:30 ` decimal at us dot ibm dot com 2006-05-18 2:28 ` malitzke at metronets dot com 2006-05-18 14:56 ` decimal at us dot ibm dot com 2006-05-18 14:57 ` decimal at us dot ibm dot com 2006-05-18 15:00 ` decimal at us dot ibm dot com [this message] 2006-05-19 22:00 ` malitzke at metronets dot com 2006-09-09 17:23 ` 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=20060518150022.6134.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).