Technical data

4. Packages
remove all artifacts that have been generated during the last FBR build. You will have to
confirm this action.
17
This is also useful to free used disk space.
4.24.3. Testing Of A Compiled Program
If a program has been compiled with fbr-make it may also be tested on the development
machine. Such a test will of course only work if the processor architecture of the developer
machine matches the processor architecture the fli4l programs were compiled for. (It is not
possible, for example, to run x86_64 flil4 programs on a x86 operating system.) If this condition
is met, change to the fli4l target directory with
chroot ~/.fbr/fbr-<branch>-<arch>/buildroot/output/target /bin/sh
and test the compiled program(s) there immedeately. Please note that executing chroot needs
administrator rights and thus you have to use sudo or su, depending on preference and system
configuration! In addition you will have to compile the FBR package busybox (via fbr-make
busybox), to have a working shell in the chroot environment. A small example:
$ sudo chroot ~/.fbr/fbr-trunk-x86/buildroot/output/target /bin/sh
Passwort:(Your password)
BusyBox v1.22.1 (fli4l) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# ls
THIS_IS_NOT_YOUR_ROOT_FILESYSTEM mnt
bin opt
dev proc
etc root
home run
img sbin
include share
lib sys
lib32 tmp
libexec usr
man var
media windows
# bc --version
bc 1.06
Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
# echo "42 - 23" | bc
19
#
4.24.4. Debugging Of A Compiled Program
In case of problems with compiled fli4l programs (crashes) you have the option to analyze the
state of the program immediately before the crash (also called “post-mortem debugging”). To
do so, activate DEBUG_ENABLE_CORE=’yes’ in the configuration of the base package. If case of
17
The whole directory ˜/.fbr/fbr-<branch>-<arch>/buildroot/output will be removed.
244