[Bug ld/6431] ld says: invalid version 3 (max 0)

2008-06-25 Thread niki dot waibel at gmx dot net

--- Additional Comments From niki dot waibel at gmx dot net  2008-06-25 
12:45 ---
couple of other tests...
===
binutils-2.17.50.0.1: fails (like reported)
binutils-2.16.91.0.7: fails (like reported)
binutils-2.16.91.0.2: fails (like reported)
binutils-2.16.91.0.1: fails (different message)
binutils-2.16.90.0.3: fails (different message)
binutils-2.16.90.0.1: fails (different message)
binutils-2.15.94.0.2.2: fails (different message)
binutils-2.15.90.0.1: fails (different message)
binutils-2.14.90.0.1: fails (different message)
===
will attach this different message.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6431

--- 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 ld/6431] ld says: invalid version 3 (max 0)

2008-06-25 Thread niki dot waibel at gmx dot net

--- Additional Comments From niki dot waibel at gmx dot net  2008-06-25 
14:30 ---
Created an attachment (id=2798)
 -- (http://sourceware.org/bugzilla/attachment.cgi?id=2798action=view)
different message


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6431

--- 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 binutils/6483] objdump -g does not understand the debug info

2008-06-25 Thread chrisj at rtems dot org

--- Additional Comments From chrisj at rtems dot org  2008-06-26 02:14 
---
Hi Nick,

Please excuse the delay in getting back to this bug. We looked into this bug
more and found the i386 tools worked fine while the m68k do not. Further it
seems -g works and -e does not.

If I build RTEMS with --target=i386-rtems4.9 using the RTEMS tools obtained by
yum on a Fedora Core 8 64bit box, install RTEMS I can extract the debug symbols
with :

$ i386-rtems4.9-objdump -e librtemsbsp.a
In archive librtemsbsp.a:
!_TAG_FILE_FORMAT   2   /extended format/
!_TAG_FILE_SORTED   0   /0=unsorted, 1=sorted/
!_TAG_PROGRAM_AUTHORIan Lance Taylor, Salvador E. Tropea and others //
!_TAG_PROGRAM_NAME  objdump /From GNU binutils/
New compilation unit:
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
int
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:int32
char   
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:int8
long int   
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:int32
unsigned int   
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:uint32
long unsigned int  
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:uint32
long long int  
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:int64
long long unsigned int 
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:uint64
short int  
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:int16
short unsigned int 
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:uint16
signed char
/opt/work/sw/rtems/src/head/c/src/lib/libbsp/i386/pc386/../../shared/bootcard.c
0; kind:t  type:int8

Same command run with m68k tools on a --target=m68k-rtems4.9 build of RTEMS I 
get:

$ m68k-rtems4.9-objdump -e librtemsbsp.a
In archive librtemsbsp.a:
m68k-rtems4.9-objdump: bootcard.o: no recognized debugging information
m68k-rtems4.9-objdump: bspclean.o: no recognized debugging information
m68k-rtems4.9-objdump: bsplibc.o: no recognized debugging information
m68k-rtems4.9-objdump: bsppost.o: no recognized debugging information
m68k-rtems4.9-objdump: bsppredriverhook.o: no recognized debugging information
m68k-rtems4.9-objdump: bspstart.o: no recognized debugging information
 [snipped]

Regards
Chris

-- 
   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |


http://sourceware.org/bugzilla/show_bug.cgi?id=6483

--- 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