a bit closer

This commit is contained in:
Ciro Santilli
2018-02-13 16:09:16 +00:00
parent d97d461605
commit 64130ecfb9
22 changed files with 316 additions and 569 deletions

View File

@@ -1,5 +1,4 @@
[[qemu-user-mode]]
= QEMU user mode
=== QEMU user mode
This has nothing to do with the Linux kernel, but it is cool:
@@ -10,12 +9,9 @@ cd buildroot/output.arm~/target
qemu-arm -L . bin/ls
....
This uses QEMU's user-mode emulation mode that allows us to run
cross-compiled userland programs directly on the host.
This uses QEMU's user-mode emulation mode that allows us to run cross-compiled userland programs directly on the host.
The reason this is cool, is that `ls` is not statically compiled, but
since we have the Buildroot image, we are still able to find the shared
linker and the shared library at the given path.
The reason this is cool, is that `ls` is not statically compiled, but since we have the Buildroot image, we are still able to find the shared linker and the shared library at the given path.
In other words, much cooler than:
@@ -24,20 +20,15 @@ arm-linux-gnueabi-gcc -o hello -static hello.c
qemu-arm hello
....
It is also possible to compile QEMU user mode from source with
`BR2_PACKAGE_HOST_QEMU_LINUX_USER_MODE=y`, but then your compilation
will likely fail with:
It is also possible to compile QEMU user mode from source with `BR2_PACKAGE_HOST_QEMU_LINUX_USER_MODE=y`, but then your compilation will likely fail with:
....
package/qemu/qemu.mk:110: *** "Refusing to build qemu-user: target Linux version newer than host's.". Stop.
....
since we are using a bleeding edge kernel, which is a sanity check in
the Buildroot QEMU package.
since we are using a bleeding edge kernel, which is a sanity check in the Buildroot QEMU package.
Anyways, this warns us that the userland emulation will likely not be
reliable, which is good to know. TODO: where is it documented the host
kernel must be as new as the target one?
Anyways, this warns us that the userland emulation will likely not be reliable, which is good to know. TODO: where is it documented the host kernel must be as new as the target one?
GDB step debugging is also possible with: