linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Trouble using with Kegel cross tool chain
@ 2009-05-07  2:50 Chris Plasun
  2009-05-07  4:50 ` Michael Neuling
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Chris Plasun @ 2009-05-07  2:50 UTC (permalink / raw)
  To: linuxppc-dev


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=linux-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 for 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-glibc-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-glibc-2.3.6
+ echo 'SRC_DIR not set, so source tarballs will be unpacked in the build directory'
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

=================

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

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Trouble using with Kegel cross tool chain
@ 2009-05-07 22:12 Chris Plasun
  0 siblings, 0 replies; 6+ messages in thread
From: Chris Plasun @ 2009-05-07 22:12 UTC (permalink / raw)
  To: linuxppc-dev


> > + 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

Ah, now it's doing something...

Thanks Mikey. I didn't think running as root would prevent the process from running. Everything is running in VirtualBox so I wasn't concerned about blowing things up.

The build has been in progress for the past 15 minutes...

I set the target as powerpc-603. Is this appropriate for the MPC8313?

Thank you.

Chris Plasun

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Trouble using with Kegel cross tool chain
@ 2009-05-07 22:19 Chris Plasun
  0 siblings, 0 replies; 6+ messages in thread
From: Chris Plasun @ 2009-05-07 22:19 UTC (permalink / raw)
  To: linuxppc


Hi Wolfgang,

> Trouble using with Kegel cross tool chain
> Wolfgang Denk wd at denx.de
> Thu May 7 15:32:36 EST 2009
> 
>      * Previous message: Trouble using with Kegel cross tool chain
>      * Next message: Trouble using with Kegel cross tool chain
>      * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 
> Dear Chris,
> 
> In message <407093.53240.qm at web58102.mail.re3.yahoo.com> you wrote:
>  >
>  > I'm getting a bit desperate trying to build a  gcc / glibc 
> cross-toolchainfor
>  > use on a Freescale MPC8313 but am having problems.
> 
> Try using ELDK (see http://www.denx.de/wiki/view/DULG/ELDK resp.
> ftp://ftp.denx.de/pub/eldk/4.2/); it's based on crosstool but has
> these issues already solved for you.
> 
> Best regards,
> 
> Wolfgang Denk

Is Denx your site? I poured over it for U-Boot.

I will take a look at this tool.

Danke schoen!

Chris Plasun

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2009-05-07 22:19 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-07  2:50 Trouble using with Kegel cross tool chain Chris Plasun
2009-05-07  4:50 ` Michael Neuling
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

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).