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

Hi, pcp,

in this thread http://dns323.kood.org/forum/t1356-HOWT … S-313.html
andrew reported, he has setting up cross compile environment.
I would prefer this way too, but need more hints...
But seems, andrew is no more active in this forum.

Last edited by CharminBaer (2008-05-12 17:29:29)

uclibc works, but you should either use snapshot or apply the fix mentioned in here: http://bugs.busybox.net/view.php?id=3124

If you want to compile kernel sources from dlink there may be 3 syntax bugs in the source that prevent compiling, but they are quite simple to fix.
Otherwise uclibc works very good, if you need some help give me a message

CharminBaer wrote:

look there...
http://buildroot.uclibc.org/buildroot.html
I´m not tried yet, but it sounds interesting.

i've tried it, but it fails hardly for some weird reason. it compiles the packages with gcc, then attempts to link with arm-ld. and it removes and unpacks ALL packages every remake. awful system

naffarin, i've got following problem when i am compiling uClibc:

In file included from ./include/sys/sysctl.h:45,
                 from libc/sysdeps/linux/arm/ioperm.c:46:
/usr/include/linux/sysctl.h:34: warning: no semicolon at end of struct or union

in short, the uclibc include #undef some variables, which in turn are needed in kernel includes. I've found on google that's because use of the internal kernel includes instead of set of includes generated by a make make_headers. but this target isn't supported by d-link's kernel.

I rather think that was an error that is caused by using kernel header instead of sanitized headers...do you use the d-link toolchain for the linux includes ? If you do, you should switch to a suitable header package like linux-headers-2.6.12 in the buildroot config.

By the way for me buildroot is working fine (after a few , well , after a lot of experimenting with the config).
You shoudl go for the current buildroot tarball (but not the svn snapshot...i had some problems with that) and uclibc 0.9.29 with the above patch, that is a working combination for me.

CharminBaer wrote:

Why not using the DNS-313 himself for make&compile? Too slow? Still don´t believe...
Today I installed gcc, make & co. at my box. But still get many errors and warnings.
Let´s see next week...

hi, i'm back

Generally, it isn't a good idea to compile on the embedded box - they usually have a slow cpu and a very little memory. Compiling the kernel this way would take more than one day, maybe longer.

If you want to use the d-links toolchain, you need to make sure you have the $CC, $PATH and other environment variables set'd up. The attached script can do this for you, just change the PATH= liine according to your d-link's source root.

When compiling the kernel, if you got the errors, try to do do $make clean first. It's not necessary to do it all the time, but if you are altering sources, there might be some unresolved dependencies.

Then you will need to add the bootp header. I'm using the original Makefile in the Image directory for that. Sadly, i dunno what I have changed in the past.

Things I remember I've changed
In the file
Image/toolchain/bin/mkflash
comment out the line rm -rf system_tmp.tgz
and in the Image/Makefile
make sure the script will copy the zImage to the Image/src/kernel (line 37)

this will create system_tmp.tgz, which includes all files you need: kernel, ramdisk, and a root filesystem

feel free to ask if you have errors..
cheers,pcp

---

Attachments:
source.me, Size: 296 bytes, Downloads: 541

pcp wrote:

Generally, it isn't a good idea to compile on the embedded box - they usually have a slow cpu and a very little memory. Compiling the kernel this way would take more than one day, maybe longer.

DNS-323 and DNS-313 are fast enough to compile most packages within reasonable time. The kernel is special in that it doesn't require a full cross-toolchain, so it's usually simple enough to cross-compile.

fonz wrote:

pcp wrote:

Generally, it isn't a good idea to compile on the embedded box - they usually have a slow cpu and a very little memory. Compiling the kernel this way would take more than one day, maybe longer.

DNS-323 and DNS-313 are fast enough to compile most packages within reasonable time. The kernel is special in that it doesn't require a full cross-toolchain, so it's usually simple enough to cross-compile.

I meant ordinary packages like libraries etc.I can't imagine compiling the large package like libc in reasonable amount of time, especially when you are developing stuff. For the simple programs like a fan control, it's still usable though.

Hope the folks from the openwrt project will make a release of a buildroot for the 313 SoC soon, their build system would be a great boon for everyone.