staticbuild: Fully static binaries build - GNU/Linux vendor independence

There exists too many GNU/Linux distributions - vendors - and any produced binary is not compatible with all of them due to the shared libraries and configuration files dependencies. Due to many hardcoded shared libraries it is no longer possible to just use gcc -static. These patches provide the functionality you would expect from: gcc -static

This static build framework is based on Fedora Core 4 (SRPMS and SRPMS updates). In fact it is not important which distribution the static build is based on as the final binaries should run on any GNU/Linux system vendor/version. Just I decided for Fedora Core.

You must use the same package versions on the main (dynamic) build system as the static libraries are built for! Therefore you must use Fedora Core 4 if using the unchanged sources or even the binaries provided here.

This static build does not provide threading - neither POSIX threads nor LinuxThreads. I did not need it anywhere and it gets everything simpler and smaller this way.

You should build your sources statically (using automake(1) --enable-static) although without gcc -static. As the last step you should relink the binaries against this staticbuild libraries by hand - it is not much possible to convince automake(1) to properly relink it the minized way for you. Check the 'build-static' script for an example.

This package has been used in its current or former versions for my projects:

• Captive: The first free NTFS read/write filesystem for GNU/Linux
• udpgate: UDP packets gateway

EOF