Dokumentacja

No Linux or Mac Drivers for Skype Phones? What are They Thinking?
The BeerFiles: "However, I've hit a telecommunications snag and, judging by the free flow of angst pervading all of the Linux forums I've visited, I'm not alone in my disgust..."

Why Open Source and Open Innovation Has to Be Taken More Seriously
The Sydney Morning Herald: "But talk about the merits of 'open vs closed' business models has reached fever pitch in the last week with Google announcing its OpenSocial platform--a web application sharing agreement between the biggest social networking sites..."

The Failure of Open Source Business Advocacy
(Josef|Youssef) Assad... Or Perhaps Not: "The advancing stature of open source in the enterprise is unquestionable..."

Overcoming Social Inertia
Free Software Foundation: "15 years have passed since the combination of GNU and Linux first made it possible to use a PC in freedom. During that time, we have come a long way..."

Constructing the Bazaar
SnapLogic: "The open-source development model can can be powerful and incredibly beneficial for any software development project. Yet, even most open-source projects do not follow this style of development..."

next: building busybox up: making linux installation disks previous: first preparation contents

building uclibc

the trickiest part to get right is probably the c library, especially because we want to use shared libraries. the space savings are tremendous and once this is done right, you can fit many more utilities on a diskette. the directory where the shared libraries exist on the target system (where they will be used) is different from the directory where they exist on the host system. without special tricks, the binaries that are compiled with uclibc won't run on the host system.

first create the following subdirectories under the myboot directory.

uclibc-dev is the directory that contains everything you need to compile programs with uclibc. it contains the include files for the uclibc library and special versions of gcc and similar programs. in fact it is a kind of cross-compiler, albeit for the same processor architecture.
rootfs is the directory where everything goes that will be on your bootable diskette.

next cd into the myboot/uclibc-0.9.20 directory. there run the following command:

 make menuconfig

next set the following configuration options in the menu:

target architecture features and options: set target cpu to 486 and leave the rest at the defaults. do not forget to set the correct kernel source. fill in $(myboot)/linux-2.4.21. myboot must be in normal (round) parentheses.
general library settings: disable support for global constructors and destructors and profiling, leave the rest at the defaults.
networking support: enable rpc support, it's useful for nfs mounts.
library installation options. this it the trickiest part.
- set shared library loader path (first item) to /lib. this is the libraries will be loaded on the target diskette, so any prefix must be left out.
- set uclibc environment directory (second item) to
  $(myboot)/uclibc-dev. this is where all files will end up that are needed by the c compiler when compiling and linking programs with uclibc.

run the following commands to make and install the library. note that we do not install the library as root as we do not install it in a system-wide directory.

 make make install make prefix=$myboot/rootfs install_target

the first command compiles the libraries, the second command installs the development code into the uclibc-dev directory and the last command installs the shared libraries into the rootfs directory. these will end up on the root file system of the bootable diskette.

compiling with uclibc can be as simple as putting the uclibc-dev directory first in your path and just running make. note that you cannot run the programs you have just made on the host system.

next: building busybox up: making linux installation disks previous: first preparation contents

lennart benschop 2003-07-16

Linux FAQ's & Manuals

building uclibc