C/Assembler question
I seem to be having problems with the compiler in getting a c/assembly listing. I have tried a couple sets of the tools and seem to be getting the same error with both sets. Is my syntax correct on the line below? Its the -Wa,-a=pc_keyb.lst that seems to cause the problem.
mips-linux-gcc -D__KERNEL__ -I/home/jharrell/work/mips_linux/include -g -Wa,-a=pc_keyb.lst -Wall -Wstrict-prototypes -Wa,-a -O2 -fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips3
-pipe -c -o pc_keyb.o pc_keyb.c
This is the error that I get when I attempt it:
pc_keyb.c: In function `kb_wait':
pc_keyb.c:103: warning: unused variable `status' {standard input}: Assembler messages:
{standard input}:565: Fatal error: Symbol kb_wait already defined.
Is there a formatting problem with this command? Any help would be greatly appreciated.
Thanks,
Jeff
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jeff Harrell Work: (801) 619-6104
Broadband Access group/TI
[email protected]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Quoted 14 lines · Jeff Harrell
I seem to be having problems with the compiler in getting a c/assembly listing. I have tried a couple sets of the tools and seem to be getting the same error with both sets. Is my syntax correct on the line below? Its the -Wa,-a=pc_keyb.lst that seems to cause the problem.
mips-linux-gcc -D__KERNEL__ -I/home/jharrell/work/mips_linux/include -g
(quoted diff) +0
-3-Wa,-a=pc_keyb.lst -Wall -Wstrict-prototypes -Wa,-a -O2 -fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips3 -pipe -c -o pc_keyb.o pc_keyb.cThis is the error that I get when I attempt it:
Quoted 8 lines
pc_keyb.c: In function `kb_wait':
pc_keyb.c:103: warning: unused variable `status' {standard input}: Assembler messages:
{standard input}:565: Fatal error: Symbolkb_waitalready defined.Is there a formatting problem with this command? Any help would be greatly appreciated.
This is weird. You pass an extra option to the assembler and the compiler begins to spit errors? Try adding -v as well and check gcc actually passes down to cpp / cc1 / as, maybe that explains things.
Ralf