Hi, Marko
I really thank you.
I downloaded or1ksim from CVS again.
But, the symptom is the same to previous one.
It was built and installed without any error, but the testbench can't pass the configuration stage.
I know that the issue related to compiler and testbench of or1ksim is revival.
(The issue titled Re:Re:[openrisc] or32 compiler errors)
I tried severals suggested by Damjan and Marko.
But, unfortunately, I still can't make a simple file to be compiled.
As pointed by Damjan and Marko, I built crt0.o and put it in "/opt/or32-uclinux/or32-uclinux/lib".
After that I compiled two files manually. hereunder error messages generated by compiler:
##########################################################################
[vmlinux:/home/maunal/WORK/or1k/or1ksim/testbench] or32-uclinux-gcc basic.s -o basic
basic.s: Assembler messages:
basic.s:31: Error: too many operands: (0)
basic.s:31: Error: invalid operands
basic.s:37: Error: too many operands: (0)
basic.s:37: Error: invalid operands
basic.s:51: Error: too many operands: (1)
basic.s:51: Error: invalid operands
basic.s:56: Error: too many operands: (1)
basic.s:56: Error: invalid operands
[vmlinux:/home/maunal/WORK/or1k/or1ksim/testbench] or32-uclinux-gcc exit.c -o exit
/opt/or32-uclinux/lib/gcc-lib/or32-uclinux/3.1/../../../../or32-uclinux/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
###########################################################################
What does the messages mean?
(The first one seems that assmbler can't handle instructions just like l.addi, r1, r1, MC_CRC(0)...)
Now, I suspect my system, RedHat7.3 (I tried the same work in RedHat7.2 also).
Is there anyone who succeeded in building and testing compiler(or32-uclinux) system in RedHat 7.3(or RedHat7.2)?
If Gil Gamliel see this message, could you tell me the status of your compiler system?
Regards,
maunal
Marko Mlinar
On Wednesday 04 September 2002 08:44, Marko Mlinar wrote:
> On Wednesday 04 September 2002 05:34, maunal moren wrote:
> > Hi, Marko
> > $ make distclean
> > $ ./configure --target=or32-uclinux
> > Where the commands are executed? At "/or1ksim" or "/or1ksim/testbench"?
> > 1. At "/or1ksim",
> > "make distclean" was stopped reporting it can't find config.h
> > It seems there is a bug (?) in Makefile.in. Target distclean-hdr removes
> > config.h. So, I commented out the line "rm -f config.h", and make
> > distclean was executed without error message. After that, I executed
> > "make all install".
> > But, nothing has been changed when "./configure --target=or32-uclinux"
> > was executed at "/or1ksim/testbench". It was stopped reporting error
> > message. 2. At "/or1ksim/testbench"
> > "make distclean" was stopped reporting "no rule to make target
> > 'distclean'". What can I do next?
>
> The problem is that your configure has or32-uclibc-gcc cached. Apparrently
> you configured many times (without distclean) in the source dir, which
> usually causes dead end position.
> So you are stuck without Makefile to make "make distclean" for you and
> configure doesn't pass because it has or32-uclibc-gcc cached.
>
> Try deleting config.cache file and configure with:
> ./configure --target=or32-uclinux
>
> again (in "testbench" dir).
>
> Marko
oh, yes, and if that doesn't work, you will have to download new copy from CVS
and build according to instructions on the web. I just built it, and it builds
ok for me.
Marko
--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml