blob: 9757ff0e44f812ab5f5c1f64c130bda3d4babdac [file] [log] [blame]
Denys Vlasenko12efcf32015-10-05 09:04:04 +02001How to test build using Aboriginal Linux system images.
2
3* Put a source tree into hdc.dir/.
4For example, this should work:
5git clone git://busybox.net/var/lib/git/busybox.git
6
7* Run ./make-hdc-img.sh: it will generate ext2 image file,
8hdc.img, from hdc.dir/* data. This requires root for loop mount.
9
10* Download and unpack, or build from source and unpack
11one or more system-image-ARCH directories into this directory
12(the one which contains this README).
13
14* Run: ./parallel-build-hdc-img.sh system-image-DIR1 system-image-DIR2...
15(background it if you don't want to see "Waiting to finish" thing).
16This runs build in several qemu virtual machines in parallel.
17
18* Observe system-image-*.log file(s) with growing log of the build.
19
20There is no automated detection of errors for now: you need to examine
21logs yourself.
22
23Log files will also contain uuencoded (or if all else fails, od -tx1'ed)
24binary, if build was successful.
25
26To debug a build problem in one of the sandboxes, change keep_hdb
27to "keep_hdb=true" in parallel-build-hdc-img.sh
28- this preserves system-image-ARCH/hdb.img after the build,
29so you can go into system-image-ARCH and run
30"HDB=hdb.img ./dev-environment.sh" to debug the problem.
31
32You can also run "./parallel-build-hdc-img.sh -s system-image-ARCH"
33- single mode, output is to screen and serial input is from keyboard.
34
35If hdc.dir/bin/busybox-$ARCH exists, it will be used during build
Denys Vlasenko2b48c382015-10-05 15:10:44 +020036to supply additional tools (dir with all applets appended to $PATH).
Denys Vlasenko12efcf32015-10-05 09:04:04 +020037
38For me, the following system images worked:
39system-image-armv4l
40system-image-armv4tl
41system-image-armv5l
42 od is buggy on arm*:
43 # echo Hello-hello-hello-hello | od -b
44 0000000 110 145 154 154 157 055 150 145 154 154 157 055 150 145 154 154
Denys Vlasenko2b48c382015-10-05 15:10:44 +020045 0000000 157 055 150 145 154 154 157 012 <= WRONG OFFSET
46 0000000 (can also be even more bogus like 17767153361)
Denys Vlasenko12efcf32015-10-05 09:04:04 +020047system-image-i686
Denys Vlasenko2b48c382015-10-05 15:10:44 +020048system-image-mips - od is buggy
49system-image-mipsel - od is buggy
Denys Vlasenko12efcf32015-10-05 09:04:04 +020050system-image-x86_64
Denys Vlasenko2b48c382015-10-05 15:10:44 +020051system-image-powerpc - qemu 1.2.2 didn't work, 2.4.0 worked; od is buggy
52system-image-sparc - qemu 1.2.2 didn't work, 2.4.0 worked; od is buggy
Denys Vlasenko12efcf32015-10-05 09:04:04 +020053
54And these did not:
55system-image-armv6l - hang on "Uncompressing Linux... done, booting the kernel"
Denys Vlasenko12efcf32015-10-05 09:04:04 +020056system-image-m68k - my qemu doesn't like "-M q800"
57system-image-mips64 - init dies "Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000a"
58system-image-sh4 - qemu segfaults early in kernel boot