|
Message
From: ThamNabble<hamiltn1@h...>
Date: Wed Jan 23 23:28:51 CET 2008
Subject: [openrisc] DHRYSTONE and or32-elf-gcc
Try this:
CC=or32-elf-gcc sh dhry.c
--
I learned today that dhry.c is a script that knows how to compile itself and
then run.. sending output to the console etc.
-T
Dimitrios Orfanos wrote:
>
> Hi to everyone,
>
> I am trying to compile the dhrystone that is included in the or1ksim0.2.0
> using the or32-elf-gcc with newlib support. And I receive some bad
> messages,
> please help, if you can:
>
> ""
> I give the command:
> or32-elf-gcc -Isupport -o dhry dhry.c ../../exit.s
>
> and I receive the message:
> /tmp/ccAfEj5g.o: In function `_main':
> dhry.c:(.text+0x420): undefined reference to `_start_timer'
> dhry.c:(.text+0x42c): undefined reference to `_read_timer'
> dhry.c:(.text+0x46c): undefined reference to `_report'
> dhry.c:(.text+0x480): undefined reference to `_report'
> dhry.c:(.text+0x494): undefined reference to `_report'
> dhry.c:(.text+0x4a8): undefined reference to `_report'
> dhry.c:(.text+0x504): undefined reference to `_report'
> /tmp/ccAfEj5g.o:dhry.c:(.text+0x520): more undefined references to
> `_report'
> follow
> /tmp/ccAfEj5g.o: In function `_main':
> dhry.c:(.text+0x918): undefined reference to `_read_timer'
> dhry.c:(.text+0xbfc): undefined reference to `_report'
> /tmp/ccAfEj5g.o: In function `_Proc_1':
> dhry.c:(.text+0xc68): undefined reference to `_report'
> dhry.c:(.text+0xe4c): undefined reference to `_report'
> dhry.c:(.text+0xedc): undefined reference to `_report'
> dhry.c:(.text+0x10ac): undefined reference to `_report'
> /tmp/ccAfEj5g.o:dhry.c:(.text+0x10f0): more undefined references to
> `_report'
> follow
> collect2: ld returned 1 exit status
>
> DO
> _______________________________________________
> http://www.opencores.org/mailman/listinfo/openrisc
>
>
--
View this message in context: http://www.nabble.com/DHRYSTONE-and-or32-elf-gcc-tp14859541p15054265.html
Sent from the OpenCores - RISC mailing list archive at Nabble.com.
|
 |
Browse
