How to Handle a Linux BSP: from u-boot to "Hello World!"

1. Get a minimal Linux system capable of running a "Hello World" C application from the pack of software that your chip vendor calls their Linux "Board Support Package".
2. Configure and build the u-boot bootloader, the Linux kernel, the busybox minimal application environment and getting dynamically linked applications working.
3. Uses the qemu emulator to emulate an ARM hardware platform that loads all software over the network.

mozrunner on Fedora x86_64

If you try to use the mozrunner python library on Fedora or Red Hat x86_64, you'll get:

$ mozrunner
Traceback (most recent call last):
  File "/home/scottt/work/itrs_test/env/bin/mozrunner", line 8, in 
    load_entry_point('mozrunner==1.3.5', 'console_scripts', 'mozrunner')()
  File "/home/scottt/work/itrs_test/env/lib/python2.6/site-packages/mozrunner/__init__.py", line 86, in main
    moz = get_moz_from_settings(settings)
  File "/home/scottt/work/itrs_test/env/lib/python2.6/site-packages/mozrunner/__init__.py", line 165, in get_moz_from_settings
    cmd_args=settings['MOZILLA_CMD_ARGS'])
  File "/home/scottt/work/itrs_test/env/lib/python2.6/site-packages/mozrunner/__init__.py", line 131, in get_moz
    raise Exception ('No default or local profile has been set.')
Exception: No default or local profile has been set.

the solution: see mozrunner issue 10 for a trivial patch to ask mozrunner to look under /usr/lib64 instead of just /usr/lib.

If you're trying to use the windmill web testing framework, you'll need mozrunner-1.x-fedora-x86_64.patch instead until someone ports windmill to mozrunner-2.

Don't you just love 64 bit userspace packaging differences (multilib) between Linux distributions?