On May 29, 2009, at 9:06 AM, ext Ju-sung.Lee wrote:
Anyone seen this failure mode before?
scratchbox 2
Target : Qemu-mipsel
toolchain : mipsel-linux-gcc
GLIB : glib-2.16.3
*$ sb2-init -c "qemu-mipsel" mipsel-target mipsel-linux-gcc*
I'm attempting to build glib on Mipsel. During the Configuration
stage,
the script freezes after printing "I can't find the libraries for
the thread implementation".
so I had to add --disable-threads. and Configuration stage was
success.
But During the make stage. the script freezes after printing ..
/tmp/ccLW3AjP.s: Assembler messages:
/tmp/ccLW3AjP.s:29: Error: unrecognized opcode `lock'
/tmp/ccLW3AjP.s:29: Error: unrecognized opcode `xaddl $2,0($4)'
/tmp/ccLW3AjP.s:51: Error: unrecognized opcode `lock'
/tmp/ccLW3AjP.s:51: Error: unrecognized opcode `addl $5,0($4)'
/tmp/ccLW3AjP.s:73: Error: unrecognized opcode `lock'
/tmp/ccLW3AjP.s:73: Error: unrecognized opcode `cmpxchgl $6,0($4)'
/tmp/ccLW3AjP.s:104: Error: unrecognized opcode `lock'
/tmp/ccLW3AjP.s:104: Error: unrecognized opcode `cmpxchgl $6,0($4)'
This looks very much like x86 assembler and might explain why mips-
linux-as cannot handle it correctly. I guess that some of the
"atomic" operation macros inside glib are expanded into wrong
architecture or something like that.
I don't know what this scripts mean. Is this qemu configuration
problem?
Doesn't seem to be qemu problem.
MW
_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
