Hi, Multi architecture support was of some interest for some time already, and the momentum and demand for crux on x86_64 is growing; also, there are some maintainers here that have x86_64 cpu's already. I'm one of them, but ran the regular 32-bit version so far, mainly because I'm still maintaining a few ports for the 32-bit version and didn't want to get into a conflict there. I think though that the time has come to seriously consider solutions to improve the support for multiple architectures, and to enable ports (of CRUX) to non-x86 architectures to use and re-use the work we put into the ports tree. You might be aware that I've experimented a long time ago with a merge tool called mppm, which worked rather nice, and was used by Simone for uCRUX. http://jw.tks6.net/files/crux/mppm.html Also, I wrote a merge point tracking for subversion called xsvn, which I used for CRUX/SPARC. http://jw.tks6.net/files/crux/xsvn/xsvn-howto.html I think that using a pure revision control tool isn't really suitable to solve our problem, and that using a semi-smart tool for the task of syncing ports is much better. As a consequence of the experience gained from using mppm and xsvn, I've tried to come up with an improved concept for multi-architecutre support. The result is a rather long document, and can be found at http://jw.tks6.net/files/crux/multi-arch-proposal I understand that not all of you are interested in this at this point in time, which is perfectly fine. If you are though, I'd appreciate if you could read through this document, ask and/or comment. If wanted, I can add it to the CLC wiki, but figured that at this point in time, I'd rather keep it on my website to underline it's inofficial state. Thanks for your attention, Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net