OPENCORES.ORG

From: rich_daddio at yahoo.com<rich_daddio@y...>
Date: Wed Jul 30 01:05:23 CEST 2008
Subject: [openrisc] building command log

Hi Jeremy, Hi Chen-Wei,

Chen-Wei it looks to me like your Linux kernel built fine. Since the Linux kernel does not require a C Library to build, this is to be expected. You can actually use this image as is, since the ramdisk you copied rgd_initrd-fb-03.ext2 contains enough userland code for you to get started. This might be enough if hardware is your focus. In order to use your toolchain to build userland(non-kernel) applications you need to build the C lib which in this case is uClibc. You can use the sample ".config" at MOF directly(download/save link as, remove html tags <br>, and copy to top of uClinux directory as .config) but you will have to change some of the paths to something like this (which you can edit directly): KERNEL_SOURCE=/path-to-your-linux/linux-2.6.19 DEVEL_PREFIX=/opt/or32/or32-uclinux (I am guessing that this is correct) Or you can do a "make config" from the uClibc top directory and model your own .config like the one at MOF by selecting/deselecting the same features (this is tedious I know). Either way after you "make install" make sure you follow the Embecosm directions or something like: http://www.meansoffreedom.com/opencores_build4.html to make sure your toolchain can find the c lib correctly. With your gdb build could you make sure you don't have any left over environment variables set from previous attempts. You could also try the GDB versions posted up at: http://www.opencores.org/projects.cgi/web/or1k/gnu_toolchain_port_old to see if the old stuff builds but these will not have Jeremy's excellent updates and fixes. HTH, Rich d ----- Original Message ----- From: Chen Wei Hsu<cwhsu1984@g...> To: Date: Tue Jul 29 17:22:48 CEST 2008 Subject: [openrisc] building command log > Hi Jeremy, > > I have deleted all the files that I compiled last time. The logs > you're > reading now are all brand new start! > //linux environment > // Linux angels 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 > x86_64 > x86_64 //x86_64 GNU/Linux > //--------------------------------------------installation of > binutils > tar xjvf binutils-2.16.1.tar.bz2 > // I didn't use "bunzip2 binutils-2.16.1.tar.bz2" because > this command > didn't unzip the file > // into a directory. Instead, it simply unzip the file into > binutils-2.16.1.tar. I will have to untar it > // again so I use tar xjvf directly. > cd binutils-2.16.1 > bzcat -dc ../binutils_2.16.1_unified.diff_rgd_fixed.bz2 | patch -p1 > // mkdir buildir_binutils <- I thought it should be "mkdir > builddir_binutils" to be consistency > mkdir builddir_binutils > cd builddir_binutils > ../binutils-2.16.1/configure --target=or32-uclinux > --prefix=$HOME/tools/or32 > make all > make install > setenv PATH $HOME/tools/or32/bin:$PATH > //since we use .tcshrc to set environment variable, I assume that > we use > tcsh! > //----------------------------------------------------end of > binutils > //----------------------------------------------------installation > of gcc > tar xjvf gcc-3.4.4.tar.bz2 > cd gcc-3.4.4 > bzcat -dc ../gcc-3.4.4-or32-unified.diff.bz2 | patch -p1 > mkdir builddir-gcc > cd builddir-gcc > ../gcc-3.4.4/configure --target=or32-uclinux > --prefix=$HOME/tools/or32 > --enable-languages=c > make all > make install > //----------------------------------------------------end of gcc > //---------------------------------------------------installation > of gdb > tar xzf gdb-5.3.tar.gz > cd gdb-5.3 > bzcat -dc ../embecosm-or32-gdb-5.3-patch.bz2 | patch -p1 > mkdir builddir-gdb > cd builddir-gdb > ../gdb-5.3/configure --target=or32-uclinux > make all > // I got the error messages which I told you before > // make[1]: *** [or1k-tdep.o] Error 1 > // make[1]: Leaving directory > `/home/users2007/cwhsu/iss/builddir-gdb/gdb' > // make: *** [all-gdb] Error 2 > //--------------------------------------------------------stop at > this step > > //---------------------------------------------------------installation > of > linux kernel > tar xjvf linux-2.6.19.tar.bz2 > cd linux-2.6.19 > bzcat -dc ../linux_2.6.19_or32_unified_simtested.bz2 | patch -p1 > bzcat -dc ../embecosm-or32-linux-2.6.19-general-patch.bz2 | patch > -p1 > cp rgd_dot_config .config > make menuconfig ARCH=or32 CROSS_COMPILE=/opt/or32/bin/or32-uclinux- > //configure the setting of core > bunzip2 rgd_initrd-fb-03.ext2.bz2 > cp rgd_initrd-fb-03.ext2 > ./linux-2.6.19/arch/or32/support/initrd-fb-03.ext2 > make vmlinux ARCH=or32 CROSS_COMPILE=/opt/or32/bin/or32-uclinux- > //I got some warnings, but I did successfully compile it without > errors this > time! > //--------------------------------------------------------end of > linux > kernel > > //--------------------------------------------------------installation > of > uClibc > tar xjvf uClibc-0.9.28.3.tar.bz2 > cd uClibc-0.9.28.3 > bzcat -dc ../uClibc-0.9.28-or32-unified.bz2 | patch -p1 > cd libc > bzcat -dc ../../uClibc-0.9.28-or32-libc-support.bz2 | patch -p1 > cd .. > bzcat -dc ../embecosm-or32-uClibc-0.9.28.3-stdio-patch.bz2 | patch > -p1 > ln -s extra/Configs/Config.or32 Config > //---------------------------------------------------------stop > here > // cause I don't understand the document again... > 3.5.2. Configuring uClibc > ... > ... > The MOF website provides a template suggested configuration file. > Copy this > into .config. > Which file should I copy into .config? Is this .config file at the > top directory of the uClibc or other directory? Also, here is my > .config and my gcc-v which you ask for last time. > attachment-0001.htm attachment-0001.htm Thank you for all the > support! Best Regards, Chen-Wei -------------- next part > -------------- An HTML attachment was scrubbed... URL: > attachment-0001.htm >