[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[openrisc] binutils, gcc and Linux on the OpenRISC [repost]



Hello again.

I had a few hours free, so I tried compiling binutils and gcc of or32-linux 
(which is actually or32-unknown-linux-gnu).

I had a few problems with binutils, but after changing the various 
configuration files (most changing or32-*-*linux to or32-*-*linux* or 
or32-*-*linux-gnu*) I managed to get all of binutils compiled.

Q1: should I get an account to commit these (small) changes?

After they where sucessfully installed, I tryed to compile gcc.  I didn't 
have much luck.

For target=or32-linux I get:

  /home/lee/newfolder/openrisc/b-gcc/gcc/xgcc 
-B/home/lee/newfolder/openrisc/b-gcc/gcc/ -B/opt/or32-linux/or32-linux/bin/ 
-I/opt/or32-linux/or32-linux/include -O2  -DCROSS_COMPILE -DIN_GCC     -g -O2 
-I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc  -I. 
-I../../gcc/gcc -I../../gcc/gcc/config -I../../gcc/gcc/../include -c 
-DL${name} \
       ../../gcc/gcc/libgcc2.c -o ${name}.o; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  or32-linux-ar rc tmplibgcc2.a ${name}.o; \
  rm -f ${name}.o; \
done
_muldi3
/home/lee/tmp/cck0wGSd.s: Assembler messages:
/home/lee/tmp/cck0wGSd.s:6: Error: unknown pseudo-op: `.def'
/home/lee/tmp/cck0wGSd.s:7: Error: unknown pseudo-op: `.scl'
/home/lee/tmp/cck0wGSd.s:8: Error: unrecognized symbol type ""
/home/lee/tmp/cck0wGSd.s:8: Warning: rest of line ignored; first ignored 
character is `0'
/home/lee/tmp/cck0wGSd.s:9: Error: expected comma after name `' in .size 
directive
/home/lee/tmp/cck0wGSd.s:9: Warning: rest of line ignored; first ignored 
character is `4'
/home/lee/tmp/cck0wGSd.s:10: Error: unknown pseudo-op: `.endef'
/home/lee/tmp/cck0wGSd.s:11: Error: unknown pseudo-op: `.def'
/home/lee/tmp/cck0wGSd.s:12: Error: unknown pseudo-op: `.val'
/home/lee/tmp/cck0wGSd.s:13: Error: unknown pseudo-op: `.scl'
/home/lee/tmp/cck0wGSd.s:14: Error: unrecognized symbol type ""
/home/lee/tmp/cck0wGSd.s:14: Warning: rest of line ignored; first ignored 
character is `0'

quite a few times.



If I try with target=or32-elf I get:

  /home/lee/newfolder/openrisc/b-gcc/gcc/xgcc 
-B/home/lee/newfolder/openrisc/b-gcc/gcc/ -B/opt/or32-linux/or32-elf/bin/ 
-I/opt/or32-linux/or32-elf/include -O2
-DCROSS_COMPILE -DIN_GCC     -g -O2 -I./include   -g1 -DHAVE_GTHR_DEFAULT 
-DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc  -I. -I../../gcc/gcc 
-I../../gcc/gcc/config -I../../gcc/gcc/../include -c -DL${name} libgcc1.S; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  mv libgcc1.o ${name}.o; \
  or32-elf-ar rc tmplibgcc1.a ${name}.o; \
  rm -f ${name}.o; \
done
__udivsi3
/home/lee/tmp/ccKU3hzO.s: Assembler messages:
/home/lee/tmp/ccKU3hzO.s:5: Error: invalid character '.' in mnemonic
/home/lee/tmp/ccKU3hzO.s:6: Error: invalid character '.' in mnemonic

<about 150 of those>


Q2: Do I need to port gcc to or32-*-linux-gnu ?

I guess I am going to need all these to start porting Linux to the OpenRISC.

Q3: Are there any documents about the whole system, processor, bus, memory, 
everything?

Q4: Are there any documents about the boot process?

Q5: Anything else I should know before I start porting a week today?

Q6: Is there a documents describing how to use the simulator?

I have been reading the documents and they are really useful.  There are a 
few little errors and one or two omission which I will send an email about 
later.

I look forward to starting shortly.

Later
Lee Begg

--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml