Wait, does that mean that I should have a libbfd in my /opt/toolchains/dc/sh-elf/lib/ directory? The only library I have is libiberty.a. Well, I'll know if dc-tool works as soon as I get a crossover cable tomorrow. I'm getting confused between what libraries were expected for me to have on my Linux ...

So, removing the reference to the sh-elf lib directory and adding a reference to libdl.a let me build everything (I haven't tested it yet). I'm not sure why the reference to the sh-elf library is there if we aren't supposed to link to anything in that library for dc-tool, which is one of the program...

So, here comes the next issue I've got. I wanted to build dcload-ip because I own a broadband adapter that I wanted to use for developmental purposes with my Dreamcast. Unfortunately, when I attempt a make, I get the following error: make -C tool make[2]: Entering directory `/home/rcsvt/cadcdev/dclo...

Hurray! All examples build, just like you promised! You definitely fix issues quickly! I'm going to mark this topic as solved considering the main issue of missing sh-elf-g++ was fixed.

Yeah, I agree. I'd still like to not let this get ignored, though. It'd be nice to compile the examples right out of the box. The newest issue I have is this one regarding networking's simhost: kos-cc -c simhost.c -o simhost.o In file included from /home/rcsvt/cadcdev/kos/../kos-ports/lwip/lwip/src/...

So, when trying to build vqenc in the utils directory, I was receiving this error: make cc -o vqenc vqenc.o get_image.o get_image_jpg.o get_image_png.o readpng.o -lpng -ljpeg -lz /usr/bin/ld: vqenc.o: undefined reference to symbol 'sqrt@@GLIBC_2.2.5' /usr/bin/ld: note: 'sqrt@@GLIBC_2.2.5' is defined...

Furthermore, when attempting to build all of the examples for the Dreamcast, I'm getting errors: kos-cc -c pvrmap.c -o pvrmap.o pvrmap.c: In function 'main': pvrmap.c:31:31: error: 'MMU_NOT_SHARED' undeclared (first use in this function) pvrmap.c:31:31: note: each undeclared identifier is reported ...

So, I removed my multilib installation of GCC 4.5.2 and also cleaned out my /opt/toolchains/dc/ directory and the dc-chain directory within kos/utils/. Building it went well and it now has a binary of sh-elf-g++ in the bin directory. Furthermore, I successfully built kos, I think, as I didn't receiv...

I built gcc 4.5.2 from a different source than the downloaded gcc 4.5.2 in the dc-chain directory. For ArchLinux, I used this package: http://aur.archlinux.org/packages.php?ID=57582

So, I should try building it with my normal GCC, which is version 4.6.2? I'll give that a go and see what happens.

Here's what I got from running sh-elf-gcc with the 'v' switch: ./sh-elf-gcc -v Using built-in specs. COLLECT_GCC=./sh-elf-gcc COLLECT_LTO_WRAPPER=/opt/toolchains/dc/sh-elf/libexec/gcc/sh-elf/4.5.2/lto-wrapper Target: sh-elf Configured with: ../gcc-4.5.2/configure --target=sh-elf --prefix=/opt/toolch...

I ran through each of the files located in my /opt/toolchains/dc/sh-elf/bin/ directory and got the version. For most of them, it's 2.22; however, for gcc, gcc-4.5.2, cpp, and gcov, the version is 4.5.2. I've uploaded an output file here: Versions : http://senkbeil.no-ip.org/tmp/version-output.log [E...

Thanks for the reply, BlueCrab. For future notice, I am running ArchLinux, which works with a rolling release system; however, I manually installed gcc-4.5.2 thinking it was necessary at the time. I've switched between gcc-4.5.2 and gcc-4.6.2 (the current version I have for my system) for builds and...

I am absolutely positive that this is an error on my part as this is my first time attempting Dreamcast development (and, really, working with any large, open-source project). Most of my experience is within academic settings, unfortunately, which means that you'll probably find me making a lot of m...