Difference between revisions of "Arch Hurd Project"
(→Stage 1 - Cross-compiler) |
|||
| Line 9: | Line 9: | ||
Build order: | Build order: | ||
* binutils | * binutils | ||
| + | * gcc (pass 1) | ||
* mach | * mach | ||
* mig | * mig | ||
* hurd | * hurd | ||
| − | * | + | * glibc (pass 1) |
| − | + | * libpthread | |
| − | * libpthread | ||
* gcc (pass 2) | * gcc (pass 2) | ||
| + | * glibc (pass 2) | ||
== Stage 2 - Cross-compile a bootable system == | == Stage 2 - Cross-compile a bootable system == | ||
Revision as of 00:48, 5 January 2010
Contents
Introduction
The Arch Hurd Project is, unsurprisingly, a project to get a working Arch system running on GNU/Hurd. This page will, at some point, tell you how you too, can get an Arch Hurd system. Maybe we'll even set up repositories and suchlike, even a website if this thing takes off.
Currently we don't have anything but an idea, some people crazy enough to like the idea, and the promise of some PKGBUILDs and a working cross compiler. Sorry.
Stage 1 - Cross-compiler
Staying consistent with Arch, the target we will build for is i686-pc-gnu. Sources for Hurd components are obtained from their git repo.
Build order:
- binutils
- gcc (pass 1)
- mach
- mig
- hurd
- glibc (pass 1)
- libpthread
- gcc (pass 2)
- glibc (pass 2)
Stage 2 - Cross-compile a bootable system
- Follow instructions from CLFS.
- More details when we get there...
Stage 3 - Natively build packages
- get makepkg/pacman working
- build packages
- make install CD
- party!
Ideas
Just what makes something Arch-like? Add ideas to this list.
- pacman/makepkg for package management
- Some form of ABS tree (in git/svn/cvs/whatever to allow easy package rollbacks, perhaps?)
- Something like the /etc/rc.conf file (anybody know anything about the Hurd boot process?)
- optimization - build for i686.
Repositories
I (Barrucadu) have a tonne of spare space/bandwidth on my Dreamhost account, so when this gets rolling if people want to volunteer to port/maintain packages they use, the repositories can live on there.
If I set up a git repo for the ABS tree, a packaging mailing list, and repositories (core/extra should do in the beginning, I imagine), I could give volunteers access to those so we could make progress.