Buffalo NAS-Central Forums

There already some threads on compiling Ocaml on Linkstations.
The problem is that Ocaml comes with hardware-FPU support on Arm only,
no soft-float support. This means you can only compile a part of Ocaml's
compiler suite. Ocaml has a byte-code and a native code compiler,
the native one fails to compile due to missing soft-float support.

To compile byte-code Ocaml compiler:

wget http://caml.inria.fr/pub/distrib/ocaml-3.09/ocaml-3.09.3.tar.bz2
tar -xjvf ocaml-3.09.3.tar.bz2
cd ocaml-3.09.3
./configure
make world install

Hello All,

I've decided to post another release of the native toolchain (prior to OpenLink/Kernel-2.6.16+/glibc-2.4+ release) in order to facilitate mindbender's, george's, Kaiten's, nobody and friend's effort to push for a OpenLink-arm release plus to test compilation theories for Zoolook's GenLink (i.e. libtorrent). This release will contain some fixes found in the bugtracker, and some additions that people have posted. As this will not be a final toolchain (one for linux-2.6.16+/glibc-2.4+), I still cannot guarentee that it will compile eabi binaries fully and correctly. However, after a test of the toolchain by mindbender and other developers for the final OK, I will make this release public.

Anyone still using the native toolchain, arm-tools version 0.16-8. please post bugs/fixes now either here or in the bugtracker so that I can make the proper fixes. Thanks

P.S. Sorry for the inconveniences that the project delay may have caused. Also note that the upcoming version will be a heavy revision from the previous.

_________________
http://www.opifer.net

I now have a working glibc linked with a gcc-4 libgcc. I haven't pushed it to 2.4 yet, but it works It requires an kernel w/ an updated library (also working now), and a new busybox + a few other things. I will make a package w/ a new image (that should be added to OpenLink-arm) including sysvinit, which is on the list. Then supply a separate toolchain package.

Let me know what you guys think (i.e. bender, Kaiten, nobody, Georg) so I can get you the correct stuff for the upcoming "preOpenLink" image.

_________________
http://www.opifer.net

@mindbender, I finally took a look at your sysvinit setup. The scripts do not work. There are several discrepancy errors. I will look at this and try to get it working

EDIT: mindbender, I shouldn't say that they didn't work, just had some bugs...sorry Anyhow, I am trying to repair the a couple of links and inits. Good Job, should have a working sysv for you soon

Also, there is this extremely odd daemon temperature/fan controller daemon that you started, and it's REALLY buggy, and screwing the box a bit. I may just replace it all with micro_evtd

_________________
http://www.opifer.net

YAY!!! I fixed sysvinit. We now have runlevels working for a stock based firmware. IMHO, I think we can have a first release of OpenLink-arm9 soon

Just need to clean up the links and edit a couple of inits, for example, the log daemon so doesn't print verbosely to the screen.

_________________
http://www.opifer.net

woohoo!

to be honest: sysvinit makes the difference regarding jtymod/Pre-openlink/OpenLink. images with sysvinit and stock glibc are our pre-openlink-images.

real openlink images will be images with more standard-glibc than the codesourcery one and a kernel compiled from patched vanilla sources.

GOOD WORK jon.

_________________
LS1 (2.6 kernel, foonas svn1062, 750 GB, UBoot 1.2) & LS Pro (FreeLink/jtymod/GenLink, changes all the time)
Thx to all donators!

agreed. Anyway, I will produce the sysvinit package soon for everyone to use. The standard-glibc is tied to the kernel, though now it's dependency has been severely reduced and thus, I will experiment w/ glibc-2.4 too. I can't say when a more standard kernel will be available, though there is light at the end of the tunnel now. Also, the kernel I posted (or will post if I haven't) should now use standard eabi syscalls, it's the OABI backup support that is weird, and may still cause issues (so, not full eabi yet, but better).

_________________
http://www.opifer.net

mindbender, saved the box for brick. Had part of the fray disrupting the datarails somehow. Anyway, I have to fix another thing w/ sysvinit, as the buffalo kill functions reset somethings. Will keep you updated.

_________________
http://www.opifer.net

may I know how i can download this chaintools. it ask me the username/passwd?

Visit here: http://buffalo.nas-central.org/index.php?title=BetaTesters and sign up to become a betatester. After doing so, PM an admin for a username/password.

_________________
http://www.opifer.net

Thanks for your informaton. I read the BetaTesters page. and also add myself to "Normal Candidate List"(I don't know if this is what I should do). Would you please consider give me access to download that chaintools. I know some Linux, only on Redhat. I never run Debian before. But I think I can learn it quickly. as far as I think, other than rpm, the main difference is the boot process and the configuration files.

I hate microsoft too! Are you microsoft haters running linux or Mac OS? Or are you stuck with Windows/DOS because of SW requirements?
Surely you're not running Windows by choice?

I personally run ubuntu/debian linux. I have a few machines w/ MS, but that's for either work or other family members not comfortable with Linux.

_________________
http://www.opifer.net

Well, I grabbed the arm-tools-0_16-8 and set up the chroot environment on my Linkstation Live.

I can compile and execute "Hello, world!". Rah.

What I would like to do now is to compile the kernel for for my box so that I can create ipchains or iptables modules. Does this source and any patches exist somewhere?

The dmesg for my stock Linkstation Live is:
Linux version 2.6.12.6-arm1 (root@localhost.localdomain) (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #79 Wed Oct 4 13:37:40 JST 2006
CPU: ARM926EJ-Sid(wb) [41069260] revision 0 (ARMv5TEJ)

So far, I'm not really that interested in replacing the stock install of Linux. It's got ssh, rsync, screen, and perl from the get go. The ctorrent that you folks compiled up (thank you, whoever did that), just drops in and runs. I had to create a new script for autostarting torrents, but that's fine (especially since perl is available anyway).

Any pointers for compiling up the kernel would be appreciated. Thanks.

Hmm, what module are you missing that prevents iptables + ipchains from working? I say this, because, the codesourcery cross-toolchain is the only stable method for compiling kernels and kernel modules for the ls pro/live. Everything else can be compiled natively.

Also, in the upcoming weeks, a new kernel will be released, accompanied by a revised + updated native toolchain. Native compiles of the kernel + modules should not be a problem then.

The sources exist on our site in the GPL/source section.

_________________
http://www.opifer.net