From: Gregg C L. <dr...@wo...> - 2004-09-19 16:53:30
|
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. Gregg C Levine drwho8 atsign worlnet dot att dot net "Oh my!" The Second Doctor's nearly favorite phrase. |
From: Gregg C L. <dr...@wo...> - 2004-09-19 20:35:33
|
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" <da...@ke...> To: "Gregg C Levine" <dr...@wo...> Cc: <lin...@li...>; <lin...@m1...> 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 > |
From: Gregg C L. <dr...@wo...> - 2004-09-20 00:38:34
|
Hello from Gregg C Levine Hmm. What I posted there, was a copy & paste from that newgroup posting. Evidently I did forget to provide a script of what the script does. Here comes the actual script: Script started on Sun 19 Sep 2004 08:25:48 PM EDT root@who4:/usr/local/src/crosstool-0.28-rc36# sh demo-sh4.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 sh4.dat gcc-3.4.1-glibc-2.3.3.dat + eval 'KERNELCONFIG=`pwd`/sh4.config' TARGET=sh4-unknown-linux-gnu 'TARGET_CFLAGS="-O' -ml '-m4"' 'GLIBC_CONFIGPARMS="no-z-defs=yes"' BINUTILS_DIR=binutils-2.15 GCC_DIR=gcc-3.4.1 GLIBC_DIR=glibc-2.3.3 LINUX_DIR=linux-2.6.8 GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.3 sh all.sh --notest +++ pwd ++ KERNELCONFIG=/usr/local/src/crosstool-0.28-rc36/sh4.config ++ TARGET=sh4-unknown-linux-gnu ++ TARGET_CFLAGS=-O -ml -m4 ++ GLIBC_CONFIGPARMS=no-z-defs=yes ++ BINUTILS_DIR=binutils-2.15 ++ GCC_DIR=gcc-3.4.1 ++ GLIBC_DIR=glibc-2.3.3 ++ LINUX_DIR=linux-2.6.8 ++ GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.3 ++ sh all.sh --notest DEJAGNU not set, so not running any regression tests GCC_EXTRA_CONFIG not set, so not passing any extra options to gcc's configure script GLIBC_ADDON_OPTIONS not set, so building all glibc add-on's + TOOLCOMBO=gcc-3.4.1-glibc-2.3.3 ++ pwd + BUILD_DIR=/usr/local/src/crosstool-0.28-rc36/build/sh4-unknown-linux-gnu/gcc -3.4.1-glibc-2.3.3 ++ pwd + TOP_DIR=/usr/local/src/crosstool-0.28-rc36 + test -z '' + SRC_DIR=/usr/local/src/crosstool-0.28-rc36/build/sh4-unknown-linux-gnu/gcc-3 .4.1-glibc-2.3.3 + 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 + 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 root@who4:/usr/local/src/crosstool-0.28-rc36# exit Script done on Sun 19 Sep 2004 08:26:21 PM EDT I think that output clarifies my position. And your right. Packages for Slackware are indeed tarballs, except the makepkg tool adds a script which adds it to the records of what's installed on the system. Since your tool says it can make RPM packages, I can convert those to ny Slackware packages. What I'd really like is a few pointers suggesting where I should go next. Gregg C Levine drwho8 atsign worldnet dot att dot net "Oh my!" The Second Doctor's nearly favorite phrase. ----- Original Message ----- From: "Dan Kegel" <da...@ke...> To: "Gregg C Levine" <dr...@wo...> Cc: <lin...@li...>; <lin...@m1...> Sent: Sunday, September 19, 2004 8:14 PM Subject: Re: [linux-sh:03313] Re: Building a cross compiler for the Dreamcast > 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 |
From: Dan K. <da...@ke...> - 2004-09-20 03:30:37
|
Gregg C Levine wrote: > Hello from Gregg C Levine > Hmm. What I posted there, was a copy & paste from that newgroup posting. > Evidently I did forget to provide a script of what the script does. > > ... > + 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 > > I think that output clarifies my position. Right. Quick question: were you logged in as root when you ran that script? If so, which part of "Don't run all.sh or crosstool.sh as root, it's dangerous" don't you understand? I'd be happy to make that message clearer. If not, hrmf, I'll have to revise my root detection. > And your right. Packages for > Slackware are indeed tarballs, except the makepkg tool adds a script which > adds it to the records of what's installed on the system. Since your tool > says it can make RPM packages, I can convert those to ny Slackware packages. > What I'd really like is a few pointers suggesting where I should go next. First off, let's just get demo-sh4.sh running. Log in as a non-root user and try running it (after creating the directory /opt/crosstool and chowning it to that user). - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change |
From: Gregg C L. <dr...@wo...> - 2004-09-20 16:10:30
|
Hello from Gregg C Levine That's what it took. I created a non-root user, logged in as him. I then set ownership on the directories necessary for building the ctoss compiler, and started it off. It took the same time that your documentation stated, or around that figure. Now the question is, installing it. How should I do that? Gregg C Levine drwho8 atsign worldnet dot att dot net "Oh my!" The Second Doctor's nearly favorite phrase. ----- Original Message ----- From: "Dan Kegel" <da...@ke...> To: "Gregg C Levine" <dr...@wo...> Cc: <lin...@li...>; <lin...@m1...> Sent: Sunday, September 19, 2004 11:28 PM Subject: Re: [linux-sh:03313] Re: Building a cross compiler for the Dreamcast > Gregg C Levine wrote: > > Hello from Gregg C Levine > > Hmm. What I posted there, was a copy & paste from that newgroup posting. > > Evidently I did forget to provide a script of what the script does. > > > > ... > > + 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 > > > > I think that output clarifies my position. > > Right. Quick question: were you logged in as root when you ran that script? > If so, which part of "Don't run all.sh or crosstool.sh as root, it's dangerous" > don't you understand? I'd be happy to make that message clearer. > If not, hrmf, I'll have to revise my root detection. > > > And your right. Packages for > > Slackware are indeed tarballs, except the makepkg tool adds a script which > > adds it to the records of what's installed on the system. Since your tool > > says it can make RPM packages, I can convert those to ny Slackware packages. > > What I'd really like is a few pointers suggesting where I should go next. > > First off, let's just get demo-sh4.sh running. Log in as a non-root > user and try running it (after creating the directory /opt/crosstool > and chowning it to that user). > - Dan > > > -- > My technical stuff: http://kegel.com > My politics: see http://www.misleader.org for examples of why I'm for regime change |
From: Dan K. <da...@ke...> - 2004-09-21 01:32:11
|
Gregg C Levine wrote: > Hello from Gregg C Levine > That's what it took. I created a non-root user, logged in as him. I then set > ownership on the directories necessary for building the ctoss compiler, and > started it off. It took the same time that your documentation stated, or > around that figure. Now the question is, installing it. How should I do > that? No need. It's already installed. It builds in its final location. You might consider chown'ing it to root. - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change |