Re: [openrisc] Another Newbie, OpenRISC, Or1ksim and Linux

["Marko Mlinar" <markom@opencores.org>]

"the clock-skew is detected and the build may be incomplete" is displayed if
the source files are newer than your system clock -- maybe you should run
touch;
but this warning usually means nothing.
--target=xxx      specifies target package will be build for.
Generally you should use or32-rtems, but with or1ksim you can write just
or32, since it require just cpu part from target tripple: cpu-[[vendor-]os]

run ./configure --help or find more information about targets in
manuals for automake, autoconf, etc. (e.g. info automake)

Marko

> Please tell me what's wrong with this. Also, I am confused with the
> argument "--target=xxxxx" for the "./configure" command since different
> places have different says, e.g., the README file under or1ksim uses "--
> target=or32-rtems", and somewhere else says "--target=or32". Is there
> any difference between them?
>
> ----- Original Message -----
> From: "Marko Mlinar" <markom@o... >
> To: <openrisc@o... >
> Date: Thu, 7 Mar 2002 08:30:52 +0100
> Subject: Re: [openrisc] Newbie, OpenRISC, Or1ksim and Linux
>
> >
> >
> > > Cool.  It runs well now.
> > great.
> >
> > > > > I also metioned Linux in the topic.  I saw the Linux
> > port on the
> > website
> > > >
> > > > and
> > > >
> > > > > thought that it would be a cool think to help out
> > on.
> > > > >
> > > > > Is there anything I can help with?
> > > >
> > > > Actually we have uCLinux, which is very similar. It is
> > now running
> > > > Microwindows
> > > > and if you can play tetris or minesweeper on the or1ksim
> > :)
> > >
> > > Hehe, cool.  I'll have a look at uCLinux tomorrow.  How
> > similar is it to
> > > linux?
> > actually it is quite the same, except it does not have mmu and is a
> > bit
> > smaller.
> > When building microwindows and compiler toolchain, you the
> > instructions
> > below
> > might be helpful. They are preliminary and not yet tested. We will
> > test it
> > and
> > publish it to the website soon.
> > Microwindows can be downloaded, using cvs -z9 co or1k/mw. And
> maybe
> > you
> > will need to update config file there also.
> >
> > good luck,
> > Marko
> >
> > ************ instructions how to build uclinux & uclibc
> > toolchain *********
> > mkdir /tmp/tools
> > cd /tmp/tools
> > mkdir or32-uclinux
> > export PATH=/tmp/tools/or32-uclinux/bin:$PATH
> >
> > #
> > # Binutils:
> > #
> >
> > cvs -z9 co or1k/binutils
> > cd or1k
> > mkdir binutils-ucl
> > cd binutils-ucl
> > ../binutils/configure --target=or32-uclinux
> > --prefix=/tmp/tools/or32-uclinux
> > make all install
> > cd ../../
> >
> > #
> > # Gcc
> > #
> >
> > cvs -z9 co or1k/gcc-3.1
> > cd or1k
> > mkdir gcc-ucl
> > cd gcc-ucl
> > ../gcc-3.1/configure --target=or32-uclinux
> > --prefix=/tmp/tools/or32-uclinux/
> >  --local-prefix=/tmp/tools/or32-uclinux/or32-uclinux/ --with-gnu-as
> > --with-g
> > nu-ld --verbose --enable-languages=c
> > make all install
> > cd ../../
> >
> > #
> > # uClinux
> > #
> >
> > cvs -z9 co or1k/uclinux
> > cd or1k/uclinux/uClinux-2.0.x/
> > make oldconfig
> > make dep
> > make
> > cd ../../../
> >
> > #
> > # uClibc
> > #
> >
> > cvs -z9 co or1k/uclibc
> > cd or1k/uclibc
> > # Edit Config file:
> > #   TARGET_ARCH=or32
> > #   CROSS = $(TARGET_ARCH)-uclinux-
> > #   KERNEL_SOURCE=/tmp/tools/or1k/uclinux/uClinux-2.0.x/
> > #   DEVEL_PREFIX = /tmp/tools/$(TARGET_ARCH)-uclinux
> > make all install
> > cd ../../or32-uclinux/bin
> > rm -f addr2line ar as cc cpp gasp gcc ld nm objcopy objdump ranlib
> > size
> > strings strip jar grepjar
> > cd ..
> >
> > #
> > # Rebuild Gcc
> > #
> > cd or1k/gcc-ucl
> > ../gcc-3.1/configure --target=or32-uclinux
> > --prefix=/tmp/tools/or32-uclinux/
> >  --local-prefix=/tmp/tools/or32-uclinux/or32-uclinux/ --with-gnu-as
> > --with-g
> > nu-ld --verbose --enable-languages=c
> > make all install
> > cd ../../
> >
> > #
> > # Sash
> > #
> > cd or1k/uclinux/userland/sash
> > make
> >
> > #
> > # Generating ramdisk image
> > #
> > mkdir romfs
> > mkdir romfs/bin
> > cp  or1k/uclinux/userland/sash/sh romfs/bin/sash
> > chmod 777 romfs/bin/sash
> > mkdir romfs/dev
> > cd romfs/dev
> > mknod ram0 1 0
> > mknod tty 4 0
> > mknod tty1 4 1
> > mknod ttyS0 4 64
> > cd ..
> > genromfs -f ../or1k/uclinux/uClinux-2.0.x/arch/or32/board/initrd
> > cd ..
> >
> > #
> > # Rebuilding uClinux
> > #
> > cd or1k/uclinux/uClinux-2.0.x/
> > make
> > cd ../../../
> >
> --
> To unsubscribe from openrisc mailing list please visit
http://www.opencores.org/mailinglists.shtml
>

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