Newcomer - First (long) questions AL develop on cubieboard

[dieghen89]

Hi guys, I'm new here. First of all big thanks to have ported my (ours) favorite distro on ARM. I'm an ArchLinux user since about 5 years, so i know quite good all the tools provided by the standard version and i'm familiar with kernel build (see kernel-netbook). On the other hand, the ARM world is totally unknown to me, so don't blame (but correct) me if i write bullshit

I'm starting an university project with the aim to develop a cheap laptop powered -also- with solar panels. We chose the cubieboard as master piece, and i'm glad to see you're supporting officially
Beyond the hardware-side (power and hdmi2lvds pcb) there's something to do with the software. When the cubieboard will be delivered i'd want to start testing a couple of buildchains, roughly the one you provide and linaro. I managed to:

• create a clean x86 chroot from what compile arm packages (i prefer avoid the distcc build)
• get an early configuration of crosstool-ng for the buildchain

I have a lot of questions, but i guess to find some patient people here.

$this->bbcode_list('1')

If i want to build a kernel, following the developer page the preferred method is through pkgbuild (i've seen the linux-sun4i in github). With this method we can install the updated package from inside the cubie, as the x86 arch do. I've read in the installation guide for cubie that you provide the uImage for the kernel; is this method incompatible with the pkgs? I mean, if i set up my cubie with an uImage, and then i want to update the kernel, the files present in /boot are not linked in the pacman db so when i'll install a packaged kernel, should appear a conflict. What's wrong in my thinking?

If i'd want to compile the whole system e.g. to test some buildchain or optimizations flags, i can grab all the pkgbuild from ABS/your github and build. The problem i can see here is that is different compared to a kernel build, that is "standalone". The pkgs needs to find libraries, dependencies etc not present in the x86 chroot. What's the right way to follow? Yeah i can launch the build from cubie and distcc, this would solve the problem, but what i have to do to avoid this way?

If i manage to realize 2), how could i create a whole root filesystem? The first thought is do something similar a chroot creation but with ARM packages and then stupidly copy them to the SD. It's right?

Where can i find some documentation about the devtools present in your github? Waiting the cubieboard i'm writing a very simple set of scripts for automate a clean chroot creation, download all necessary git projects, buildchain creation with crosstool, etc. I want to write something for a root fs creation (as asked in 3), and maybe understand the method you used for yours scripts (that i'm sure offers more than i need) could me help.

I've been more long winded than i was expecting, excuse me A big thanks for everyone read till here, be sure i'll come back with other questions

[WarheadsSE]

The developers strongly suggest distcc for a reason. Also, anything compiled outside our tool chains, we will not support. Sorry.

As for building a rootfs. Pacstrap works from a base image on a matching processor architecture, and most of the tools are self commented, or are identical to upstream.

[kmihelich]

We're not here to teach you how to do what we do. If you really want that level of help, our consulting rates are fair.

[dieghen89]

$this->bbcode_second_pass_quote('WarheadsSE', 'T')he developers strongly suggest distcc for a reason. Also, anything compiled outside our tool chains, we will not support. Sorry.

As for building a rootfs. Pacstrap works from a base image on a matching processor architecture, and most of the tools are self commented, or are identical to upstream.

[kmihelich]

Asking about certain aspects is one thing. Asking us how to rebuild all of the packages and put them into a working root filesystem is another. You are asking about the latter, and is not something we're prepared to teach sans compensation. It's far too complex and in-depth, as it encompasses the majority of the work we do as developers for this distribution.

[dieghen89]

I apologize for the misunderstanding. Maybe i have a more open idea about, i don't think i asked company secrets, just some guideline for an arm newbie. I respect your point of view and i close the argument, the last thing i want is argue on this kind of stuff. My next posts will be pertinent to end-user issues or btw directly related on your (great) work with ALARM.

Coming back in-topic. Can be known the reasons you haven't choose linaro, not even unofficial/test? I never owned an arm device so i still don't know the real benefits, i just read news

[WarheadsSE]

Just don't take phoronix as accurate.