DCEmulation

I have come to burden you all with more problems, sorry lol.


I'm trying to get a development environment in Linux working, and still being a noob at all this toolchain/gcc/makefile/repository crap that gets hidden away from me in Windows it's quite frustrating.

I'm following instructions from here:
http://gamedev.allusion.net/softprj/kos/svn.php

It's very well written, however I can't setup a repository because it says:


However when I browse to http://gamedev.allusion.net/svn/ I get this:


So my question is:
1- Is there any other URL I can visit to get these files?
2- What exactly is these files "*_full.dump.bz2" and "_incr.dump.bz2"?

Sorry if I'm sounding like a complete retard here

Thanks!

That page is extremely old and doesn't reflect the current state of things at all, unfortunately. Now that you pointed out that its still there like that, I'll go and get rid of it before anyone else gets confused.

Basically, what you need to do is to get KOS from the SVN:

Then from there, go into the directory where it got downloaded to, look in the kos/utils/dc-chain directory in there and you should find what you need to get things set up. The download.sh script will download the source to GCC, Binutils, and Newlib. The unpack.sh script will untar them. The Makefile can be used to build everything. Take a look at the top of the Makefile and adjust any settings as you see fit. Probably the only ones that you'll need to change are the sh_prefix and arm_prefix if you want to change the directory where things are installed. Once you've done that, it should be as simple as typing "make" to get the toolchain to build.

From there, you'll have to set up your environ script, which isn't particularly hard since KOS comes with an example that should be mostly right to start with. Then build KOS, and you're done.

Haha, I had a feeling it was out of date but to what extent I didn't/don't know.


I'll try this, thanks a bunch!
I'll post back if I have any more issues (let's hope not!)

Yeah... Very old. Basically, I'm about the only person left that updates anything with regard to KOS, and I never really got a chance to actually go through and update the documentation on the website at all. At some point (prior to any new release) I intend to do it. When that will be, who knows.

Good luck!

I'm not trying to totally hijack the thread, but I need to set this up to compile DC KOS binaries.



Will manually installing the GCC package cause conflicts in my system? I'm so used to package managers doing the work, and even custom managers for compiling. AUR on Arch Linux...

Out of the three needed packages from the download script, I only have GCC installed.



Do I need to setup a chroot environment to keep them seperate? I've only done that once about a year back, or so.

_________________

Sorry to be a bother again.

the download.sh script outputs this:


This did fail, right?

Yes... Odd, I've never seen them take off an older release from the FTP. Regardless, change the references to binutils-2.21 to binutils-2.22 (in download.sh, unpack.sh, and Makefile -- look for the newlib_ver line in there) and you should be good to go.

You need to build a sh-elf and arm-elf version of GCC, Binutils, and Newlib. The script won't touch your system ones and will install the Dreamcast-related stuff in a different directory from the system stuff anyway.

It did for me, but all the script contains is wget commands.

I downloaded from here 'mirrors.usc.edu/pub/gnu/binutils'. I guess I could have opened the download.sh in a text editor, and changed the line to "wget -c mirrors.usc.edu/pub/gnu/binutils/binutils-2.21.tar.bz2 || exit 1". Everything seemed to compile properly for me.



Oh, okay. Thank you.

_________________

That worked great, thanks again!

EDIT:
I got past the last problem, but now another compile issue:


/home/nico/toolchains/ was a path I changed in the makefile, so it's installing to that correctly. It generated the sh-elf folders etc but there is no include folder after the it stops here.

I started from scratch 3 times, I'm guessing the issue is elsewhere

Did you set the paths for where you wanted to install the toolchain in the "*/cadcdev/kos/utils/dc-chain/Makefile"?

As an example, I personally set mine to the following where $HOME would be "/user/USERNAME/", or "/root".


In contradiction to the advice of almost every *nix user out there, I'm running my system as root (I'm the only user of this PC), but I'm betting the issues you are having are related to permissions. Did you create the install directory, and/or run the svn command, as a normal user? Was it initially created in a directory your normal user had permissions to?

_________________

