User Tools

Site Tools


developersguide:pkgsrconarm

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
developersguide:pkgsrconarm [2016/02/09 10:35]
dcvmoole [Getting started] a bit more
developersguide:pkgsrconarm [2016/02/09 13:49]
dcvmoole clarification
Line 7: Line 7:
 Ideally, pkgsrc would be crosscompiled with MINIX3-on-ARM as target, just like MINIX3 itself needs to be crosscompiled for ARM. However, the main problem with this approach is that crosscompiling pkgsrc is not yet supported properly by pkgsrc itself. This is a larger problem that would have to be, and hopefully eventually will be, addressed by the NetBSD/​pkgsrc community. It is unlikely that we can pull this off ourselves. Ideally, pkgsrc would be crosscompiled with MINIX3-on-ARM as target, just like MINIX3 itself needs to be crosscompiled for ARM. However, the main problem with this approach is that crosscompiling pkgsrc is not yet supported properly by pkgsrc itself. This is a larger problem that would have to be, and hopefully eventually will be, addressed by the NetBSD/​pkgsrc community. It is unlikely that we can pull this off ourselves.
  
-Crosscompiling is necessary not only to compile the packages for the ARM platform, but also to compile them for MINIX3, ​which means that the only way to avoid having to crosscompile at all, is to compile the pkgsrc packages natively from the MINIX3-on-ARM platform itself (as is done for MINIX3-on-x86 as well). With the current situation, this gives us two options.+Crosscompiling is necessary not only to compile the packages for the ARM platform, but also to compile them for MINIX3; thuscompiling from Linux on ARM as host platform would still require crosscompilation. This means that the only way to avoid having to crosscompile at all, is to compile the pkgsrc packages natively from the MINIX3-on-ARM platform itself (as is done for MINIX3-on-x86 as well). With the current situation, this gives us two options.
  
 The first option is to compile the packages from the beagle* hardware itself. This would probably have to involve an external (USB) hard disk connected to the BeagleBone Black/​White,​ formatted with ext2 to allow for long file names, to host the entire pkgsrc environment. We currently do have a USB stack and mass storage driver for the BBB/BBW, so doing so should not require extensions to the current system. However, it is possible that the beagle* hardware is too weak to pull this off in any reasonable time frame (if at all, due to, say, too little RAM); we simply don't know, and won't know until somebody actually tries. The first option is to compile the packages from the beagle* hardware itself. This would probably have to involve an external (USB) hard disk connected to the BeagleBone Black/​White,​ formatted with ext2 to allow for long file names, to host the entire pkgsrc environment. We currently do have a USB stack and mass storage driver for the BBB/BBW, so doing so should not require extensions to the current system. However, it is possible that the beagle* hardware is too weak to pull this off in any reasonable time frame (if at all, due to, say, too little RAM); we simply don't know, and won't know until somebody actually tries.
Line 19: Line 19:
 Quoting sambuc on IRC (2016-02-09):​ Quoting sambuc on IRC (2016-02-09):​
  
-"I would first look to bootstrap pkgsrc on minix/arm. You can take a look at https://​github.com/​Stichting-MINIX-Research-Foundation/​pkgsrc-ng/​blob/​3.3.0/​minix/​pbulk-ng.sh to see the exact way we bootstrap on minix/x86 +I would first look to bootstrap pkgsrc on minix/arm. You can take a look at https://​github.com/​Stichting-MINIX-Research-Foundation/​pkgsrc-ng/​blob/​3.3.0/​minix/​pbulk-ng.sh to see the exact way we bootstrap on minix/x86 
-the first step is to do what is within the lines 270-332" +the first step is to do what is within the lines 270-332 
- +then you will be able to use bmake to compile anything you want from pkgsrc 
-"then you will be able to use bmake to compile anything you want from pkgsrc" +you don't need to build the chroot for now. This is mainly a safety net to ensure a clean environment on minix/x86 
- +and as those steps take a couple of hours already, even on intel, we copy the chroot, to be able to restart from the step n-1 when needed 
-"you don't need to build the chroot for now. This is mainly a safety net to ensure a clean environment on minix/x86" +iirc, the strict minimum to do to get bmake & pkgsrc working is line 273-297, then you have bmake available
- +
-"and as those steps take a couple of hours already, even on intel, we copy the chroot, to be able to restart from the step n-1 when needed+
- +
-"iirc, the strict minimum to do to get bmake & pkgsrc working is line 273-297, then you have bmake available"+
developersguide/pkgsrconarm.txt · Last modified: 2016/02/09 13:49 by dcvmoole