wip-arm

wip-arm

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

At Ludo's request I have started a branch: wip-arm 

It contains the start of a port to an Arm architecture.  Currently
it hasn't got very far unfortunately.

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-arm

[Ludovic Courtès]

John Darrington <john@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?

That sounds like a good start, thanks for all the work!

Ludo’.

Re: wip-arm

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

On Thu, Nov 27, 2014 at 02:19:44PM +0100, Ludovic Court??s wrote:
     John Darrington <john@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?
     
Yes.  Unfortunately they are insufficient for  building guix which surprised me.
Obviously I have misunderstood something.

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-arm

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On Thu, Nov 27, 2014 at 02:19:44PM +0100, Ludovic Court??s wrote:
     John Darrington <john@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.
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 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?

J'


-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: wip-arm

[Ludovic Courtès]

John Darrington <john@darrington.wattle.id.au> skribis:

> On Thu, Nov 27, 2014 at 02:19:44PM +0100, Ludovic Court??s wrote:
>      John Darrington <john@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’.