Hi! I'm regaining all the fun of porting! :-D I've just set-up again some script to (once a day) build a (kernel-only, for now) cross-compiler for the vax-linux target. (To be exact, I'm building for all these targets: alpha-linux arm-eabi avr bfin-elf frv-linux h8300-elf hppa-linux hppa64-linux m32r-linux m68k-linux microblaze-uclinux mips-linux mips64-linux mn10300-linux powerpc-linux powerpc64-linux ppc-linux ppc64-linux s390-linux s390x-linux sh-linux sh64-linux sparc-linux sparc64-linux tic6x-uclinux tilepro-linux vax-linux xtensa-linux ) It's the `master' branch of binutils's, gcc's and gdb's GIT repositories. What made me wonder the most was that things seem to work out of the box. I remember the dark times quite well, when it was quite a drama building a kernel-only cross-compiler, let alone one that could build userland. My next step is to also extract Maciej's SRPMs (you can find them at ftp://ftp.linux-mips.org/pub/linux/mips/people/macro/SRPMS/) and build them as well (for `vax-linux' only.) That should bring me back to business. What's also quite nice is, that after not building a vax-linux gcc for quite some time, it just worked. Some 5 or 6 years ago, that target was broken like two times a month! That was (even longer ago) why I wrote a script to compile a compiler on a regular basis to catch problems early. (It's easier then to find the trouble-causing patch.) MfG, JBG -- Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481 Signature of: The real problem with C++ for kernel modules is: the second : the language just sucks. -- Linus Torvalds