Technical data

4. Packages
and libraries should be identified that use libm (Library with mathematical functions) use
fbr-make links-against libm.so.0 because libm.so.0 is the name of the libm library. A
possible output would be:
$ fbr-make links-against librrd_th.so.4
Executing plugin links-against
Files linking against librrd_th.so.4
collectd usr/lib/collectd/rrdcached.so
collectd usr/lib/collectd/rrdtool.so
rrdtool usr/bin/rrdcached
In the first column is the package name and in the second the (relative) path to the file that
is linked against the library in question.
To find the library name for a library, you can use readelf like this:
$ readelf -d ~/.fbr/fbr-trunk-x86/buildroot/output/target/lib/libm-0.9.33.2.so |
> grep SONAME
0x0000000e (SONAME) Library soname: [libm.so.0]
Display Of Version Changes
The command fbr-make version-changes is interesting (only) for fli4l-team developers with
write access to the fli4l SVN repository. It lists all FBR packages whose version has been
modified locally, i.e. those where the version in the working copy differs from the repository
version. This helps the developer to get an overview on updated FBR packages before writing
the changes to the repo. A possible output is:
$ fbr-make version-changes
Executing plugin version-changes
Package version changes
KAMAILIO: 4.0.5 --> 4.1.1
Here you can see that the package kamailio in FBR was updated from version 4.0.5 to
version 4.1.1.
4.24.6. Changing The FBR Configuration
Reconfiguration Of The FBR
By using fbr-make buildroot-menuconfig it is possible to select the FBR packages to be
compiled. This is useful if you want to compile other FBR packages for the fli4l that are not
enabled by default but are integrated in the uClibc buildroot, or if you want to activate own
FBR packages. On the other other hand global properties of FBR may be changed, such as
the version of the used GCC compiler. On successful exit of the configuration menu, the new
configuration is saved in the directory src/fbr/buildroot/.config.
Please note, however, that such changes of the toolchain configuration are not
officially supported because the resulting binaries will be incompatible with the
official fli4l distribution with a high probability. So if you need binaries for your
own OPT and want to publish this OPT, you should not change the toolchain
settings!
248