[linux-sh:03314] Re: Building a cross compiler for the Dreamcast

Hello from Gregg C Levine
Actually yes I did. And something within the scripts didn't appreciate my
efforts. I posted my efforts to the newgroup. In case you didn't see it
there, I've got a local copy:
>>>>>>>>>>>>
Hello from Gregg C Levine
I did that. I used the default browser for KDE to download that one. Tar
complained so I grabbed it via wget. Extracted it into the /usr/local/src
directory.

I then ran the script for setting things for the SH4. I should have
mentioned, that my
target isn't one of the developer boards from the company, its a Dreamcast
that's
my target.

I then ran the next script, it complained about not having a couple of
variables set.
Same with the crosstool.sh script. I also created a script file to explain
this:
Script started on Thu 16 Sep 2004 12:21:11 AM EDT
root@who4:/usr/local/src/crosstool-0.28-rc35# sh all.sh
Please set TARGET to the Gnu target identifier (e.g. pentium-linux)
root@who4:/usr/local/src/crosstool-0.28-rc35# sh crosstool.sh
Please set PREFIX to where you want the toolchain installed.
root@who4:/usr/local/src/crosstool-0.28-rc35# exit
Script done on Thu 16 Sep 2004 12:23:17 AM EDT

I am some what confused. I did read the documentation pointed to inside the
doc
directory that the README file points to. Also I'd like to have the
crosstool
scripts build Slackware packages. I'm also going to post the output from the
demo-sh4.sh script:
#!/bin/sh
set -ex
TARBALLS_DIR=/usr/local/src/sh4
RESULT_TOP=/opt/crosstool
export TARBALLS_DIR RESULT_TOP
GCC_LANGUAGES="c,c++"
export GCC_LANGUAGES

# Really, you should do the mkdir before running this,
# and chown /opt/crosstool to yourself so you don't need to run as root.
mkdir -p $RESULT_TOP

# Build the toolchain.  Takes a couple hours and a couple gigabytes.
# note: binutils < 2.13 doesn't know about sh4, so don't try building
gcc-2.95
# note: gcc-3.2.3 has ICE compiling glibc for sh4
(http://gcc.gnu.org/PR6954), so
don't try building gcc-3.2.3

#eval `cat sh4.dat gcc-3.3-glibc-2.2.5.dat`    sh all.sh --notest
#eval `cat sh4.dat gcc-3.3-glibc-2.3.2.dat`    sh all.sh --notest
#eval `cat sh4.dat gcc-3.3.2-glibc-2.3.2.dat`  sh all.sh --notest
#eval `cat sh4.dat gcc-3.3.3-glibc-2.3.2.dat`  sh all.sh --notest
#eval `cat sh4.dat gcc-3.4.0-glibc-2.3.2.dat`  sh all.sh --notest
 eval `cat sh4.dat gcc-3.4.1-glibc-2.3.3.dat`  sh all.sh --notest
#eval `cat sh4.dat gcc-3.4.1-glibc-20040827.dat`  sh all.sh --notest

echo Done.
I examined the configuration files for the SH4, and I noticed that its set
for the
generic processor. Would that make a difference?
---
Gregg C Levine drwho8 atsign att dot net
--
PS- Nice website discussing your work.
>>>>>>>>
I just don't know what's wrong there.
Gregg C Levine  drwho8 atsign att dot net
"Oh my!" The Second Doctor's nearly favorite phrase.

----- Original Message ----- 
From: "Dan Kegel" <[email protected]>
To: "Gregg C Levine" <[email protected]>
Cc: <[email protected]>; <[email protected]>
Sent: Sunday, September 19, 2004 1:57 PM
Subject: [linux-sh:03313] Re: Building a cross compiler for the Dreamcast


> Gregg C Levine wrote:
> > Hello from Gregg C Levine
> > Apologies for the duel posted message, but I don't know how many of both
> > groups subscribe to both.
> > I seem to be having the programming equivalent of Writers Block. I can
not
> > seem to be able to build a working cross compiler for Dreamcast, and its
SH4
> > processor. This would be based on the GCC 3.3,4 sources. That version
was
> > chosen because that's the version supplied with my Slackware 10.0
> > installation media. The binary utilities would be at version 2.15.90.03,
for
> > the same reasons.
> >
> > Is anyone on the two lists reasonably familiar with how Slackware builds
its
> > packages to suggest a set of scripts? Naturally this would include an
> > appropriate libary as well.
>
> Do you want to run Linux on your Dreamcast?  If so, have you tried
> http://kegel.com/crosstool yet?
> - Dan
>
> -- 
> My technical stuff: http://kegel.com
> My politics: see http://www.misleader.org for examples of why I'm for
regime change
>