[linux-sh:03315] Re: Building a cross compiler for the Dreamcast
Dan Kegel <[email protected]> Sun, 19 Sep 2004 17:14:26 -0700
| Newsgroups | gmane.linux.ports.sh.general |
|---|---|
| Message-ID | <[email protected]> |
Gregg C Levine wrote: > 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. Which script was that? Note that the recommended way to run for starters is sh demo-sh4.sh > 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 That's exactly what you would expect if you ran all.sh or crosstool.sh without setting those variables. > I did read the documentation pointed to inside the > doc directory that the README file points to. Evidently the doc sucks. If I can figure out how, I'll improve it. > Also I'd like to have the crosstool scripts build Slackware packages. Can't help you there. I don't know what those are. Aren't they just tarballs? > 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. Er, that's not the output from the script, that's the script itself. Are you quite sure you ran it? - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change