gdb 6.3 build problem on arm/xscale

From: eransha (eransha.groups_at_gmail.com)
Date: 08/08/05 

Date: 8 Aug 2005 09:45:39 -0700

Hi,
I downloaded gdb 6.3(same occured at 6.2) and tried to build it as
follows:
1. ../gdb-6.3/configure --target=$TARGET --prefix=${PREFIX}
TARGET is armeb-xscale-linux-gnu (big endian arm)
and PREFIX is armeb-xscale-linux-gnu directory
2. make
but then after awhile I get the error:
gcc -c -DHAVE_CONFIG_H -DPROFILE=1 -DWITH_PROFILE=-1
-DDEFAULT_INLINE=0 -DMODET -DNEED_UI_LOOP_HOOK
-DSIM_TARGET_SWITCHES -I. -I../../../gdb-6.3/sim/arm -I../common
-I../../../gdb-6.3/sim/arm/../­common -I../../include
-I../../../gdb-6.3/sim/arm/../­../include -I../../bfd
-I../../../gdb-6.3/sim/arm/../­../bfd -I../../opcodes
-I../../../gdb-6.3/sim/arm/../­../opcodes -I../../intl
-I../../../gdb-6.3/sim/arm/../­../intl -g -O2
../../../gdb-6.3/sim/arm/iwmmx­t.c
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function 'WMAC':
../../../gdb-6.3/sim/arm/iwmmx­t.c:2117: error: invalid lvalue in
assignment
../../../gdb-6.3/sim/arm/iwmmx­t.c:2133: error: invalid lvalue in
assignment
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function 'WMADD':
../../../gdb-6.3/sim/arm/iwmmx­t.c:2169: error: invalid lvalue in
assignment
../../../gdb-6.3/sim/arm/iwmmx­t.c:2177: error: invalid lvalue in
assignment
../../../gdb-6.3/sim/arm/iwmmx­t.c:2186: error: invalid lvalue in
assignment
../../../gdb-6.3/sim/arm/iwmmx­t.c:2191: error: invalid lvalue in
assignment
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function 'WSLL':
../../../gdb-6.3/sim/arm/iwmmx­t.c:2840: warning: integer constant is
too large for 'long' type
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function 'WSRA':
../../../gdb-6.3/sim/arm/iwmmx­t.c:2917: warning: integer constant is
too large for 'long' type
../../../gdb-6.3/sim/arm/iwmmx­t.c:2917: warning: integer constant is
too large for 'long' type
../../../gdb-6.3/sim/arm/iwmmx­t.c:2919: warning: integer constant is
too large for 'long' type
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function 'WSRL':
../../../gdb-6.3/sim/arm/iwmmx­t.c:2988: warning: integer constant is
too large for 'long' type
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function 'WUNPCKEH':
../../../gdb-6.3/sim/arm/iwmmx­t.c:3290: warning: integer constant is
too large for 'long' type
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function 'WUNPCKEL':
../../../gdb-6.3/sim/arm/iwmmx­t.c:3357: warning: integer constant is
too large for 'long' type
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function
'Fetch_Iwmmxt_Register':
../../../gdb-6.3/sim/arm/iwmmx­t.c:3707: warning: incompatible
implicit
declaration of built-in function 'memcpy'
../../../gdb-6.3/sim/arm/iwmmx­t.c:3712: warning: incompatible
implicit
declaration of built-in function 'memcpy'
../../../gdb-6.3/sim/arm/iwmmx­t.c: In function
'Store_Iwmmxt_Register':
../../../gdb-6.3/sim/arm/iwmmx­t.c:3722: warning: incompatible
implicit
declaration of built-in function 'memcpy'
../../../gdb-6.3/sim/arm/iwmmx­t.c:3727: warning: incompatible
implicit
declaration of built-in function 'memcpy'
make[2]: *** [iwmmxt.o] Error 1

Is there a special patch I need to apply in order to compile the gdb
for armeb?

Relevant Pages

  • building gdb for ARM
    ... declaration of built-in function 'memcpy' ...
    (comp.sys.arm)
  • Re: Are decorators really that different from metaclasses...
    ... >>declaration, just as we do with its docstring. ... Assignment in Python has quite ... > bodies are executed when the class statement is executed, ... Maybe we just need to be clear as to which lines under the def statement ...
    (comp.lang.python)
  • Re: C99: Suggestions for style(9)
    ... M. Warner Losh schrieb: ... It is worrisome that somebody is inclined to obfuscate the code (in this case replacing multiple variables with descriptive names by a single variable with a generic name) because it is less hassle to conform to stylethis way. ... So it is very convenient to have this single assignment and its declaration at the same place. ...
    (freebsd-hackers)
  • Re: What exactly does the SAVE statement do ?
    ... the subroutine declaration, and that made me going crazy, because I ... like an assignment statement, it isn't one. ... is an initialization. ...
    (comp.lang.fortran)
  • Re: JavaScript global object
    ... Variables should always be declared using a var statement. ... When control enters an execution context for eval code, ... However, because the function declaration is evaluated using eval, it doesn't exist until execution of that function call. ... The variable, TestEval2, does not exist anywhere within the scope chain of the EvalCode function, therefore assignment will proceed by creating a new global variable, and assigning to it a reference to the new function object. ...
    (comp.lang.javascript)