John Darrington <j...@darrington.wattle.id.au> skribis: > On Thu, Nov 27, 2014 at 02:19:44PM +0100, Ludovic Court??s wrote: > John Darrington <j...@darrington.wattle.id.au> skribis: > > > It contains the start of a port to an Arm architecture. Currently > > it hasn't got very far unfortunately. > > It allow you to cross-build the bootstrap tarballs for ARM, right? > > > Does anyone know the next step? > > The bootstrap tarballs are insufficient to natively build guix on the target > machine.
Yes, that’s expected. > And I have been unable to build a version of Guile which is up to the job - > they all > have one problem or another. The machine should already have a working Guile, GCC, libgcrypt, etc. Using the bootstrap tools for that job may fail unexpected. (Since you gave access to your armv7 box, I tried to get Guile running, but haven’t been very far yet. I’ll keep you updated.) > The Porting section in the manual says that I must "update" some files and > return the "right > name" and that it must be "taught about the new platform". Can anyone > elaborate on this? > How do I know what parts of the files must be updated? Which name is "right" > and how do > I "teach" it about the new platform? Commit 1c0c417d expounds that section a bit. Commit f57ff219a, which added mips64el-linux, should also give you info. Thanks, Ludo’.
