From 9039109dadedca9910280eea7870fe82253c842c Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Mon, 27 Dec 2004 19:28:55 +0000 Subject: Update FAQ, remove references to 'toolchain' and instead emphasize 'buildroot', which can do everything 'toolchain' could do and then some. And is actively maintained. -Erik --- docs/uclibc.org/FAQ.html | 106 +++++++++++++++++++++++++++-------------------- 1 file changed, 62 insertions(+), 44 deletions(-) (limited to 'docs') diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html index a28f2569a..c8d136f52 100644 --- a/docs/uclibc.org/FAQ.html +++ b/docs/uclibc.org/FAQ.html @@ -228,27 +228,29 @@ How could it be smaller and not suck? of GNU binutils, the gcc compiler, and uClibc, all built to produce binaries linked with uClibc for your target system. - You can build your own native uClibc toolchain using the uClibc - toolchain builder from - uClibc toolchain builder, - or the uClibc buildroot system from + You can build your own native uClibc toolchain using the uClibc buildroot system. +

To build your own uClibc toolchain, follow the following simple steps:

@@ -260,13 +262,17 @@ How could it be smaller and not suck? Yes, you really do need to build a toolchain to produce uClibc binaries. We used to provide a toolchain wrapper, but that has been removed due to numerous problems. The uClibc developers have gone to a lot of trouble - to produce a - uClibc toolchain builder, - and the + to produce the uClibc buildroot system, - which make it easy to build your own uClibc toolchain. Feel free to take - the gcc and binutils patches we provide and use them in your own toolchain - build system. + which makes it easy to build your own uClibc toolchain and/or an initial + uClibc based system. + +

+ Feel free to take the gcc and binutils patches we provide and use them in + your own toolchain build system. If you choose to use your own toolchain + build system, you will need to use these patches since the upstream GNU + binutils and gcc releases do not currently have full support for building a + uClibc toolchain.

@@ -277,12 +283,18 @@ How could it be smaller and not suck? It is possible in some limited cases to re-use an existing glibc toolchain and subvert it into building uClibc binaries by using gcc commands such as "-nostdlib" and "-nostdinc". In fact, this used to be the recommended - method for compiling programs with uClibc using a uClibc toolchain wrapper. + method for compiling programs with uClibc, and we made this easy to do by + providing a uClibc toolchain wrapper, which attempted to automagically subvert + an existing glibc toolchain. + +

+ This toolchain wrapper was removed from uClibc 0.9.22, and it will not be - coming back. This is because it is impossible to fully subvert an existing - toolchain in many cases. As uClibc has become more capable the many problems - with re-using an existing glibc toolchain led us to conclude that the only - safe and sane way to build uClibc binaries is to use a uClibc toolchain. + coming back. This is because it proved impossible to completely subvert an + existing toolchain in many cases, and therefore proved to be a real + maintainence burder. As uClibc became more capable, the many problems with + re-using an existing glibc toolchain led us to conclude that the only safe + and sane way to build uClibc binaries was to use a uClibc toolchain.

@@ -296,41 +308,47 @@ How could it be smaller and not suck?

Is a pre-compiled uClibc development system available?

- If you want to be really lazy and start using uClibc right - away without needing to compile your own toolchain or anything, you can - grab a copy of the uClibc development systems, currently available for + If you want to be really lazy and start using uClibc right away + without needing to compile your own toolchain or anything, you can grab a + pre-compiled uClibc development system. These are currently available for + i386, powerpc, arm, mips, mipsel, and sh4. - The powerpc dev system mostly works, but there is still some sortof - problem with the shared library loader that has not yet been resolved.

- These are pre-built uClibc only development systems (created using - buildroot), and provide a - really really easy way to get started. These are about bzip2 compressed - ext2 filesystems containing all the development software you need to build - your own uClibc applications. With bash, awk, make, gcc, g++, autoconf, - automake, ncurses, zlib, openssl, openssh, gdb, strace, busybox, GNU - coreutils, GNU tar, GNU grep, etc, these should have pretty much everything - you need to get started building your own applications linked against - uClibc. You can boot into them, loop mount them, dd them to a spare drive - and use resize2fs to make them fill a partition... Whatever works best for + + Each of these uClibc development systems was created using + buildroot). + +

+ + These are bzip2 compressed ext2 filesystems containing all the development + software you need to build your own uClibc applications, including: bash, awk, + make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh, gdb, + strace, busybox, GNU coreutils, GNU tar, GNU grep, etc. + +

+ + This should be pretty much everything you need to get started building your + own applications with uClibc. Once you download one of these systems, you + can then boot into it, loop mount it, dd it to a spare drive and use a tool + such as resize2fs to make it fill a partition... Whatever works best for you.

The quickest way to get started using a root_fs image (using the i386 platform as an example) is:

Type "exit" to end the chroot session and return to the host system.

-- cgit v1.2.3