linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Chris Plasun <chrispl78@yahoo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Trouble using with Kegel cross tool chain
Date: Thu, 07 May 2009 14:50:11 +1000	[thread overview]
Message-ID: <17589.1241671811@neuling.org> (raw)
In-Reply-To: <407093.53240.qm@web58102.mail.re3.yahoo.com>



In message <407093.53240.qm@web58102.mail.re3.yahoo.com> you wrote:
> 
> Hi,
> 
> I'm getting a bit desperate trying to build a  gcc / glibc cross-toolchainfor
 
> use on a Freescale MPC8313 but am having problems.
> 
> I follow the Quick Start instructions at 
> http://www.kegel.com/crosstool/crosstool-0.43/doc/crosstool-howto.html and 
> run demo-powerpc-603.sh (is that the correct script for the MPC8313?)
> 
> I check the /opt/crosstool directory and there is nothing there.
> 
> Below are the results of running the above script:
> 
> =================
>  
> linux-66oa:~/work/crosstool-0.43 # sh demo-powerpc-603.sh 
> + TARBALLS_DIR=/root/downloads
> + RESULT_TOP=/opt/crosstool
> + export TARBALLS_DIR RESULT_TOP
> + GCC_LANGUAGES=c,c++
> + export GCC_LANGUAGES
> + mkdir -p /opt/crosstool
> ++ cat powerpc-603.dat gcc-4.1.0-glibc-2.3.6-tls.dat
> +
> eval TARGET=powerpc-603-linux-gnu 'TARGET_CFLAGS="-O' '-mcpu=603"'
> 'GCC_EXTRA_CONFIG="--with-cpu=603' '--enable-cxx-flags=-mcpu=603"'
> BINUTILS_DIR=binutils-2.16.1 GCC_CORE_DIR=gcc-3.3.6 GCC_DIR=gcc-4.1.0
> GLIBC_DIR=glibc-2.3.6 LINUX_DIR=linux-2.6.15.4 LINUX_SANITIZED_HEADER_DIR=lin
ux-libc-headers-2.6.12.0
> GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.6 GDB_DIR=gdb-6.5
> 'GLIBC_EXTRA_CONFIG="$GLIBC_EXTRA_CONFIG' --with-tls --with-__thread
> '--enable-kernel=2.4.18"' sh all.sh --notest
> ++ TARGET=powerpc-603-linux-gnu
> ++ TARGET_CFLAGS='-O -mcpu=603'
> ++ GCC_EXTRA_CONFIG='--with-cpu=603 --enable-cxx-flags=-mcpu=603'
> ++ BINUTILS_DIR=binutils-2.16.1
> ++ GCC_CORE_DIR=gcc-3.3.6
> ++ GCC_DIR=gcc-4.1.0
> ++ GLIBC_DIR=glibc-2.3.6
> ++ LINUX_DIR=linux-2.6.15.4
> ++ LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0
> ++ GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.6
> ++ GDB_DIR=gdb-6.5
> ++ GLIBC_EXTRA_CONFIG=' --with-tls --with-__thread --enable-kernel=2.4.18'
> ++ sh all.sh --notest
> You set both LINUX_DIR and LINUX_SANITIZED_HEADER_DIR - ignoring LINUX_DIR fo
r the build
> DEJAGNU not set, so not running any regression tests
> GLIBC_ADDON_OPTIONS not set, so building all glibc add-on's
> KERNELCONFIG not set, so not configuring linux kernel
> + TOOLCOMBO=gcc-4.1.0-glibc-2.3.6
> ++ pwd
> + BUILD_DIR=/root/work/crosstool-0.43/build/powerpc-603-linux-gnu/gcc-4.1.0-g
libc-2.3.6
> ++ pwd
> + TOP_DIR=/root/work/crosstool-0.43
> + test -z ''
> + SRC_DIR=/root/work/crosstool-0.43/build/powerpc-603-linux-gnu/gcc-4.1.0-gli
bc-2.3.6
> + echo 'SRC_DIR not set, so source tarballs will be unpacked in the build dir
ectory'
> SRC_DIR not set, so source tarballs will be unpacked in the build directory
> + case x$PREFIX in
> + case x$USER in
> + abort 'Don'\''t run all.sh or crosstool.sh as root, it'\''s dangerous'
> + echo 'Don'\''t' run all.sh or crosstool.sh as root, 'it'\''s' dangerous
> Don't run all.sh or crosstool.sh as root, it's dangerous
> + exec false

Are you running as root?  If so, don't.

Mikey

> 
> =================
> 
> The point of this exercise is to build a compiler to build Mono so that
> I can run .NET programs on the MPC8313.
> 
> I would really appreciate any help.
> 
> Thanks,
> Chris Plasun
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 

  reply	other threads:[~2009-05-07  4:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  2:50 Trouble using with Kegel cross tool chain Chris Plasun
2009-05-07  4:50 ` Michael Neuling [this message]
2009-05-07  5:32 ` Wolfgang Denk
2009-05-07  6:07 ` Chris Plasun
  -- strict thread matches above, loose matches on Subject: below --
2009-05-07 22:12 Chris Plasun
2009-05-07 22:19 Chris Plasun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17589.1241671811@neuling.org \
    --to=mikey@neuling.org \
    --cc=chrispl78@yahoo.com \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).