public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "malitzke at metronets 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: Fri, 19 May 2006 22:00:00 -0000 [thread overview] Message-ID: <20060519220012.14008.qmail@sourceware.org> (raw) In-Reply-To: <20060517171248.2671.malitzke@metronets.com> ------- Additional Comments From malitzke at metronets dot com 2006-05-19 22:00 ------- Well, after rebuilding most of X11R6 and reinstalling mozilla (2.7.12) that problem, apparently, misinterpretation of some character went away. Going back to the weak_alias issue. Now, after CVS updates to glibc, svn updates to gcc-4.2 (main trunk) and rebuilt binutils the order of the parameters has become irrelevant. I always thought it was really a gcc issue but after hand editing the four *.S by hand I thought it would be helpful to the glibc community to have a little patch. Again, it might be only of temporary interest to know that it is necessary to change VERSION=0605xx in the binutils bfd, gas, and gprof configure files to something like =2.17. Otherwise, the configuration of glibc will term ld and as as being too old. Finally in reading the equivalents to PR 333 (my PR 2672 was made equivalent to 333) I see that similarily to the gcc in-crowd, people from the user community are not really wellcome. At over 70 years, but as a former assembly language real-time systems programmer I can take a hint and will restrict myself to cases like ICE and segmentation errors. That issue in PR 2672 will either fade away or I will find a way to fake it out and continue building my own libcs, as I have been doing for a long time. I started with gcc-1.4.x and the Berkeley libraries; hacking both for use on SCO's Xenix. -- 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-19 22: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 2006-05-19 22:00 ` malitzke at metronets dot com [this message] 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=20060519220012.14008.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).