[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-15 Thread ian at airs dot com
--- Additional Comments From ian at airs dot com 2005-04-15 16:35 --- My point is that symbols like the STT_FILE symbol or STT_SECTION symbols do not need to have a name. It is not a bug to have a symbol with no name. The macro tc_canonicalize_symbol_name applies to all symbols. That m

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-15 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-15 15:26 --- Rejecting zero-length symbols could be undone, but I don't see the point; namely I can't see how you would ever use such a symbol (a standalone # operator is certainly illegal on ia64, and besides that ia64 has

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-15 Thread ian at airs dot com
--- Additional Comments From ian at airs dot com 2005-04-15 14:56 --- Subject: Re: New: Error: Zero-length symbol is illegal Nick Clifton <[EMAIL PROTECTED]> writes: > > The ia64 assembler is choking on `.file ""' with the error message > > "Zero-length symbol is illegal". According t

Re: [Bug gas/847] New: Error: Zero-length symbol is illegal

2005-04-15 Thread Ian Lance Taylor
Nick Clifton <[EMAIL PROTECTED]> writes: > > The ia64 assembler is choking on `.file ""' with the error message > > "Zero-length symbol is illegal". According to the GAS manual this > > should be allowed. The problem is that gcc 3.4 and later now uses > > `.file ""' instead of `.file ""' when in

[Bug gas/848] gas testsuite FAIL: macros dot

2005-04-15 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-15 13:34 --- This is more wide-spread, other affected targets are hppa, ns32k, and vax. Slightly different reasons cause d30v, dlx, i860, and or32 to fail. For these, the testcase output expectation needs to be adjusted; I

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-15 Thread jbeulich at novell dot com
--- Additional Comments From jbeulich at novell dot com 2005-04-15 12:24 --- I see two problems with this suggestion: The small one is that the change to read.c isn't shown. The larger one is that I don't think this is the right thing to do here. tc_canonicalize_symbol_name shouldn't b

[Bug ld/815] [C-api -> C++ lib] undefined symbol _Unwind*

2005-04-15 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2005-04-15 11:19 --- libqt-mt.so.3.3.4 defines [EMAIL PROTECTED] $22 = {root = {root = {next = 0x85d2380, string = 0x85a9ea0 "[EMAIL PROTECTED]", hash = 421875337}, type = bfd_link_hash_undefweak, u = {undef = {ne

[Bug gas/847] Error: Zero-length symbol is illegal

2005-04-15 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2005-04-15 11:46 --- Subject: Re: New: Error: Zero-length symbol is illegal Hi Andreas, > The ia64 assembler is choking on `.file ""' with the error message > "Zero-length symbol is illegal". According to the GAS manual this shoul

Re: [Bug gas/847] New: Error: Zero-length symbol is illegal

2005-04-15 Thread Nick Clifton
Hi Andreas, The ia64 assembler is choking on `.file ""' with the error message "Zero-length symbol is illegal". According to the GAS manual this should be allowed. The problem is that gcc 3.4 and later now uses `.file ""' instead of `.file ""' when input comes from stdin. Hmm, well the documen

[Bug ld/815] [C-api -> C++ lib] undefined symbol _Unwind*

2005-04-15 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2005-04-15 11:16 --- I've traced what is happening, and everything now makes sense. This fix checked in to mainline and 2.16 should cure your problem. PR ld/815 * elflink.c (elf_smash_syms): Clear undef.next

Re: [Bug ld/850] New: linker issued assertion failure elf64-ppc.c:7771

2005-04-15 Thread Nick Clifton
Hi Robert, The problem caught is about error during linking of executable. /usr/bin/ld: BFD 041202 20041202 assertion fail elf64-ppc.c:7771 Please could you provide a simple way to reproduce this problem. This error msg is repeated many times. ld -V GNU ld version 041202 20041202 You may find that

[Bug ld/850] linker issued assertion failure elf64-ppc.c:7771

2005-04-15 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2005-04-15 10:49 --- Subject: Re: New: linker issued assertion failure elf64-ppc.c:7771 Hi Robert, > The problem caught is about error during linking of executable. > /usr/bin/ld: BFD 041202 20041202 assertion fail elf64-ppc.c:7771

[Bug ld/815] [C-api -> C++ lib] undefined symbol _Unwind*

2005-04-15 Thread pluto at pld-linux dot org
--- Additional Comments From pluto at pld-linux dot org 2005-04-15 07:20 --- (In reply to comment #11) full link command: /usr/bin/ld --eh-frame-hdr -m elf_i386 -shared -o .libs/wmfthumbnail.so -z combreloc -L/usr/lib/gcc/i686-pld-linux/4.0.0 -L/home/users/pluto/rpm/BUILD/kdelib