DSM-G600, DNS-3xx and NSA-220 Hack Forum

Anyone willing to help a newb out with this?

Running Ubuntu 6.0.6.1 desktop.  Compiled the toolchain without issue (least as far as I can tell).

Now I'm not really sure what to do.  I read that some paths need to be setup to use these tools?  But other then running a 'make' or some other setup script I haven't done much so need a little hand holding.

I use a Sharp Zaurus PDA running OpenEmbedded, so I know there are a lot of apps that could have potential on this unit.


Thanks in advance

Any chance of getting a new link to the precombiled toolchain binary? 
The link from the homepage is broken.

Gavin.

I'm trying to build the toolchain on Ubuntu Dapper, which has gcc4 as it's default C compiler.  When I run make I get:

/home/beattie/dsm-g600/toolchain/powerpc-uclibc-toolchain/toolchain_build_powerpc/gdb-6.0/gdb/gdbtypes.c:3059: error: invalid lvalue in increment

Not surprising given the directions not to use gcc4, but I can't figure out how to force it to use a different version.  CC=gcc-3.4 make -e fails in a way that leads me to beleive that it is using gcc-3.4 when it should be using the cross-compiler.

Anybody have an clues?

It has been a few months since I compiled mine, but I'm pretty sure I just installed gcc-3.4 and then changed the gcc link in /usr/bin to point to that instead of 4.x, and then changed it back when done.

I can't compile this toolchain under my Debian

When I try to compile the toolchain I get this error:

...
checking for library containing socketpair... none required
checking for library containing tgetent... no
configure: error: no termcap library found
make[2]: *** [configure-gdb] Error 1
make[2]: Leaving directory `/home/systemr89/powerpc-uclibc0.9.26-toolchain/toolchain_build_powerpc/gdb-build'
make[1]: *** [/home/systemr89/powerpc-uclibc0.9.26-toolchain/toolchain_build_powerpc/gdb-build/.compiled] Error 2
make[1]: Leaving directory `/home/systemr89/powerpc-uclibc0.9.26-toolchain'
make: *** [build-stamp] Error 2

termcap library is dismissed and I haven't found any way to solve this problem.
Install termcap-compat, lib5 and ldso not solve the problem

Hello,

I've some problems with porting python on dsmg600. It seems to me that the first is that my toolchain  uclibc is not exactly the same than dsm one.
On your toolchain have you the same uClibc-0.9.26.so than on dsm ? (ls -l and md5sum) ?

sala wrote:

It's not quite possible to compile all files with same size and with same md5 sum on a different host systems

Ok thks ...

sala wrote:

But this toolchan is the one provided by d-link + some fixes described at first post.

I gave mine on ftp.dlink.com but the uclibc is download at make time so you're not sure to have the same uclibc than the one use by dlink. Same problem with the linux headers and gcc.

The download site at gnu changed. GCC_SITE is wrong in gcc-uclibc-3.3.mk. Remove "releases" from the link.

hutzel wrote:

I assume this was not done automatically, i tried compiling gnu-hello with the posted Q'n'D script above- it failed.

What is exactly the error you get and for what command?

hutzel wrote:

Oh dear! How I regret moving from my amiga to win95 instead of Linux back in 1995

Well, I regret sleeping in my English class

2015 update to anyone that needs to build the toolchain. I highly suggest you do this inside a chroot of Debian Sarge on the device, which will take some time to compile, but the end result is worth it.
You'll need to place these files in the /sources/dl/ directory upon extraction from the toolchain source tarball...

binutils-2.14.90.0.7.tar.bz2
uClibc-0.9.26.tar.bz2
gcc-3.3.3.tar.bz2
gdb-6.0.tar.bz2

so you'd cd into the folder and wget the files to that location... cd .. back to the base of that folder and run make. unless you're missing a package the compiler needs, it should start compiling the toolchain as expected. if you ARE missing something, remedy the problem, go back to the base of the folder and run make again... it should start right back up where it left off.

if you're still having trouble downloading the files from the links provided, a simple google search for the file in question will turn up mirrors for both files.

Also make sure that if you ARE compiling these on a chrooted sarge install that you have gettext, bison, libncurses5-dev and flex packages installed via apt-get/aptitude, as well as the normal assortment of essential building tools. build-essential seems to be a metapackage that really didn't do anything for me with the chrooted sarge install (usually installs a plethora of tools for compiling on newer versions), but I want to believe that it's because the files were already downloaded when the chroot initially grabbed packages.

At the current moment I type this, the toolchain is compiling on my DSM-G600 in the chroot. it's taking its normal time, but I AM compiling on a 175MHz PPC 603e core with only 32 megs of actual RAM...! and the 500-or-so odd megs of swap.

The reason for adding these files to the powerpc-ucibc-toolchain/sources/dl directory is because then make doesn't need to grab them later from obviously 404'd links. I endured this so you don't have to.
Hopefully this is of some help. also try and make sure you do the compile wiithin a screen session, it's a lot easier to detatch and come back to it later instead of having a terminal window open to it all the time. the compile will take a long time.