No, the issue he's having now is that the script didn't exit when the error occurred during newlib's compilation. If you didn't actually FIX the issue with newlib's build, it was that you didn't have the makeinfo program installed. If you don't fix it, you'll likely never get that part working properly (you could also work around it by hacking up the Makefile, but that's a bit more work that I don't remember how to do off the top of my head right now).

I recommend removing the whole /home/nico/toolchains/dc directory and starting over (you should also clean out all of the intermediate directories that the dc-chain makefile made for building the tools), once you install the makeinfo program.

Most Linux distributions will have that in the "texinfo" package, apparently.

Since he's installing in his home directory, it is not likely to be a permissions issue.

Even if you are the only user, you should never run as root for regular use. Not that me stating this will probably change your mind, but from a systems programmer's perspective, that is a REALLY bad idea. One flaw in any of the programs you run on a daily basis (and believe me, I'm sure there are plenty of them), and your system would be toast. Hell, one mistyped command and your system would be toast.

Okay this is getting pretty frustrating now.

Every time I attempt this, it always uses binutils 2.21 instead of 2.22 (if that's worth noting seeing as it seems to be only me with this particular issue)

And I'm still stuck at this error:


In sh-elf there is a FILE called include, but no directory. So I can see why it's giving this error but I don't know why it tries to access a folder it hasn't yet created.

I've installed texinfo package, ran things as root, made sure no permission issues are present etc. But I'm still getting stuck at this error.

Oh and I've wiped everything clean before restarting the build. Actually downloading a fresh copy from the SVN. So no original files remain when I restart the build.

Any thoughts?

Update KOS to the latest SVN revision. I've changed it in the SVN to use 2.22 now.

The problem is that Newlib still isn't building properly, so your problem is actually further up the log from what you've posted. If you're not getting the message about makeinfo anymore, I'm not sure what to suggest without seeing what the actual problem is that prevents Newlib from building.

If its still a problem with makeinfo, I have a way that you might be able to work around it... Namely, download and un-gzip the file I've attached to this post, run the download/unpack scripts as normal, then put the "missing" file that came out of the file you downloaded from this post in the newlib-1.18.0 directory, overwriting the existing "missing" file there. Hopefully then it'll work... I can't actually check on my machine, since I don't have the problem that you seem to have with makeinfo.

First of all, thanks for all the help. I really appreciate your help BlueCrab.

I've tried the new file, and various other things (generally fiddling with the makefile etc).

But I still can't get past this error. Everything seems up to date (svn and whatnot).

I've flushed the output to a file.

EDIT:
Okay, seems I can't paste it here or upload the file. But here is the output from pastebin if it helps:
http://pastebin.com/CrWGd6Y3

I'm not sure what else I could try...

Aha! That shows the issue quite well, actually. The problem is that it didn't build sh-elf-gcc properly, because you were missing a dependency for GCC. Install GMP 4.2 or later, MPFR 2.3.1 or later, and MPC 0.8.0 or later from your system's package manager. Make sure to get the -devel packages too, if needed on your distribution.

Thanks BlueCrab, you wisdom truly knows no bounds I guess

I'll install those and have another try, what lines gave it away though? (for general education)

This part:


Also, I just noticed in that log that it didn't actually install binutils either. It complained that it couldn't create the directory /opt/toolchains. You probably need to run make as root to make sure it works right, or give your regular user permission to write to /opt. Either that, or install it somewhere that you do have write permissions, like in your home directory as you were trying to do before.

Hi, Bluecrab. I was just wondering about the dc-chain script failing due to missing dependencies during the configure phase. Would it be better to configure all the tools first and report the missing dependencies?

I've rebuilt the toolchain a couple of times after reinstalling linux and found myself restarting the process because GMP et al were not part of the default install.

_________________
behold the mind
inspired by Dreamcast

Honestly, my Makefile-fu isn't all that great to actually figure out how to fix it. Really, the problem is that it doesn't exit when there is an error, as a Makefile should... It doesn't actually exit unless a sub-call to make fails, which is what the main issue is.

Um - when do you plan to add SD support to the "official" repo? Most of us can't use it until you do. I'm using the repo from emuforge as that has SD card support. I'm sure many others are as well. That also has Chui's Allegro port as well.