Re: [openrisc] Running ORPsoc simulator

[Marko Mlinar <markom@opencores.org>]

Robert,

I cannot remember what is wrong, how it should be linked, if you want to use 
-c and -o options.
Try looking at mailing list archive, there have been already a lot of 
discussion on this subject.

Marko


On Tuesday 11 February 2003 13:06, Robert Cragie wrote:
> Hi Marko,
>
> > You need or32-uclibc-gcc (not or32-uclinux-gcc) to build uclinux
> > programs. uclibc's "make install" should prepare it.
> >
> > Marko
>
> I realised I had made a mistake originally - I did not specify the path in
> uclibc Config file correctly. However, I rebuilt with the corrected file
> and now I see all the or32-uclibc-xxx files in /opt/or32-uclinux/bin. All
> are symlinks except for or32-uclibc-gcc and or32-uclibc-ld, which is what I
> would expect.
>
> However I still get the crt0.o linkage problem. I added -v to the command
> line in Makefile and got this:
>
> or32-uclibc-gcc  -r -d -v simpleinit.o -o init
> Invoked as or32-uclibc-gcc
> arg[ 0] = /opt/or32-uclinux/bin/or32-uclinux-gcc
> arg[ 1] = -r
> arg[ 2] = -d
> arg[ 3] = -v
> arg[ 4] = simpleinit.o
> arg[ 5] = -o
> arg[ 6] = init
> arg[ 7] = -nostdinc
> arg[ 8] = -I/opt/or32-uclinux/include/
> arg[ 9] = -I/opt/or32-uclinux/lib/gcc-lib/or32-uclinux/3.1/include
> Reading specs from /opt/or32-uclinux/lib/gcc-lib/or32-uclinux/3.1/specs
> Configured with:
> ../gcc-3.1/configure --target=or32-uclinux --prefix=/opt/or32-uclinux
> --loca l-prefix=/opt/or32-uclinux/or32-uclinux --with-gnu-as --with-gnu-ld
> --verbos e --enable-languages=c : (reconfigured)
> ../gcc-3.1/configure --target=or32-uclinux --prefix=/opt/or32-uclinux
> --loca l-prefix=/opt/or32-uclinux/or32-uclinux --with-gnu-as --with-gnu-ld
> --verbos e --enable-languages=c
> Thread model: single
> gcc version 3.1 20020121 (experimental)
>  /opt/or32-uclinux/lib/gcc-lib/or32-uclinux/3.1/collect2 -o init -d -r
> crt0.o -L/opt/or32-uclinux/lib/gcc-lib/or32-uclinux/3.1
> -L/opt/or32-uclinux/
> lib/gcc-lib/or32-uclinux/3.1/../../../../or32-uclinux/lib
> simpleinit.o -lgcc -lc -lgcc
> /opt/or32-uclinux/lib/gcc-lib/or32-uclinux/3.1/../../../../or32-uclinux/bin
>/ ld: cannot open crt0.o: No such file or directory
> collect2: ld returned 1 exit status
> make: *** [init] Error 1
>
> So why does it think it's running '/opt/or32-uclinux/bin/or32-uclinux-gcc'
> in argv[0]? And why is it specifying crt0.o in the 'collect2' command?
>
> Regarding ext2 or romfs file question yesterday, I thought a bit more about
> it and I assume that Linux can tell what sort of file system it is booting
> from the 'boot sector' or equivalent, thus either romfs or ext2 will do for
> initrd. Is this correct?
>
> Robert Cragie, Design Engineer
> _______________________________________________________________
> Jennic Ltd, Furnival Street, Sheffield, S1 4QT,  UK
> http://www.jennic.com  Tel: +44 (0) 114 281 2655
> _______________________________________________________________
> Visit our stand (C79) at DATE - Munich 4-6 March 2003
> _______________________________________________________________

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