Re: bug report
Hi Bob, I have received this bug using GNAT GDB 3.15p. Is there anything I can do to get more information on what's failing? (ie environment variable) BFD: BFD internal error, aborting at coffcode.h line 749 in styp_to_sec_flags BFD: Please report this bug. You can run the program inside GDB. You should then be able to backtrack from the abort to find out what is happening. Also if you are using an older version of binutils then you might try upgrading to the latest release (2.15) or even the mainline sources in the CVS repository. If neither of these things helps then you can submit a bug report for us to investigate. There is a bugzilla system set up at: http://sources.redhat.com/bugzilla/ Or you could email a report to this list. (Please do try to include as much helpful information as possible, and if at all practical a *small* testcase that reproduces the problem). Cheers Nick ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Binutils build broken at FreeBSD 5.3 after -Werror enabling
After patch http://sourceware.org/ml/binutils-cvs/2005-03/msg00191.html binutils build broken at FreeBSD 5.3 Build terminate with message: In file included from /usr/home/wanderer/pkg/build/binutils/src/src/binutils/size.c:34: /usr/home/wanderer/pkg/build/binutils/src/src/binutils/../include/getopt.h:116: warning: function declaration isn't a prototype I see this warning long time (>2 years) already when i build binutils at FreeBSD. Using --disable-werror help build binutils. Please, add my e-mail address to replies: I am not recieve posts from any binutils maillists. Vladimir ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/795] UCN problems exposed by GCC tests: gcc.dg/ucnid-2.c, 3, 4 and 6.
--- Additional Comments From nickc at redhat dot com 2005-03-18 11:38 --- Hi Hans-Peter, 0x80 and 0xc3 are not ASCII characters, so why would you expect GAS to be able to assemble them if they are not inside a string defintion ? For what it is worth I was able to compile and assemble all of the ucnid-?.c testcases using the latest binutils and gcc with an mmix-knuth-mmixware toolchain and I did not see these errors. Cheers Nick -- What|Removed |Added Status|NEW |WAITING http://sources.redhat.com/bugzilla/show_bug.cgi?id=795 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/795] UCN problems exposed by GCC tests: gcc.dg/ucnid-2.c, 3, 4 and 6.
--- Additional Comments From hp at sourceware dot org 2005-03-18 12:10 --- In response to comment #1, I would expect GAS to assemble it because it's generated by GCC (presumed correct). Since you have a mmix-knuth-mmixware toolchain available, I suggest looking at the generated assembly from gcc.dg/ucnid-2.c. You should see this symbol. I don't know why you had success assembling the test-cases on your system. I'm on FC2. -- What|Removed |Added Status|WAITING |NEW http://sources.redhat.com/bugzilla/show_bug.cgi?id=795 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/795] UCN problems exposed by GCC tests: gcc.dg/ucnid-2.c, 3, 4 and 6.
--- Additional Comments From hp at sourceware dot org 2005-03-18 12:16 --- Perhaps not as obvious as I thought, so I'll mention that the GCC ucnid tests are supposed to test exactly what this PR is about; UCN-coded identifiers. -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=795 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: [Bug gas/795] UCN problems exposed by GCC tests: gcc.dg/ucnid-2.c, 3, 4 and 6.
Hi Hans-Peter, In response to comment #1, I would expect GAS to assemble it because it's generated by GCC (presumed correct). My current theory is that it must be a gcc bug. But then I could just be passing the buck... Since you have a mmix-knuth-mmixware toolchain available, I suggest looking at the generated assembly from gcc.dg/ucnid-2.c. You should see this symbol. Hmm, well what I see is: [...] LC:0 IS @ BYTE #e3,#82,#b2,#0 [...] (with no embedded 0x80 or 0xc3 characters) I don't know why you had success assembling the test-cases on your system. I'm on FC2. I'm on RedHat Enterprise Linux 3 but I am using a gcc toolchain built from today's sources in the FSF GCC repository (and today's binutils). Cheers Nick ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/795] non-ascii-identifier problems exposed by GCC tests: gcc.dg/ucnid-2.c, 3, 4 and 6.
--- Additional Comments From hp at sourceware dot org 2005-03-18 12:18 --- ...except of course that the identifiers aren't UCN-encoded in the GCC-generated assembly. -- What|Removed |Added Summary|UCN problems exposed by GCC |non-ascii-identifier |tests: gcc.dg/ucnid-2.c, 3, |problems exposed by GCC |4 and 6.|tests: gcc.dg/ucnid-2.c, 3, ||4 and 6. http://sources.redhat.com/bugzilla/show_bug.cgi?id=795 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/795] non-ascii-identifier problems exposed by GCC tests: gcc.dg/ucnid-2.c, 3, 4 and 6.
--- Additional Comments From nickc at redhat dot com 2005-03-18 13:06 --- Subject: Re: UCN problems exposed by GCC tests: gcc.dg/ucnid-2.c, 3, 4 and 6. Hi Hans-Peter, > In response to comment #1, I would expect GAS to assemble it because it's > generated by GCC (presumed correct). My current theory is that it must be a gcc bug. But then I could just be passing the buck... > Since you have a mmix-knuth-mmixware > toolchain available, I suggest looking at the generated assembly from > gcc.dg/ucnid-2.c. You should see this symbol. Hmm, well what I see is: [...] LC:0 IS @ BYTE #e3,#82,#b2,#0 [...] (with no embedded 0x80 or 0xc3 characters) > I don't know why you had success > assembling the test-cases on your system. I'm on FC2. I'm on RedHat Enterprise Linux 3 but I am using a gcc toolchain built from today's sources in the FSF GCC repository (and today's binutils). Cheers Nick -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=795 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
opcodes po file problem (Modified by Clytie Siddall)
Hi :) I've been discussing this problem with Ian Lance Taylor, and he has asked me to pass it on to you. Evidently a string is marked c-format when it shouldn't be (this stops it passing the checks to be submitted as a valid translation), and I can't fix that: any changes in the original file have to be made before the .po file is generated, otherwise the altered original data will cause problems when the translation is reintegrated with the program being translated. I don't know if you or Ian need to make the change, but now you both know about it. :) If you can edit the file and release the update to the Translation Project at the University of MontrÃal, then I can finish and submit the translation. Thankyou. :) from Clytie __mail with Ian___ Hi again :) On 17/03/2005, at 2:06 PM, Ian Lance Taylor wrote: Clytie Siddall <[EMAIL PROTECTED]> writes: #: ip2k-asm.c:376 #, c-format msgid "%operator operand is not a symbol" msgstr "%toÃn tá tÃc tá khÃng phái là mát kà hiáu" I don't understand exactly what's bothering it; the error message is: opcodes/opcodes-2.15.96.pot:396: number of format specifications in `msgid' and `msgstr' does not match I think the problem is that there is a c-format market on the string. I don't know why that is there. The string is not a printf string. Unfortunately, I'm not allowed to edit that data, or the msgid string, since that will cause problems when you reintegrate the translated file with the application. Do I need to send this request to the binultils address, or can you amend the file and send in the update? Otherwise I can't submit the translation, which would be a waste. ___end excerpt___ he answered: Yes, I guess you should send that to the binutils list as well. I'm not sure why the c-format marking is there. and I have. :) from Clytie (vi-VN, team/nhÃm Gnome-vi) Clytie Siddall--Renmark, in the Riverland of South Australia á thÃnh phá Renmark, tái mián sÃng cáa Nam Ãc smime.p7s Description: S/MIME cryptographic signature ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
further info on opcodes file
The gurus have spoken, on the Translation Project mailing list, anyway. :) The developer should not change the .pot file directly - he would have to do this again and again each time the .pot file is regenerated - but rather add a comment in the line before the string in the C code: /* xgettext:no-c-format */ so there you are. Sorry for all the emails, but I haven't run into this problem before, so it's all learning for me too. from Clytie (vi-VN, team/nhÃm Gnome-vi) Clytie Siddall--Renmark, in the Riverland of South Australia á thÃnh phá Renmark, tái mián sÃng cáa Nam Ãc ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
