diff options
| author | Mike Frysinger <vapier@gentoo.org> | 2007-04-17 13:11:21 +0000 |
|---|---|---|
| committer | Mike Frysinger <vapier@gentoo.org> | 2007-04-17 13:11:21 +0000 |
| commit | 557eef285f38cdc5a3d7a4c8b7d0d5182193ea2e (patch) | |
| tree | 354947039b560c64faafdb667c7281a167d27eae /docs | |
| parent | 76a888bead02ab125898c4402805d071d93a9266 (diff) | |
move uclibc.org out of actual source tree
Diffstat (limited to 'docs')
27 files changed, 0 insertions, 2642 deletions
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html deleted file mode 100644 index a21e2bdcb..000000000 --- a/docs/uclibc.org/FAQ.html +++ /dev/null @@ -1,693 +0,0 @@ -<!--#include file="header.html" --> - - -<h3>Frequently Asked Questions</h3> - -This is a collection of some of the most frequently asked questions -about uClibc. Some of the questions even have answers. If you -have additions to this FAQ document, we would love to add them, - -<ol> -<li><a href="#naming">Why is it called uClibc?</a> -<li><a href="#platforms">What platforms does uClibc run on?</a> -<li><a href="#why">Why are you doing this? What's wrong with glibc?</a> -<li><a href="#doesnt_suck">So uClibc is smaller then glibc? Doesn't that mean it - completely sucks? How could it be smaller and not suck?</a> -<li><a href="#why_should_i">Why should I use uClibc?</a> -<li><a href="#licensing">If I use uClibc, do I have to release all my source code to the world for - free? I want to create a closed source commercial application and I want - to protect my intellectual property.</a> -<li><a href="#development">Can I use it on my x86 development system?</a> -<li><a href="#shared"> Does uClibc support shared libraries?</a> -<li><a href="#compiling">How do I compile programs with uClibc?</a> -<li><a href="#toolchain">Do I really need to build a uClibc toolchain?</a> -<li><a href="#wrapper">What happened to the old toolchain wrapper?</a> -<li><a href="#dev_systems">Is a pre-compiled uClibc development system available?</a> -<li><a href="#bugs">I think I found a bug in uClibc! What should I do?!</a> -<li><a href="#miscompile">My package builds fine but link fails with errors like "undefined reference - to __fputc_unlocked", who do I blame?!</a> -<li><a href="#gnu_malloc">My package builds fine but link fails with errors like "undefined reference - to rpl_realloc / rpl_malloc", who do I blame?!</a> -<li><a href="#job_control">Why do I keep getting "sh: can't access tty; job control - turned off" errors? Why doesn't Control-C work within my shell?</a> -<li><a href="#autoconf">How do I make autoconf and automake behave?</a> -<li><a href="#ldd">When I run 'ldd' to get a list of the library dependencies - for a uClibc binary, ldd segfaults! What should I do?</a> -<li><a href="#timezones">Why does localtime() return times in UTC even when I have my timezone set?</a> -<li><a href="#history">What is the history of uClibc? Where did it come from?</a> -<li><a href="#demanding">I demand that you to add <favorite feature> right now! How come - you don't answer all my questions on the mailing list instantly? I demand - that you help me with all of my problems <em>Right Now</em>!</a> -<li><a href="#helpme">I need help with uClibc! What should I do?</a> -<li><a href="#contracts">I need you to add <favorite feature>! Are the uClibc developers willing to - be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide - support contracts?</a> -<li><a href="#support">I think you guys are great and I want to help support your work!</a> - - -</ol> - - -<hr /> -<p> -<h2><a name="naming">Why is it called uClibc?</a></h2> -<p> - - The letter 'u' is short for µ (the greek letter "mu"). µ is commonly used - as the abbreviation for the word "micro". The capital "C" is short for - "controller". So the name uClibc is sortof an abbreviation for "the - microcontroller C library". For simplicity, uClibc is pronounced - "yew-see-lib-see". - <p> - The name is partly historical, since uClibc was originally - created to support <a href="http://www.uclinux.org">µClinux</a>, a port of - Linux for MMU-less microcontrollers such as the Dragonball, Coldfire, and - ARM7TDMI. These days, uClibc also works just fine on normal Linux systems - (such as i386, ARM, and PowerPC), but we couldn't think of a better name. - -<hr /> -<p> -<h2><a name="platforms">What platforms does uClibc run on?</a></h2> -<p> - - - Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300, - m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors. - - -<hr /> -<p> -<h2><a name="why">Why are you doing this? What's wrong with glibc?</a></h2> -<p> - - Initially, the project began since the GNU C library lacked support for - MMU-less systems, and because glibc is very large. The GNU C library is - designed with a very different set of goals then uClibc. The GNU C library - is a great piece of software, make no mistake. It is compliant with just - about every standard ever created, and runs on just about every operating - system and architecture -- no small task! But there is a price to be paid - for that. It is quite a large library, and keeps getting larger with each - release. It does not even pretend to target embedded systems. To quote - from Ulrich Drepper, the maintainer of GNU libc: "...glibc is not the right - thing for [an embedded OS]. It is designed as a native library (as opposed - to embedded). Many functions (e.g., printf) contain functionality which is - not wanted in embedded systems." 24 May 1999 - - - -<hr /> -<p> -<h2><a name="doesnt_suck">So uClibc is smaller then glibc? Doesn't that mean it completely sucks? -How could it be smaller and not suck?</a></h2> -<p> -<p> - - uClibc and glibc have different goals. glibc strives for features - and performance, and is targeted for desktops and servers with - (these days) lots of resources. It also strives for ABI stability. - - <p> - - On the other hand, the goal of uClibc is to provide as much functionality - as possible in a small amount of space, and it is intended primarily for - embedded use. It is also highly configurable in supported features, at the - cost of ABI differences for different configurations. uClibc has been - designed from the ground up to be a C library for embedded Linux. We don't - need to worry about things like MS-DOS support, or BeOS, or AmigaOs any - other system. This lets us cut out a lot of complexity and very carefully - optimize for Linux. - - <p> - - In other cases, uClibc leaves certain features (such as full C99 Math - library support, wordexp, IPV6, and RPC support) disabled by default. - Those features can be enabled for people that need them, but are otherwise - disabled to save space. - - <p> - - Some of the space savings in uClibc is obtained at the cost of performance, - and some is due to sacrificing features. Much of it comes from aggressive - refactoring of code to eliminate redundancy. In regards to locale data, - elimination of redundant data storage resulted in substantial space - savings. The result is a libc that currently includes the features needed - by nearly all applications and yet is considerably smaller than glibc. To - compare "apples to apples", if you take uClibc and compile in locale data - for about 170 UTF-8 locales, then uClibc will take up about 570k. If you - take glibc and add in locale data for the same 170 UTF-8 locales, you will - need over 30MB!!! - - <p> - - The end result is a C library that will compile just about everything you - throw at it, that looks like glibc to application programs when you - compile, and is many times smaller. - - -<hr /> -<p> -<h2><a name="why_should_i">Why should I use uClibc?</a></h2> -<p> - - I don't know if you should use uClibc or not. It depends on your needs. - If you are building an embedded Linux system and you are tight on space, then - using uClibc instead if glibc may be a very good idea. - - <p> - - If you are building an embedded Linux system and you find that - glibc is eating up too much space, you should consider using - uClibc. If you are building a huge fileserver with 12 Terabytes - of storage, then using glibc may make more sense. Unless, for - example, that 12 Terabytes will be Network Attached Storage and - you plan to burn Linux into the system's firmware... - - - -<hr /> -<p> -<h2><a name="licensing">If I use uClibc, do I have to release all my source code to the world for - free? I want to create a closed source commercial application and I want - to protect my intellectual property.</a></h2> -<p> - - No, you do not need to give away your application source code just because - you use uClibc and/or run on Linux. uClibc is licensed under the <a - href="http://www.gnu.org/copyleft/lesser.html">Lesser GPL</a> license, just - like the GNU C library (glibc). Please read this license, or have a lawyer - read this license if you have any questions. Here is my brief summary... - Using shared libraries makes complying with the license easy. You can - distribute a closed source application which is linked with an unmodified - uClibc shared library. In this case, you do not need to give away any - source code for your application. Please consider sharing some of the - money you make with us! :-) - <p> - - If you make any changes to uClibc, and distribute uClibc or distribute any - applications using your modified version, you must also distribute the - source code for uClibc containing all of your changes. - <p> - - If you distribute an application which has uClibc statically linked, you - must also make your application available as an object file which can later - be re-linked against updated versions of uClibc. This will (in theory) - allow your customers to apply uClibc bug fixes to your application. You do - not need to make the application object file available to everyone, just to - those you gave the fully linked application. - - -<hr /> -<p> -<h2><a name="development">Can I use it on my x86 development system?</a></h2> -<p> - - Sure! In fact, this can be very nice during development. By - installing uClibc on your development system, you can be sure that - the code you are working on will actually run when you deploy it on - your target system. - - - -<hr /> -<p> -<h2><a name="shared"> Does uClibc support shared libraries?</a></h2> -<p> - - Yes. uClibc has native shared library support on i386, ARM, mips, - SH, CRIS, and PowerPC processors. Other architectures can use shared - libraries but will need to use the GNU libc shared library loader. - <p> - Shared Libraries are not currently supported by uClibc on MMU-less systems. - <a href="http://www.snapgear.com/">SnapGear</a> has implemented - shared library support for MMU-less systems, however, so if you need MMU-less - shared library support they may be able to help. - - -<hr /> -<p> -<h2><a name="compiling">How do I compile programs with uClibc?</a></h2> -<p> - - You will need to have your own uClibc toolchain. A toolchain consists - of <a href="http://sources.redhat.com/binutils/">GNU binutils</a>, - <a href="http://gcc.gnu.org/">the gcc compiler</a>, and uClibc, all - built to produce binaries for your target system linked with uClibc. - You can build your own native uClibc toolchain using the - <a href="http://buildroot.uclibc.org/">uClibc buildroot system</a>. - - <p> - To build your own uClibc toolchain, follow the following simple - steps: - <ul> - <li> Point your web browser <a href="http://buildroot.uclibc.org/">here</a>, - <li> Download of copy of buildroot - <li> Unpack the tarball on your Linux system somewhere - <li> Edit the Makefile as needed if you wish to change anything. - <li> run 'unset CC'. Then run 'unset CXX'. Some Linux systems - (i.e. Gentoo) set variables such as 'CC' in the system environment - which really messes things up when cross compiling. - <li> run 'make menuconfig' - <li> Select the things you want to build. If you <em>only</em> want a - toolchain, leave everything except the toolchain disabled. - <li> save your buildroot configuration. - <li> run 'make' - <li> go eat a nice wholesome sandwich, drink a pop, call a friend, - play a video game, and generally find something to do. While you - are waiting, buildroot will download all the needed source code and - then compile things up for you. - <li> You should now have a shiny new toolchain, and maybe even a shiny - new uClibc based root filesystem or development system, depending on - the options you selected. - </ul> - -<hr /> -<p> -<h2><a name="toolchain">Do I really need to build a uClibc toolchain?</a></h2> -<p> - - 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 the - <a href="http://buildroot.uclibc.org/">uClibc buildroot system</a>, - which makes it easy to build your own uClibc toolchain and/or an initial - uClibc based system. - - <p> - 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. - - -<hr /> -<p> -<h2><a name="wrapper">What happened to the old toolchain wrapper?</a></h2> -<p> - - 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, and we made this easy to do by - providing a uClibc toolchain wrapper, which attempted to automagically subvert - an existing glibc toolchain. - - <p> - - This toolchain wrapper was removed from uClibc 0.9.22, and it will not be - 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. - - <p> - - Some discussion on the reasoning behind this decision can be found here: - <a href="http://www.uclibc.org/lists/uclibc/2003-October/007315.html"> - http://www.uclibc.org/lists/uclibc/2003-October/007315.html</a> - in the uClibc mailing list archives. - -<hr /> -<p> -<h2><a name="dev_systems">Is a pre-compiled uClibc development system available?</a></h2> -<p> - - If you want to be <em>really</em> 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 - - <a href="http://www.uclibc.org/downloads/root_fs_arm.ext2.bz2">arm</a>, - <a href="http://www.uclibc.org/downloads/root_fs_armeb.ext2.bz2">armeb</a>, - <a href="http://www.uclibc.org/downloads/root_fs_i386.ext2.bz2">i386</a>, - <a href="http://www.uclibc.org/downloads/root_fs_mips.ext2.bz2">mips</a>, - <a href="http://www.uclibc.org/downloads/root_fs_mipsel.ext2.bz2">mipsel</a>, - <a href="http://www.uclibc.org/downloads/root_fs_powerpc.ext2.bz2">powerpc</a>, and - <a href="http://www.uclibc.org/downloads/root_fs_sh4.ext2.bz2">sh4</a>. - - <p> - - 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. - - <p> - - Each of these uClibc development systems was created using - <a href="http://buildroot.uclibc.org/">buildroot</a>. - - <p> - - These development systems should provide 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. - - <p> - The quickest way to get started using a root_fs image (using the i386 - platform as an example) is: - <ul> - <li>Download root_fs_i386.bz2 from uclibc.org</li> - <li>bunzip2 root_fs_i386.bz2</li> - <li>mkdir root_fs</li> - <li>su root</li> - <li>mount -o loop root_fs_i386 root_fs</li> - <li>chroot root_fs /bin/su -</li> - </ul> - Type "exit" to end the chroot session and return to the host system. - <p> - - - -<hr /> -<p> -<h2><a name="bugs">I think I found a bug in uClibc! What should I do?</a></h2> -<p> - - If you find a problem with uClibc, please submit a detailed bug report to - the uClibc mailing list at <a href="mailto:uclibc@mail.uclibc.org"> - uclibc@mail.uclibc.org</a>. Please do not send private email to Erik - (the maintainer of uClibc) asking for private help unless you are planning - on paying for consulting services. When we answer questions on the uClibc - mailing list, it helps everyone, while private answers help only you... - - A well-written bug report should include an example that demonstrates the - problem behaviors and enables anyone else to duplicate the bug on their own - machine. For larger applications where it may prove difficult to provide - an example application, we recommend that you use a tool such as gdb, - strace, ltrace, and or valgrind to create a logfile showing the problem - behavior. - - -<hr /> -<p> -<h2><a name="miscompile">My package builds fine but link fails with errors like - "undefined reference to __fputc_unlocked", who do I blame?!</a></h2> -<p> - - This error crops up when a build system mixes system headers (say glibc) - with the target headers (say uClibc). Make sure your build system is not - including extraneous include options (-I) and double check that it is using - the correct compiler. Many build systems incorrectly force things like - -I/usr/include or -I/usr/local/include or -I${prefix}/include (which usually - just expands to -I/usr/include). - - -<hr /> -<p> -<h2><a name="gnu_malloc">My package builds fine but link fails with errors like "undefined reference - to rpl_realloc / rpl_malloc", who do I blame?!</a></h2> -<p> - - This error crops up because you didn't enable MALLOC_GLIBC_COMPAT support. - Configure scripts detect whether your libc supports "GNU malloc" features by - seeing whether malloc(0) returns NULL (glibc malloc(0) will return a non NULL - pointer). uClibc defaults to malloc(0) returning NULL so autoconf will assume - malloc from your libc sucks and procede to try and compile the malloc replacement - version in the gnulib addon. However, since not many packages include gnulib, - they will fail to link with rpl_realloc / rpl_malloc errors. You could force - configure to assume working behavior by exporting the variables 'jm_cv_func_working_malloc' - (older autoconf) and 'ac_cv_func_malloc_0_nonnull' (newer autoconf) to 'yes' - before running `./configure`. - - -<hr /> -<p> -<h2><a name="job_control">Why do I keep getting "sh: can't access tty; job control - turned off" errors? Why doesn't Control-C work within my shell?</a></h2> -<p> - - This isn't really a uClibc question, but I'll answer it here anyways. Job - control will be turned off since your shell can not obtain a controlling - terminal. This typically happens when you run your shell on /dev/console. - The kernel will not provide a controlling terminal on the /dev/console - device. Your should run your shell on a normal tty such as tty1 or ttyS0 - and everything will work perfectly. If you <em>REALLY</em> want your shell - to run on /dev/console, then you can hack your kernel (if you are into that - sortof thing) by changing drivers/char/tty_io.c to change the lines where - it sets "noctty = 1;" to instead set it to "0". I recommend you instead - run your shell on a real console... - - -<hr /> -<p> -<h2><a name="autoconf">How do I make autoconf and automake behave?</a></h2> -<p> - - When you are cross-compiling, autoconf and automake are known to behave - badly. This is because a large number of configure scripts (such as the - one from openssh) try to actually execute applications that were cross - compiled for your target system. This is bad, since of course these won't - run, and this will also prevent your programs from compiling. You need to - complain to the authors of these programs and ask them to fix their broken - configure scripts. - - -<hr /> -<p> -<h2><a name="ldd">When I run 'ldd' to get a list of the library dependencies - for a uClibc binary, ldd segfaults! What should I do?</a></h2> -<p> - - Use the ldd that is built by uClibc, not your system's one. You can build - uClibc'd ldd for your host system by going into the uClibc/utils/ directory - in the uClibc source and running 'make ldd.host'. - <p> - - When your system's ldd looks for library dependencies, it actually _runs_ - that program. This works fine -- usually. It generally will not work at - all when you have been cross compiling (which is why ldd segfaults). The - ldd program created by uClibc is cross platform and doesn't mind at all if - it cannot execute the target program. If you use the uClibc version of - 'ldd', it will do the right thing and produce correct results, even when it - is used on cross compiled binaries. - - -<hr /> -<p> -<h2><a name="timezones">Why does localtime() return times in UTC even when I have my timezone set?</a></h2> -<p> - - - The uClibc time functions get timezone information from the TZ environment - variable, as described in the Single Unix Specification Version 3. See - <a href="http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html"> - http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html</a> - for details on valid settings of TZ. For some additional examples, read - <a href="http://www.uclibc.org/lists/uclibc/2002-August/004010.html"> - http://www.uclibc.org/lists/uclibc/2002-August/004010.html</a> in the uClibc - mailing list archive. - You can store the value of TZ in the file '/etc/TZ' and uClibc will then - automagically use the specified setting. - - -<hr /> -<p> -<h2><a name="history">What is the history of uClibc? Where did it come from?</a></h2> -<p> - - - uClibc started off as a fork on the <a - href="http://www.cix.co.uk/~mayday/">Linux-8086 C library</a>, which is - part of the <a href="http://www.elks.ecs.soton.ac.uk/">elks project</a>. - The Linux-8086 C library was, apparently, largely written from scratch but - also borrowed code from libc4, glibc, some Atari library code, with bits - and pieces from about 20 other places. - - <p> - - I had for some time been despairing over the state of C libraries in Linux. - GNU libc, the standard, is very poorly suited to embedded systems and has - been getting bigger with every release. I spent quite a bit of time - looking over the available Open Source C libraries that I knew of, and none - of them really impressed me. I felt there was a real vacancy in the - embedded Linux ecology. The closest library to what I imagined an embedded - C library should be was uClibc. But it had a lot of problems too -- not - the least of which was that, traditionally, uClibc required a complete - source tree fork in order to support each and every new platform. This - resulted in a big mess of twisty versions, all different. I decided to fix - it and the result is what you see here. - - <p> - - To start with, (with some initial help from <a - href="http://www.uclinux.org/developers/">D. Jeff Dionne</a>), I ported - uClibc to run on i386. I then grafted in the header files from glibc and - cleaned up the resulting breakage. This (plus some additional work) has - made it much less dependant on kernel headers, a large departure from its - traditional tightly-coupled-to-the-kernel origins. I have written and/or - rewritten a number of things that were missing or broken, and sometimes - grafted in bits of code from the current glibc and libc5. I have also - added a proper configuration system which allows you to easily select your - target architecture and enable and disable various features. Many people - have helped by testing, contributing ports to new architectures, and adding - support for missing features. - - <p> - - In particular, around the end of 2000, Manuel Novoa III got involved with - uClibc. One of his first contributions was the original gcc wrapper (which - has since been removed). Since then, he has written virtually all of the - current uClibc stdio, time, string, ctype, locale, and wchar-related code, - as well as much of stdlib and various other bits throught the library. - - <p> - - These days, uClibc is being developed and enhanced by Erik Andersen - and Manuel Novoa III of - <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> - along with the rest of the embedded Linux community. - - - -<hr /> -<p> -<h2><a name="demanding">I demand that you to add <favorite feature> right now! How come - you don't answer all my questions on the mailing list instantly? I demand - that you help me with all of my problems <em>Right Now</em>!</a></h2> -<p> - - You have not paid us a single cent and yet you still have the - product of several years of work from Erik and Manuel and - many other people. We are not your slaves! We work on uClibc - because we find it interesting. If you go off flaming us, we will - ignore you. - - - -<hr /> -<p> -<h2><a name="helpme">I need help with uClibc! What should I do?</a></h2> -<p> - - If you find that you need help with uClibc, you can ask for help on the - uClibc mailing list at uclibc@mail.uclibc.org. In addition to the uClibc - mailing list, Erik and Manuel are also known to sometimes hang out on the - uClibc IRC channel: #uclibc on irc.freenode.net. - - <p> - - <b>Please do not send private email to Erik and/or Manuel asking for - private help unless you are planning on paying for consulting services.</b> - When we answer questions on the uClibc mailing list, it helps everyone - since people with similar problems in the future will be able to get help - by searching the mailing list archives. Private help is reserved as a paid - service. If you need to use private communication, or if you are serious - about getting timely assistance with uClibc, you should seriously consider - paying for consulting time. - - <p> - - - -<hr /> -<p> -<h2><a name="contracts">I need you to add <favorite feature>! Are the uClibc developers willing to - be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide - support contracts?</a></h2> -<p> - - Sure! Now you have our attention! What you should do is contact <a - href="mailto:andersen@codepoet.org">Erik Andersen</a> of <a - href="http://codepoet-consulting.com/">CodePoet Consulting</a> to bid - on your project. If Erik is too busy to personally add your feature, there - are several other active uClibc contributors who will almost certainly be able - to help you out. Erik can contact them and ask them about their availability. - - -<hr /> -<p> -<h2><a name="support">I think you guys are great and I want to help support your work!</a></h2> -<p> - - Wow, that would be great! You can click here to help support uClibc and/or request features. - - <!-- Begin PayPal Logo --> - <center> - <form action="https://www.paypal.com/cgi-bin/webscr" method="post"> - <input type="hidden" name="cmd" value="_xclick"> - <input type="hidden" name="business" value="andersen@codepoet.org"> - <input type="hidden" name="item_name" value="Support uClibc and/or request features"> - <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png"> - <input type="hidden" name="no_shipping" value="1"> - <input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal"> - </form> - </center> - <!-- End PayPal Logo --> - - If you prefer to contact us directly for payments, hardware donations, - support requests, etc., you can contact - <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> here. - -<hr /> - -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> - -<!--#include file="footer.html" --> - diff --git a/docs/uclibc.org/about.html b/docs/uclibc.org/about.html deleted file mode 100644 index 51f261b39..000000000 --- a/docs/uclibc.org/about.html +++ /dev/null @@ -1,99 +0,0 @@ -<!--#include file="header.html" --> - - -<!-- Begin Introduction section --> - -<h3>A C library for embedded Linux</h3> - -uClibc (aka µClibc/pronounced yew-see-lib-see) is a C library for developing -embedded Linux systems. It is much smaller than the <a -href="http://www.gnu.org/software/libc/libc.html">GNU C Library</a>, but nearly -all applications supported by glibc also work perfectly with uClibc. Porting -applications from glibc to uClibc typically involves just recompiling the -source code. uClibc even supports shared libraries and threading. It currently -runs on <a href="http://kernel.org/">standard Linux</a> and <a -href="http://www.uclinux.org">MMU-less (also known as µClinux)</a> systems with -support for alpha, ARM, cris, i386, i960, h8300, m68k, mips/mipsel, PowerPC, -SH, SPARC, and v850 processors. - -<p> - -If you are building an embedded Linux system and you find that -glibc is eating up too much space, you may want to consider using -uClibc. If you are building a huge fileserver with 12 Terabytes -of storage, then using glibc may make more sense. Unless, for -example, that 12 Terabytes will be Network Attached Storage and -you plan to burn Linux into the system's firmware... - -<p> - -uClibc is maintained by <a href= -"http://codepoet.org/andersen/erik/erik.html">Erik Andersen</a> -and is licensed under the -<a href="http://www.gnu.org/copyleft/lesser.html">GNU LESSER GENERAL PUBLIC LICENSE</a> -. This license allows you to make closed source commercial applications using -uClibc. (Please consider sharing some of the money you make ;-). You do not need -to give away all your source code just because you use uClibc and/or run on Linux. -See the <a href="FAQ.html">list of Frequently Asked Questions</a> for details. - -<p> - -<h3>Sponsors</h3> - -Please visit our sponsors and thank them for their -support! They have provided money for equipment and -bandwidth. Next time you need help with a project, -consider these fine companies! - - -<ul> - <li><a href="http://www.penguru.net">Penguru Consulting</a><br> - Custom development for embedded Linux systems and multimedia platforms - </li> - - <li><a href="http://opensource.se/">opensource.se</a><br> - Embedded open source consulting in Europe. - </li> - - <li><a href="http://www.codepoet-consulting.com">Codepoet Consulting</a><br> - Custom Linux, embedded Linux, BusyBox, and uClibc - development. - </li> - -</ul> - -If you wish to be a sponsor, or if you have already contributed and would like -your name added here, email <a href= "mailto:andersen@codepoet.org">Erik</a>. - -<p> -<table BORDER=0> -<tr> -<td> -Do you like uClibc? Do you need support? Do you need some features -added? Then why not help out? We are happy to accept donations -(such as bandwidth, mirrors sites, and hardware for the various -architectures). We can also provide support contracts, and implement -funded feature requests. To contribute, you can either click on the -Donate image to donate using PayPal, or you can contact Erik at -<a href="http://codepoet-consulting.com/">CodePoet Consulting</a> -(we have a credit card machine so you can avoid PayPal if you wish). -</td> - -<td> -<!-- Begin PayPal Logo --> -<form action="https://www.paypal.com/cgi-bin/webscr" method="post"> - <input type="hidden" name="cmd" value="_xclick"> - <input type="hidden" name="business" value="andersen@codepoet.org"> - <input type="hidden" name="item_name" value="Support uClibc"> - <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png"> - <input type="hidden" name="no_shipping" value="1"> - <input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal"> -</form> -</td> -<!-- End PayPal Logo --> - -</tr> -</table> - - -<!--#include file="footer.html" --> diff --git a/docs/uclibc.org/copyright.txt b/docs/uclibc.org/copyright.txt deleted file mode 100644 index 8fa3d612a..000000000 --- a/docs/uclibc.org/copyright.txt +++ /dev/null @@ -1,29 +0,0 @@ - -The code and graphics on this website (and it's mirror sites, if any) are -Copyright (c) 1999-2007 by Erik Andersen. All rights reserved. - -Documents on this Web site including their graphical elements, design, and -layout are protected by trade dress and other laws and MAY BE COPIED OR -IMITATED IN WHOLE OR IN PART. THIS WEBSITE IS LICENSED FREE OF CHARGE, THERE -IS NO WARRANTY FOR THE WEBSITE TO THE EXTENT PERMITTED BY APPLICABLE LAW. -SHOULD THIS WEBSITE PROVE DEFECTIVE, YOU MAY ASSUME THAT SOMEONE MIGHT GET -AROUND TO SERVICING, REPAIRING OR CORRECTING IT SOMETIME WHEN THEY HAVE NOTHING -BETTER TO DO. REGARDLESS, YOU GET TO KEEP BOTH PIECES. - -IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY -COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THIS -WEBSITE AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR -INABILITY TO USE THIS WEBSITE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR -LOSS OF HAIR, LOSS OF LIFE, LOSS OF MEMORY, LOSS OF YOUR CARKEYS, MISPLACEMENT -OF YOUR PAYCHECK, OR COMMANDER DATA BEING RENDERED UNABLE TO ASSIST THE -STARFLEET OFFICERS ABORD THE STARSHIP ENTERPRISE TO RECALIBRATE THE MAIN -DEFLECTOR ARRAY, LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE -WEBSITE TO OPERATE WITH YOUR WEBBROWSER), EVEN IF SUCH HOLDER OR OTHER PARTY -HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - -You have been warned. - -You can contact the webmaster at <andersen@codepoet.org> if you have some sort -of problem with this. - diff --git a/docs/uclibc.org/developer.html b/docs/uclibc.org/developer.html deleted file mode 100644 index 0bf1b070a..000000000 --- a/docs/uclibc.org/developer.html +++ /dev/null @@ -1,56 +0,0 @@ -<!--#include file="header.html" --> - - -<h3>Subversion Read/Write Access</h3> - -To obtain commit access, you will need to demonstrate you are serious by -submitting a few good patches first. Then, you will need to select a username -to use when committing changes to SVN, you will need to send me the username -you have selected, you must send me your preferred contact email address, and -finally, you must send me an ssh version 2 DSA key with 1024 bits (the default) -or more. If you do not currently have an ssh version 2 DSA key, you can -generate a key using the command<pre>ssh-keygen -t dsa</pre> This will -create the files <pre>/home/<USERNAME>/.ssh/id_dsa -/home/<USERNAME>/.ssh/id_dsa.pub</pre> You must then send the content -of 'id_dsa.pub' to me so I can setup your account. The content of 'id_dsa' -should of course be kept secret. - -<p> - -Note that if you would prefer to keep your communications with me -private, you can encrypt your email using my -<a href="http://www.codepoet.org/andersen/erik/gpg.asc">public key</a>. - -<p> - -Once you are setup with an account, you will need to use your account to -checkout a copy of uClibc from Subversion: - -<pre> -svn list svn+ssh://username@svn.uclibc.org/svn/trunk/uClibc</pre> -<br> -It goes without saying you must change <em>username</em> to your own -username... -<p> - -You can then enter the newly checked out uClibc directory, make changes, check -your changes, diff your changes, revert your changes, and and commit your -changes usine commands such as: - -<pre> -svn diff -svn status -svn revert -svn commit</pre> - -<p> - -For additional detail on how to use Subversion, please visit the -<a href="http://subversion.tigris.org/">the Subversion website</a>. -You might also want to read online or buy a copy of <a -href="http://svnbook.red-bean.com/">the Subversion Book</a>... - - -<!--#include file="footer.html" --> - - diff --git a/docs/uclibc.org/download.html b/docs/uclibc.org/download.html deleted file mode 100644 index 6ecbc3aca..000000000 --- a/docs/uclibc.org/download.html +++ /dev/null @@ -1,31 +0,0 @@ -<!--#include file="header.html" --> - - - -<h3>Download</h3> - -Source for the latest release can always be -downloaded from <a href="downloads/">http://www.uclibc.org/downloads</a> - -<p> -You can also obtain <a href= "downloads/snapshots/">Daily Snapshots</a> of -the latest development source tree for those wishing to follow uClibc development, -but cannot or do not wish to use Subversion (svn). - -<p> - -<ul> - <li> Click here to <a href="/cgi-bin/viewcvs.cgi/trunk/uClibc/">browse the source tree</a>. - </li> - - <li>Anonymous <a href="subversion.html">Subversion access</a> is available. - </li> - - <li>For those that are actively contributing obtaining - <a href="developer.html">Subversion read/write access</a> is also possible. - </li> - -</ul> - -<!--#include file="footer.html" --> - diff --git a/docs/uclibc.org/footer.html b/docs/uclibc.org/footer.html deleted file mode 100644 index 0f8493dad..000000000 --- a/docs/uclibc.org/footer.html +++ /dev/null @@ -1,39 +0,0 @@ -<!-- Footer --> - - - </td> - </tr> - </table> - -<hr /> - - - <table width="100%"> - <tr> - <td width="60%"> - <font face="arial, helvetica, sans-serif" size="-1"> - <a href="/copyright.txt">Copyright © 1999-2007 Erik Andersen</a> - <br> - Mail all comments, insults, suggestions and bribes to - <br> - Erik Andersen <a href="mailto:andersen@codepoet.org">andersen@codepoet.org</a><br> - </font> - </td> - - <td> - <a href="http://www.vim.org/"><img border=0 width=88 height=31 - src="images/written.in.vi.png" - alt="This site created with the vi editor"></a> - </td> - - <td> - <a href="http://osuosl.org/"><img border=0 width=114 height=63 - src="images/osuosl.png" - alt="This site is kindly hosted by OSL"></a> - </td> - - </TR> - </table> - - </body> -</html> diff --git a/docs/uclibc.org/header.html b/docs/uclibc.org/header.html deleted file mode 100644 index 294bafdbe..000000000 --- a/docs/uclibc.org/header.html +++ /dev/null @@ -1,81 +0,0 @@ -<!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'> - -<html> - <head> - <meta http-equiv='Content-Type' content='text/html; charset=iso-8859-1'> - <title>uClibc</title> - <style type="text/css"> - body { - background-color: #DEE2DE; - color: #000000; - } - :link { color: #660000 } - :visited { color: #660000 } - :active { color: #660000 } - td.c2 {font-family: arial, helvetica, sans-serif; font-size: 80%} - td.c1 {font-family: lucida, helvetica; font-size: 248%} - </style> - </head> - - <body> - <basefont face="lucida, helvetica, arial" size="3"> - - - - -<table border="0" cellpadding="0" cellspacing="0"> - - -<tr> -<td width="16%"> - <div class="c3"> - <table border="0" cellspacing="1" cellpadding="2"> - <tr> - <td class="c1">uClibc</td> - </tr> - </table> - </div> -</td> -</tr> - -<tr> - -<td valign="TOP"> - <br><a href="/about.html">About</a> - <br><a href="/lists.html">Mailing Lists</a> - <br><a href="/FAQ.html">FAQ</a> - <br><a href="/news.html">Latest News</a> - <br><a href="/download.html">Download</a> - <br><a href="/toolchains.html">Toolchains</a> - <br><a href="/cgi-bin/viewcvs.cgi/trunk/uClibc/">Browse Source</a> - <br><a href="/subversion.html">Accessing Source</a> - <br><a href="http://bugs.uclibc.org/">Bug Tracking</a> - <br><a href="/products.html">Products</a> - <br><a href="/other_libs.html">Other libcs</a> - - <p><b>Related Sites</b> - <br><a href="http://cxx.uclibc.org/">uClibc++</a> - <br><a href="http://busybox.net/">BusyBox</a> - <br><a href="http://udhcp.busybox.net/">udhcp</a> - <br><a href="http://buildroot.uclibc.org/">buildroot</a> - <br><a href="http://www.scratchbox.org/">Scratchbox</a> - <br><a href="http://openembedded.org/">OpenEmbedded</a> - <br><a href="http://www.ucdot.org/">uCdot</a> - <br><a href="http://www.linuxdevices.com">LinuxDevices</a> - <br><a href="http://slashdot.org/">Slashdot</a> - <br><a href="http://freshmeat.net/">Freshmeat</a> - <br><a href="http://linuxtoday.com/">Linux Today</a> - <br><a href="http://lwn.net/">Linux Weekly News</a> - <br><a href="http://www.tldp.org/HOWTO">Linux HOWTOs</a> - -<!-- - <a href="http://validator.w3.org/check/referer"><img - src="/images/vh40.gif" height=31 width=88 - align=left border=0 alt="Valid HTML 4.0!"></a> ---> - -</td> - - -<td Valign="TOP"> - diff --git a/docs/uclibc.org/images/back.png b/docs/uclibc.org/images/back.png Binary files differdeleted file mode 100644 index 79923869b..000000000 --- a/docs/uclibc.org/images/back.png +++ /dev/null diff --git a/docs/uclibc.org/images/dir.png b/docs/uclibc.org/images/dir.png Binary files differdeleted file mode 100644 index 1d633ce4a..000000000 --- a/docs/uclibc.org/images/dir.png +++ /dev/null diff --git a/docs/uclibc.org/images/donate.png b/docs/uclibc.org/images/donate.png Binary files differdeleted file mode 100644 index b55621bb9..000000000 --- a/docs/uclibc.org/images/donate.png +++ /dev/null diff --git a/docs/uclibc.org/images/fm.mini.png b/docs/uclibc.org/images/fm.mini.png Binary files differdeleted file mode 100644 index c0883cd34..000000000 --- a/docs/uclibc.org/images/fm.mini.png +++ /dev/null diff --git a/docs/uclibc.org/images/gfx_by_gimp.png b/docs/uclibc.org/images/gfx_by_gimp.png Binary files differdeleted file mode 100644 index d58314034..000000000 --- a/docs/uclibc.org/images/gfx_by_gimp.png +++ /dev/null diff --git a/docs/uclibc.org/images/ltbutton2.png b/docs/uclibc.org/images/ltbutton2.png Binary files differdeleted file mode 100644 index 556f72a6c..000000000 --- a/docs/uclibc.org/images/ltbutton2.png +++ /dev/null diff --git a/docs/uclibc.org/images/osuosl.png b/docs/uclibc.org/images/osuosl.png Binary files differdeleted file mode 100644 index b00b5007d..000000000 --- a/docs/uclibc.org/images/osuosl.png +++ /dev/null diff --git a/docs/uclibc.org/images/sdsmall.png b/docs/uclibc.org/images/sdsmall.png Binary files differdeleted file mode 100644 index b1024501b..000000000 --- a/docs/uclibc.org/images/sdsmall.png +++ /dev/null diff --git a/docs/uclibc.org/images/text.png b/docs/uclibc.org/images/text.png Binary files differdeleted file mode 100644 index 6034f899f..000000000 --- a/docs/uclibc.org/images/text.png +++ /dev/null diff --git a/docs/uclibc.org/images/vh40.gif b/docs/uclibc.org/images/vh40.gif Binary files differdeleted file mode 100644 index c5e9402e7..000000000 --- a/docs/uclibc.org/images/vh40.gif +++ /dev/null diff --git a/docs/uclibc.org/images/written.in.vi.png b/docs/uclibc.org/images/written.in.vi.png Binary files differdeleted file mode 100644 index 84f59bc15..000000000 --- a/docs/uclibc.org/images/written.in.vi.png +++ /dev/null diff --git a/docs/uclibc.org/index.html b/docs/uclibc.org/index.html deleted file mode 100644 index 1bab6b069..000000000 --- a/docs/uclibc.org/index.html +++ /dev/null @@ -1 +0,0 @@ -<!--#include file="news.html" --> diff --git a/docs/uclibc.org/lists.html b/docs/uclibc.org/lists.html deleted file mode 100644 index 1fbea3bc9..000000000 --- a/docs/uclibc.org/lists.html +++ /dev/null @@ -1,50 +0,0 @@ -<!--#include file="header.html" --> - - -<!-- Begin Introduction section --> - -<h3>uClibc Dev Mailing List</h3> -<p> -uClibc has a <a href="/lists/uclibc/">mailing list</a> for discussion and -development. You can subscribe by visiting -<a href="http://uclibc.org/mailman/listinfo/uclibc">this page</a>. There is -also an <a href="/lists/uclibc/">online archive</a>. -Only subscribers to the uClibc mailing list are allowed to post to this list. -</p> - -<h3>uClibc SVN Commits Mailing List</h3> -<p> -There is also a mailing list for <a href="/lists/uclibc-cvs/">svn commits</a> -for people wishing to read the complete diff of each and every change to -uClibc -- not for the faint of heart. Active developers can subscribe by -visiting <a href="http://uclibc.org/mailman/listinfo/uclibc-cvs">this -page</a>. The Subversion server is the only one permtted to post to this -list. And yes, this list name uses the word 'cvs' even though we don't use -that anymore ... -</p> - -<h3>Search the List Archives</h3> -Please search the mailing list archives before asking questions on the mailing -list, since there is a good chance someone else has asked the same question -before. Checking the archives is a great way to avoid annoying everyone on the -list with frequently asked questions... You should also check the -<a href="FAQ.html">list of Frequently Asked Questions</a>, since the answer -you need may very well be listed there. - -<p> -<center> -<form method="GET" action="http://www.google.com/custom"> -<input type="hidden" name="domains" value="uclibc.org"> -<input type="hidden" name="sitesearch" value="uclibc.org"> -<input type="text" name="q" size="31" maxlength="255" value=""> -<br> -<input type="submit" name="sa" value="search the mailing list archives"> -<br> -<a href="http://www.google.com"><img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google" height="32" width="75" align="middle"></a> -<br> -</form> -</center> -</p> - - -<!--#include file="footer.html" --> diff --git a/docs/uclibc.org/news.html b/docs/uclibc.org/news.html deleted file mode 100644 index ea89d8537..000000000 --- a/docs/uclibc.org/news.html +++ /dev/null @@ -1,105 +0,0 @@ -<!--#include file="header.html" --> - - -<ul> - - <li> <b>28 February 2007, uClibc 0.9.28.3 Released</b> - <br> - - We're aiming for a new release-early-release-often record or something with - the release of uClibc-0.9.28.3, which fixes a few more problems that tured - up after last week's 0.9.28.2 release -- in particular a problem with weak - threading symbols. As with last week's release, this is intended as a - drop-in replacement for the long-term stable uClibc 0.9.28 release series. - - <br> - - Head to the <a href="/downloads/">downloads page</a> to pick up the - <a href="/downloads/uClibc-0.9.28.3.tar.bz2">0.9.28.3 release</a>. - - <p> - <li> <b>21 February 2007, uClibc 0.9.28.2 Released</b> - <br> - - We're pleased to announce uClibc-0.9.28.2, with a few more bugfixes - and minor cleanups for tried and true stable 0.9.28 series. As with - uClibc 0.9.28.1, this is intended as a drop-in replacement for the - stable uClibc 0.9.28 release. - - <br> - - Trundle over to the <a href="/downloads/">downloads page</a> to pick up the - <a href="/downloads/uClibc-0.9.28.2.tar.bz2">0.9.28.2 release</a>. - - <p> - <li> <b>28 January 2007, uClibc 0.9.28.1 Released</b> - <br> - - Take one part uClibc-0.9.28 and many part bugfixes and you we're proud to - announce uClibc-0.9.28.1. What sort of bugfixes you may wonder? The good - kind of course. This marks the new state of development which matches so - many other projects; while heavy development happens on the next major - version, we'll push out some stable point releases. - - <br> - - Trundle over to the <a href="/downloads/">downloads page</a> to pick up the - <a href="/downloads/uClibc-0.9.28.1.tar.bz2">0.9.28.1 release</a>. - - <p> - <li> <b>17 August 2005, uClibc 0.9.28 Released</b> - <br> - - CodePoet Consulting is pleased to announce the release of uClibc 0.9.28. - You are probably used to this by now, but this release is NOT binary - compatible with uClibc 0.9.27 or any earlier release, so be prepared to - recompile your software if you are still using an old version of uClibc. - - <p> - - Updated uClibc development systems built using uClibc 0.9.28, along - with the <a href="http://buildroot.uclibc.org/">uClibc buildroot</a> - and source code used to compile these development systems will be released - later this evening, along with - <a href="http://ltp.sourceforge.net/">Linux Test Project test suite</a> - results demonstrating how uClibc is doing. Contributions of LTP test - suite run results using uClibc are welcome... - - <p> - - As usual the - <a href="http://www.uclibc.org/downloads/uClibc-0.9.28.tar.bz2">source code for this release</a> - is available <a href="http://www.uclibc.org/downloads/">here</a>. - - - - <p> - <li><b>13 January 2005 -- Bug and Patch Tracking</b><p> - - Bug reports sometimes get lost when posted to the mailing list. The - developers of uClibc are busy people, and have only so much they can keep - in their brains at a time. In my case, I'm lucky if I can remember my own - name, much less a bug report posted last week... To prevent your bug report - from getting lost, if you find a bug in uClibc, please use the - <a href="http://bugs.uclibc.org/">shiny new Bug and Patch Tracking System</a> - to post all the gory details. - - <p> - - The same applies to patches... Regardless of whether your patch - is a bug fix or adds spiffy new features, please post your patch - to the Bug and Patch Tracking System to make certain it is - properly considered. - - - <p> <li> <b>Old News</b> - <br> - <a href="/oldnews.html">Click here to read older news</a> - <p> - - - -</ul> - -<!--#include file="footer.html" --> - diff --git a/docs/uclibc.org/oldnews.html b/docs/uclibc.org/oldnews.html deleted file mode 100644 index 655e291df..000000000 --- a/docs/uclibc.org/oldnews.html +++ /dev/null @@ -1,1143 +0,0 @@ -<!--#include file="header.html" --> - - -<ul> - - - <li> <b>12 January 2005, uClibc 0.9.27 Released</b> - <br> - - CodePoet Consulting is pleased to announce the release of - uClibc 0.9.27. Release highlights include a new stdio core, - Linux 2.6.x support, a much improved shared library loader, - support for several new architectures, and of course fixes for - the usual pile of bugs. - - <p> - - Due primarily to the stdio changes, this release is NOT binary - compatible with uClibc 0.9.26 or any earlier release, so be - prepared to recompile your software if you are still using an - old version of uClibc. Sorry for the pain... - - <p> - - Updated uClibc development systems using uClibc 0.9.27, along - with the uClibc buildroot and source code used to compile these - development systems, have also been released and are available - from the uclibc.org downloads area. - - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.27.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - - - <p> - <li> <b>20 April 2004, uClibc 0.9.26 based Debian uwoody</b> - <br> - - CodePoet Consulting (i.e. Erik) is pleased to announce the immediate - availability of an x86 port of Debian woody compiled with uClibc 0.9.26. - This was originally announced a couple of months ago, but has been updated - a few times since to correct several small problems. If you want an easy - way to start building your own uClibc based applications, this is it. This - even supports building your own packages using 'apt-get', and using - 'apt-get' to install already compiled packages from uclibc.org. You can - find Erik's uwoody distribution <a - href="http://www.uclibc.org/dists/">uwoody distribution here</a>. Assembling - this Debian/uClibc system required a <em>lot</em> of work, so if you - think this is the coolest thing since the invention of water, feel free to - <a href="http://uclibc.org/FAQ.html#support">let us know</a>. - - - <p> - <li> <b>3 January 2004, uClibc 0.9.26 Released</b> - <br> - - CodePoet Consulting is sorry to announce there was a pthread bug that - slipped though our extensive testing and was only noticed a few hours after - the previous release. As a result, we are now releasing uClibc 0.9.26 - which fixes this bug, and is otherwise identical to the previous release. - - <p> - - This release remains binary compatible with uClibc 0.9.21-25, as long as - you take care to avoid any configuraton changes that will break things. - Please be aware we <b>will</b> break binary compatibilty in the upcoming - 0.9.27 release to implement a few necessary changes we have been - postponing. That will hopefully be the last ABI change before we freeze - the ABI for the upcoming 1.0.x stable uClibc series. - - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.26.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - - <li> <b>3 January 2004, uClibc 0.9.25 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.25. This contains many bug fixes and cleanups, and is - recommended for anyone using uClibc. This release remains binary - compatible with uClibc 0.9.21-24 (as long as you take care to avoid any - configuraton changes that will break things). We <b>were</b> planning to break - binary compatibilty in this release, but decided to hold those changes so - we could push out a bugfix release. - - <p> - - Please be aware we <b>will</b> break binary compatibilty in the upcoming - 0.9.26 release to implement a few changes we have been postponing. That - will hopefully be the last ABI change before we freeze the ABI for the - upcoming 1.0.x stable uClibc series. - - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.25.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - - <p> - <li> <b>19 December 2003, dev systems updated to uClibc 0.9.24</b> - <br> - - Current uClibc development systems have been posted for - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mips.bz2">mips</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mipsel</a>, and - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_sh4.bz2">sh4</a>. - The powerpc dev system mostly works, but there are still some - problems with the shared library loader that have not yet been resolved. - Details on what these are and how to use them can be found in the - <a href="/FAQ.html#dev_systems">FAQ</a> - - - <p> - <li> <b>15 December 2003, uClibc 0.9.24 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.24. This contains various minor updates and fixes for a few - silly configuration problems. Arm users should notice a speed increase - since some arm optimized string functions have been added. And several - bugs have been fixed. - - <p> - - This release continues to be binary compatible with uClibc 0.9.21 to 0.9.23 - -- as long as you pick compatible configuration options. The next release - will <b>not</b> be binary compatible. We've been saving up a few needed - changes that will be going into the next release, so while you will not - need to recompile all your applications and libraries just yet, keep in - mind we will have a flag day soon... - - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.24.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - <li> <b>13 November 2003, uClibc 0.9.23 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.23. Of course, we are somewhat less than pleased that there - were configuration problems in the previous release that made such it - necessary to release .23 so quickly. Updated uClibc development systems - using uClibc 0.9.23 are being built and will be posted shortly. And Erik - has built Debian stable (woody) for x86 with uClibc and it runs great. - - <p> - - This release continues to be binary compatible with uClibc 0.9.21 and - 0.9.22 -- as long as you pick compatible configuration options. Enabling - or disabling things like soft-float, locale, wide char support, or changing - cpu optimizations are all good examples of binary incompatible - configuration options. If have changed any of those sorts of options (or - if you are not sure!) you will need to recompile all your applications and - libraries. - - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.23.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - <p> - - - <p> - <li> <b>8 November 2003, uClibc 0.9.22 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.22. This release has been cooking for a couple of months now - and is looking quite solid. We have done quite a lot of testing with this - release and things are looking good. And Erik has built Debian stable - (woody) for x86 with uClibc and it runs great. Expect that to be released - in the next few days. - - <p> - - This release is binary compatible with uClibc 0.9.21 -- as long as you pick - compatible configuration options. Enabling or disabling things like - soft-float, locale, wide char support, or changing cpu optimizations are - all good examples of binary incompatible configuration options. If have - changed any of those sorts of options (or if you are not sure!) you will - need to recompile all your applications and libraries. - - <p> - - Updated uClibc development systems using uClibc 0.9.22 will be made - available within a few days. Meanwhile, we invite you to try out uClibc - with the latest <a href="http://ltp.sourceforge.net/">Linux Test Project - test suite</a> (you will need to apply a small <a - href="http://www.uclibc.org/cgi-bin/viewcvs.cgi/trunk/buildroot/sources/ltp-testsuite.patch?rev=1.3">patch</a>. - And also give the latest Perl and Python test suites a try as well. - If you find any bugs in uClibc, PLEASE let us know! - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.22.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - <p> - - - <p> - <li> <b>30 September 2003, dev systems updated to uClibc 0.9.21+</b> - <br> - - The uClibc development systems for - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mips</a>, - have been updated to uClibc 0.9.21 (plus all the CVS updates up to - today). Several problems have been fixed up, - gcc has been updated to version 3.3.1, binutils was updated to 2.14.90.0.6, and - <em>tada</em> everything finally works for cross compiling. These were - all cross compiled (which really makes things faster since the older - mipsel releases used to take 2 days to build!) - - <p> - These are ~100 MB ext2 filesystems that run natively on the specified - architecture. They contains all the development software you need to build - your own uClibc applications, including bash, coreutils, findutils, - diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace, - make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh perl, - and more. And of course, everything is dynamically linked against uClibc. - By using a uClibc only system, you can avoid all the painful - cross-configuration problems that have made using uClibc somewhat painful - in the past. If you want to quickly get started with testing or using - uClibc you should give these images a try. You can loop mount and them - you can chroot into them, you can boot into with using user-mode Linux, - and you can even 'dd' them to a spare partition and use resize2fs to make - them fill the drive. Whatever works for you. - - <p> If you would like to build your own custom uClibc system, you can - use <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>, which is - how these uClibc development systems were created. - <p> - - - <p> - <li> <b>9 September 2003, uClibc 0.9.21 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.21. This release has been brewing for several months now, and - provides quite a lot of additional functionality and quite a few bug fixes - as well. Many people will be pleased that this release fixes the - "dlopen()'ing libraries that depend on libraries" problem. - - <p> - - The biggest thing in this release (and I do mean that literally) is that - uClibc now has full ANSI/ISO C99 locale support. Well, except for - wcsftime() and collating items in regex, which are not done yet. Adding - support for the default set of locales (169 UTF-8 locales and 144 locales - using other codesets) will enlarge uClibc by around 300k. Still, if you - need locale support, that is still much better than the roughly 30MB the - comparable set of locale date occupies with glibc. And you can of course - reduce the 300k by reducing the number of supported locales. - - <p> - - As usual, this release has many improvements, both large and small. At - this point, most applications that compile and work with glibc will also - compile and run with uClibc. Both Perl and Python pass all the tests in - their test suites (both with and without locale support enabled). We - invite you to grab a copy of the latest <a - href="http://ltp.sourceforge.net/"> Linux Test Project test suite</a> and - give uClibc some abuse. We are not yet perfect, but we are getting pretty - darn close. - - <p> - - This release is not binary compatible with earlier releases. Depending on - your configuration, you may actually still be binary compatible, but it - would be a good idea to recompile your applications when moving to the - uClibc 0.9.21 release. We are sorry about that, but we have never promised - to provide binary compatibility until we hit version 1.0. And even then, - if you change your uClibc configuration, you still still generally need to - recompile... - - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.21.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - <p> - - Updated uClibc development systems using uClibc 0.9.21 will be made - available within a few days. - <p> - - - <p> - <li> <b>30 June 2003, uClibc 0.9.20 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.20. This is primarily a bug-fix release. This release remains - binary compatible with 0.9.18 and 0.9.19 (as long as you leave the - new UCLIBC_HAS_TM_EXTENSIONS option disabled), so you don't have to recompile - everything if you don't really feel like it. - <p> - - This release has many small improvements. At this point, most applications - that compile and work with glibc will also compile and run with uClibc. - Perl and Python even pass all the tests in their test suites. - <p> - - There is currently one notable exception. Applications that use dlopen() - to load libraries that themselves depend on other libraries, may have weak - symbols within those depended-upon libraries resolved incorrectly. This - problem is currently being worked on. Other than that, everything seems - to now be working as expected.... - - <p> - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.20.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - <p> - - - <p> - <li> <b>30 June 2003, dev systems updated to uClibc 0.9.20</b> - <br> - - The uClibc development systems for - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mips</a>, - have been updated to uClibc 0.9.20. Several problems have been fixed up, - gcc has been updated to version 3.3, and Perl 5.8.0 is now included. - <p> - - This is a 150 MB ext2 filesystem that runs natively on the specified - architecture. It contains all the development software you need to build - your own uClibc applications, including bash, coreutils, findutils, - diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace, - make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh perl, - and more. And of course, everything is dynamically linked against uClibc. By - using a uClibc only system, you can avoid all the painful - cross-configuration problems that have made using uClibc somewhat painful - in the past. If you want to quickly get started with testing or using - uClibc you should give these images a try. You can loop mount and then - chroot into them, you can boot into them using user-mode Linux, and you can - even 'dd' them to a spare partition and use resize2fs to make them fill the - drive. Whatever works for you. - - <p> If you would like to build your own custom uClibc system, you can - use <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>, which is - how the uClibc development systems were created. - <p> - - - <p> - <li> <b>6 March 2003, development system updates</b> - <br> - - The uClibc development systems for - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a>, - and now for the first time - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mips</a>, - have been updated to uClibc 0.9.19. Several smaller problems - have also been fixed up. - <p> - - This is an ext2 filesystem that runs natively on the specified - architecture. It contains all the development software you need to build - your own uClibc applications, including bash, coreutils, findutils, - diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace, - make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh and - more. And of course, everything is dynamically linked against uClibc. By - using a uClibc only system, you can avoid all the painful - cross-configuration problems that have made using uClibc somewhat painful - in the past. If you want to quickly get started with testing or using - uClibc you should give these images a try. You can loop mount and - then chroot into them, you can boot into them using user-mode Linux, - you can even 'dd' them to a spare partition and use resize2fs to - make them fill the drive. Whatever works best for you. - <p> - - Have Fun. - <p> - - - <p> - <li> <b>3 March 2003, uClibc 0.9.19 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.19. This is once again primarily a bug-fix release. Several - critical problems with system calls were fixed, the pthreads library was - improved, debugging of applications using uClibc's pthreads library is - now possible (requires gdb 5.3 or newer that is compiled using uClibc), - and a number of other random fixes are included. This release retains - binary compatibility with uClibc 0.9.18 (except for mips, which didn't - work properly with uClibc 0.9.18 anyways). Updated development system - images compiled with uClibc 0.9.19 will be released shortly. - - <p> - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a> and <a - href="http://www.uclibc.org/downloads/uClibc-0.9.19.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - <p> - - - - - <p> - <li> <b>17 February 2003, development system updates</b> - <br> - - The uClibc development systems for - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a> - and - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - and - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a> - have been again updated. This time around a few broken symlinks - (one preventing C++ code from compiling) have been fixed, several - system calls related to uids and gid have been fixed, the powerpc - system call mechanism has been updated, and GNU tar and GNU grep - have been added. gcc, gcc+, ssh, etc are all still included and - things remain binary compatible with uClibc 0.9.18. - Have Fun. - <p> - - - <p> - <li> <b>12 February 2003, development system updates</b> - <br> - - The uClibc development system has had a number of problems - fixed, and has been updated for uClibc 0.9.18. The - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a> - and - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - and - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a> - devel systems are updated and ready to download and use. - Have Fun. - <p> - - - <p> - <li> <b>12 February 2003, uClibc 0.9.18 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.18. This is primarily a bug-fix release, as there were a few - directory handling problem that could cause application using uClibc 0.9.17 - to either segfault or lose the first character when reading directry names. - Unfortunately, once again, this release is _NOT_ binary compatible with - earlier uClibc releases. I _think this will be the last time (with the - possible exception of some future changes to our locale support...) - - <p> - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a> - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.18.tar.bz2">source code</a> - for this release are available <a href="http://www.uclibc.org/downloads/">here</a>. - You might want to download uClibc from the closest - <a href="http://kernel.org/mirrors/">kernel.org mirror site</a>. - Just pick the closest mirror site, and then go to - <a href="http://www.kernel.org/pub/linux/libs/uclibc/"> - http://www.XX.kernel.org/pub/linux/libs/uclibc/</a> - to download uClibc, where XX is your two letter country code. - <p> - <p> - - <p> - <li> <b>25 January 2003, uClibc 0.9.17 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.17. The biggest piece of news with this release, thanks to - Manuel Novoa's continuing hard work, is that we now have fully standards - compliant locale support (optional of course). The support works nicely, - (though configuring the locales you wish to support is still manual -- a - task for the next release). Full locale data for over 300 locales adds - approximately 250k. The collation data for all supported locales is - roughly 180k. This may seem rather large to some -- but it is much smaller - than the approximately 40 MB needed by Glibc to provide the same data. And - if you don't need it, you can either disable locale support entirely, or - enable a smaller set of locales. - - <p> - - This release also fixes <em>lots and lots</em> of bugs. The arm - architecture support (I am embarrassed to note) was totally broken in the - last release, but is now working as expected. A security problem (a - buffer overflow in getlogin_r) was fixed. And there were architecture - updates across the board (x86, arm, powerpc, cris, h8300, sparc, and mips). - And of course, this release includes the usual pile of bug fixes. Many - thanks for the large number of patches and fixes that were contributed! - - <p> - - Unfortunately, this release is not binary compatible with earlier uClibc - releases. As noted as item 3 <a href="downloads/Glibc_vs_uClibc_Differences.txt">here</a>, - uClibc does not (yet) attempt to - ensure binary compatibility across releases. We will eventually do that - (once we reach the "1.0" release) but not yet. A few bugs turned up that - needed to be fixed, and the only good way to fix them was to change some - fundamental data structure sizes. As a result, this release is _NOT_ - binary compatible with earlier releases -- you will need to recompile your - applications. The x86, arm, powerpc, and mips architectures (i.e. the - systems Erik has available in his office for testing) have been tested and - are known to work following this change. Other architectures <em>may</em> - need additional updates. Sorry about that, but it had to be done. - - <p> - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a> - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.17.tar.bz2">source code</a> - for this release are available <a href="http://www.uclibc.org/downloads/">here</a>. - You might want to download uClibc from the closest - <a href="http://kernel.org/mirrors/">kernel.org mirror site</a>. - Just pick the closest mirror site, and then go to - <a href="http://www.kernel.org/pub/linux/libs/uclibc/"> - http://www.XX.kernel.org/pub/linux/libs/uclibc/</a> - to download uClibc, where XX is your two letter country code. - <p> - - <p> - <li> <b>25 January 2003, dev system updates, arm image released</b> - <br> - - A number of additional problems have been fixed and the arm build - is now, finally, compiling and working as expected. As such, - I have updated the <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2"> - i386 development system image</a>, the - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2"> - powerpc development system image</a>, and I am also releasing - upon an unsuspecting world the brand new - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2"> - arm development system image</a>! - Have fun! - <p> - - All three development system images were compiled and built using the stock - <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a> system. These were also - built using the (about to be announced in a couple on minutes) uClibc - 0.9.17 release, so if you want to begin compiling and testing stuff with - uClibc, but you don't feel like spending the _hours_ it takes to download, - configure, and build your own uClibc based development system -- then you - may want to download these and give them a try. They each contain a 100 MB - ext2 filesystem with everything you need to begin compiling your own - applications. I have (at least minimally) tested each of them and verified - that the included gcc and g++ compilers produce working uClibc linked - executables. - - <p> - Oh, and I have also have updated the uClibc/gcc toolchain builders, so - if you just want a simple uClibc/gcc toolchain, - <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">one of these should work for you.</a> - <p> - - - <p> - <li> <b>10 January 2003, dev system updates, powerpc image released</b> - <br> - - A few problems showed up in yesterday's development system release - (adduser was broken, gdb didn't work, libstdc++ shared libs were missing, - etc). So I've updated the <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2"> - i386 development system image</a> to fix these problems. - Also, the <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2"> - powerpc development system image</a> has finally finished compiling - and is now released upon an unsuspecting world. Have fun! - <p> - - - <p> - <li> <b>9 January 2003, uClibc development system released</b> - <br> - - CodePoet Consulting (i.e. Erik) has been working hard on <a - href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a> recently, and is pleased to - offer a full stand-alone uClibc-only development system. This is an ext2 - filesystem for i386 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, valgrind, - busybox, GNU coreutils, and more, this should have pretty much everything - you need to get started building your own applications linked against - uClibc. By using a uClibc only system, you can avoid all the painful - cross-configuration problems that have made using uClibc somewhat painful - in the past. A powerpc and an arm version are in progress. Expect them - to be released shortly.... - - <p> - - The <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2"> - uClibc development system is an 18MB bzip2 compressed ext2 filesystem</a>, - so be prepared to wait if you are on a slow link. If you wish to have more - space, you can loop mount it and 'cp -a' the contents to their own - partition, or do what I did... <EM>WARNING, the following can be very - dangerous. Please be sure you know what you are doing before trying this. - I am not responsible if you lose all your important data.</EM>I had a spare - hard drive (in my case /dev/hdg but you'll want to adapt this to your own - needs), so I partitioned it with a single ext2 partition filling the drive - (in my case /dev/hdg1). Then I ran:<PRE> - bzcat root_fs_i386.bz2 | dd of=/dev/hdg1 - e2fsck -f /dev/hdg1 - resize2fs -p /dev/hdg1</PRE> - - which overwrote everything on /dev/hdg with the new uClibc devel system, - and then expanded the filesystem with the uClibc devel system till it - filled the whole drive. - <p> - - - <p> - <li> <b>8 November 2002, uClibc 0.9.16 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.16. This release adds full support (including a native shared - library loader) for the CRIS architecture, contributed by Tobias Anderberg. - Stefan Allius contributed a number of patches to fix the initialization - order for shared library global constructors and destructors as well as a - large number of SuperH fixes and cleanups. uClibc now compiles with - newer versions of gcc (i.e. RedHat 8.0). Thanks to Christian Michon, - uClibc no longer requires perl to compile. Steven J. Hill fixed dlopen for - mips. Several problems with pty and tty handling were fixed. Manuel Novoa - added new support for an /etc/TZ file to globally set the system timezone, - and fixed up a number of remaining wide char issues. Manuel is still hard - at work on bringing full locale support (optional of course) to uClibc. - And of course, this release includes the usual pile of bug fixes. Many thanks - for the large number of patches and fixes that were contributed! - <p> - - Erik and Manuel have been working on a - <a href="downloads/Glibc_vs_uClibc_Differences.txt"> - document describing some of the differences between uClibc and glibc.</a> - It's not yet 100% complete, and it hasn't been nicely formatted yet. But - it contains a lot of helpful information and is worth a look. - <p> - - And finally, the the old uClibc configuration system has been completely - removed (and there was much rejoicing). It was replaced with an entirely - new system based on <a href="http://www.xs4all.nl/~zippel/lc/">LinuxKernelConf</a>, - which has since been included into Linux 2.5.45, so it looks like Erik made - the right choice. Of course, those who have existing build systems using uClibc - will need to make a few changes... We think the change is worth it. - <p> - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a> - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.16.tar.bz2">source code</a> - for this release are available <a href="http://www.uclibc.org/downloads/">here</a>. - You might want to download uClibc from the closest - <a href="http://kernel.org/mirrors/">kernel.org mirror site</a>. - Just pick the closest mirror site, and then go to - <a href="http://www.kernel.org/pub/linux/libs/uclibc/"> - http://www.XX.kernel.org/pub/linux/libs/uclibc/</a> - to download uClibc, where XX is your two letter country code. - <p> - Updated gcc-3.2 and gcc-2.95 toolchains will be released shortly. - <p> - - - <p> - <li> <b>16 September 2002, gcc-3.2 and gcc-2.95 toolchains released</b> - <br> - - CodePoet Consulting (i.e. Erik) has released updated gcc-3.2 and gcc-2.95 - uClibc toolchains. These toolchains build real gcc cross compilers (i.e. - not just a wrapper) and create executables linked vs uClibc. The new - gcc-3.2 provides uClibc support with the latest and greatest compiler - available from the gcc team. The gcc-2.95 toolchain has been updated to - the latest version of uClibc and now provides full C++ support, using the - <a href="http://www.stlport.org/">STLport</a> standard C++ library. - <p> - - This toolchain should make it easy for anyone to build uClibc based - applications. - <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/"> Source code can be downloaded here</a>. - Be aware that much of the needed source code will actually be downloaded on - when you compile the toolchains. To build a toolchain, simply - grab the source, edit the Makefile to select where you would like - the toolchain installed, run 'make', and then go watch TV, eat - dinner, or visit with your friends while it compiles. It takes - about 15 minutes for Erik to compile the gcc-3.2 toolchain (w/C++ support) - on his Athlon XP 1600 (not counting the time it takes to download - source code). - <p> - - - - <p> - <li> <b>27 August 2002, uClibc 0.9.15 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability - of uClibc 0.9.15. This release fixes a number of problems that turned - up since the last release. The good news is that uClibc now - passes all tests in the perl 5.8 and Python 2.2.1 test suites, both with - and without pthreads. So without any further ado.... - <p> - The - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a> - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.15.tar.bz2">source code</a> - for this release are available <a href="http://www.uclibc.org/downloads/">here</a>. - <p> - Have fun! - <p> - - - <p> - <li> <b>12 August 2002, uClibc 0.9.14 Released</b> - <br> - - CodePoet Consulting is slightly less pleased then usual to announce the - immediate availability of uClibc 0.9.14. This is, unfortunately, a bugfix - release intended to fix the couple of dumb things that slipped into the - previous release. Version 0.9.13 of uClibc would fail to compile when - enabling both RPC and Pthreads. There was also a problem with RPC thread - local storage (but noone noticed since it didn't compile ;-). Also, the - thread locking in exit(), onexit() and atexit() was broken, and wasn't - actually locking anything. This release also fixes uClibc's gcc wrapper - to use crtbeginS.o and crtendS.o when compiling PIC code, fixing a subtle - bug (that was much less subtle on powerpc). Finally, this release includes a - few minor compile warning cleanups. - <p> - The - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a> - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.14.tar.bz2">source code</a> - for this release are available <a href="http://www.uclibc.org/downloads/">here</a>. - <p> - Have fun! - <p> - - - <li> <b>12 August 2002, Native uClibc/gcc-3.1.1 toolchain released</b> - <br> - - CodePoet Consulting (i.e. Erik) has released an updated native - uClibc/gcc-3.1.1 toolchain. This toolchain builds a real gcc cross - compiler (i.e. not just a wrapper) and creates executables linked vs - uClibc. This toolchain has been (briefly) tested as working on x86, arm, - mips, and arm7tdmi (uClinux). This toolchain provides a number of - improvements over previous releases. In particular, Steven J. Hill found - and fixes a number of "glibc-isms" in the libstdc++ math support which - caused a number of math functions to be mapped to the non-standard named - under GNU libc. This release also includes greatly improved uClinux - "elf2flt" support, and it now produces working flat binaries for my - uClinux/arm7tdmi system. The native uClibc/gcc-2.95 toolchain will be - updated in a few days, and will include STLport which will allow that - toolchain to also provide full C++ support. - <p> - - This toolchain should make it easy for anyone to build uClibc based - applications. - <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. - Be aware that much of the needed source code will actually be downloaded on - demand when you compile things. To build the toolchain, simply - grab the source, edit the Makefile to select where you would like - the toolchain installed, run 'make', and then go watch TV, eat - dinner, or visit with your friends while it compiles. It takes - about 15 minutes for Erik to compile the gcc-3.1.1 toolchain (w/C++ support) - on his Athlon XP 1600 (not counting the time it takes to download - source code). Your results may vary... - <p> - - <li> <b>9 August 2002, uClibc now mirrored on kernel.org!</b> - <br> - uClibc is now available from the kernel.org mirrors! This should make - uClibc downloads much faster. The kernel.org mirrors will have all - uClibc release versions (everything but the daily snapshots). - Here is a list of all the <a href="http://kernel.org/mirrors/">kernel.org mirror sites</a>. - Just pick the closest mirror site, and then go to "/pub/linux/libs/uclibc/" - to download uClibc. - Just pick the closest mirror site, and then go to - <a href="http://www.kernel.org/pub/linux/libs/uclibc/"> - http://www.XX.kernel.org/pub/linux/libs/uclibc/</a> to download the latest - uClibc release from a nice fast system. - <p> - <p> - - <p> - <li> <b>9 August 2002, uClibc 0.9.13 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.13. After several days of testing, this release is looking very - solid. This release fixes three security vulnerabilites in previous - releases. There was an off-by-one buffer overflow in the group handling - code, and integer overflows in calloc() and xdr_array(). - <p> - - This release adds native shared library support for the Hitachi - SuperH architecture, thanks to Stefan Allius and Edie C. Dost. A - new mmap based malloc was implemented by Miles Bader. This is much - smarter than the old "malloc-simple" and is now the default for - mmu-less systems, where it should greatly help reduce memory - fragmentation and wastage. In addition to these larger items, there - has been a <em>lot</em> of work done to make uClibc a cleaner, more - capable, library. Most applications now compile and run without - any trouble. - <p> - The - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a> - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.13.tar.bz2">source code</a> - for this release are available <a href="http://www.uclibc.org/downloads/">here</a>. - <p> - Have fun! - <p> - - - <li> <b>11 July 2002, Native uClibc toolchains updated</b> - <br> - CodePoet Consulting (i.e. Erik) has released updated native - uClibc/gcc-3.1 and uClibc/gcc-2.95 toolchains. These toolchains - build real gcc cross compilers (i.e. not just a wrapper) and create - executables linked vs uClibc. These toolchains have been tested - and found working on x86, arm, and mmu-less arm. They should work - (at least in theory!) for all architectures supported by uClibc. - <p> - - These toolchains should make it easy to anyone to build uClibc based - applications. - <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. - Be aware that much of the needed source code will actually be downloaded on - demand when you compile things. To build the toolchain, simply - grab the source, edit the Makefile to select where you would like - the toolchain installed, run 'make', and then go watch TV, eat - dinner, or visit with your friends while it compiles. It takes - about 15 minutes for Erik to compile the gcc-3.1 toolchain (w/C++ support) - on his Athlon XP 1600 (not counting the time it takes to download - source code). Your results may vary... - <p> - - - <P> - <li> <b>20 June 2002, uClibc 0.9.12 Released</b> - <br> - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.12. This release adds an i960 port, an initial alpha port, - fully working mips shared library support, shared library support fixes - for on powerpc, and many other improvements. One very exciting new feature - is nearly complete locale support, thanks to a lot of hard work by Manuel - Novoa III. uClibc's locale support is <em>much</em> smaller than glibc's, - though it is also slightly less flexible. This release was delayed by a - month due to the arrival of a new baby at Erik's house. For those that - have been anxiously waiting, this release should certainly be worth the - wait. Have fun! - <p> - The <a href="downloads/Changelog">Changelog</a> - and <a href="downloads/uClibc-0.9.12.tar.bz2">source code</a> - for this release are available <a href="downloads/">here</a>. - - <li> <b>28 May 2002, Native uClibc/gcc-3.1 toolchain</b> - <br> - CodePoet Consulting has released source code and a Makefile to build a - gcc-3.1 toolchain that natively targets uClibc. Additionally, the - gcc-3.0.4 and gcc-2.95 toolchains have also been updated. These toolchains - make it easy to build uClibc based applications. - <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. - and is now much smaller, - since much of the needed binutils and gcc source code is now downloaded on - demand. To build the toolchain, simply grab the source, edit the Makefile - to select where you would like the toolchain installed, and then run 'make' - and wait for it to compile. - - <p> - <p><li> <b>10 April 2002, uClibc 0.9.11 Released</b> - <br> - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.11. This release is primarily focused on fixing the issues that - have turned up since the last release. Several bugs in the gcc wrapper - have been fixed, allowing applications such as iproute2 and XFree86 to link properly. - Large file support has been improved, and a thread locking bug was - fixed that could cause s*printf calls to deadlock when threading was - enabled. Several bugs were also fixed with the powerpc, h8300, m68k, - sparc, and mips architecture support. Many additional applications now - compile and run perfectly and have been added to the <a - href="uClibc-apps.html">working applications list</a> . - <p> - The <a href="downloads/Changelog">Changelog</a> - and <a href="downloads/uClibc-0.9.11.tar.bz2">source code</a> - for this release are available <a href="downloads/">here</a>. - - - - <p> - <li> <b>10 April 2002, Native uClibc/gcc-3.0.4 toolchain</b> - <br> - CodePoet Consulting has released source code and a Makefile - to build a gcc-3.0.4 toolchain that natively targets uClibc. - This brings with it full C++ support for uClibc, including the - libstdc++ library. A gcc-2.95.x toolchain will also be released - shortly, but is not yet ready. At this time, only source code and - a Makefile for the native uClibc toolchain is being released (i.e. - no binaries, sorry). - <a href="/cgi-bin/viewcvs.cgi/trunk/toolchain/">Source code can be downloaded here</a>. - <p> - To build the toolchain, simply grab the source, edit the Makefile - to select where you would like the toolchain installed. Then - run 'make' and wait for it to compile. If you do not have a copy - of uClibc already, it will download the latest daily snapshot. - - - <p> - <li> <b>21 March 2002, uClibc 0.9.10 Released!</b> - <br> - - CodePoet Consulting is pleased to announce the immediate - availability of uClibc 0.9.10. This release adds pthreads support - (including pthreads support for mmu-less systems!). Additionally, - thanks to Manuel Novoa III, we now have a completely new stdio - library, which is small, standards compliant, supports pthreads, - wide/narrow streams, large files, and can even operate in a - low-memory unbuffered mode. Many, many bugs have been fixed and a - number of additional applications now compile and run perfectly. - Even with all these changes, uClibc continues to be very small. - On x86, a default build of the uClibc C library is still just 168k. - - <p> - - To make things more interesting, the release also adds support for - C++ constructors and destructors. To make it easy to use uClibc - when developing C++ applications, this release also provides a - wrapper for the GNU C++ compiler. Of course, for more complex C++ - applications, such as those using iostreams, a standard C++ library - (libstdc++) is required. A native GNU toolchain (binutils/gcc) that - provides libstdc++ linked with uClibc 0.9.10 will be released in the - next couple of days, so stay tuned. - - <p> - The <a href="downloads/Changelog">Changelog</a> - and <a href="downloads/uClibc-0.9.10.tar.bz2">Source code</a> - for this release are available <a href="downloads/">here</a>. - <p> - - - <p> - <li> <b>4 February 2002, uClibc 0.9.9 Released!</b> - <br> - - CodePoet Consulting is pleased to announce the immediate - availability of uClibc 0.9.9. With this release, - <a href="uClibc-apps.html">just about - everything we have tested now compiles and runs</a>. In fact, - there are now so many programs on the working application list that - rather than continue to add to this list, from now on we - will only be adding applications to the <em>not working list</em>. Most applications - on the <em>not working list</em> either require pthreads, or require - wide-character support. Work on wide-character support is - well underway, and will hopefully be moving into CVS in the next week or - two. Full pthreads support and rentrancy are on the TODO list - and are expected to be complete in the next couple of months. - <p> - The <a href="downloads/Changelog">Changelog</a> - and <a - href="downloads/uClibc-0.9.9.tar.bz2">Source code</a> - for this release are available <a href="downloads/">here</a>. - <p> - One final bit on news -- as some of you may have noticed, uclibc.org - has been a bit overloaded and somewhat slow recently. The server should - be getting colocated tomorrow, which will eliminate the speed problem. - During the move, there may be some temporary disruption of service... - <p> - Have Fun! - - <p> - <li> <b>22 December 2001, uClibc 0.9.8 Released!</b> - <br> - - After many months of initial development, we are pleased to announce the - release of uClibc 0.9.8. This release should be quite solid, and is very - usable. This also, hopefully, marks a transition from a slow incubation - phase to a more methodical release cycle. From now one, there should be - approximately one release per month. - <p> - The source code for this release is available - <a href="downloads/">here</a>. - - - <p> - <li> <b>26 November 2001, powerpc shared libraries fully working</b> - <br> - Dave Schleef finished off the the work needed for shared library support on - powerpc. There had been a few problems remaining, and those are now squashed. - So shared libs on powerpc should be working fully now. - - <p> - <li> <b>14 November 2001, m68 compiles again, Large file support working</b> - <br> - About a month ago I synced the header files with glibc 2.2.4 for better - C++ support and better standards compliance. I forgot to sync up m68k, - sparc, powerpc, and mipsel. Dave Schleef fixed powerpc while he was fixing - up the shared lib loader. I just fixed up m68k, sparc, and mipsel so they - should all compile again. - <p> - I also finished up fixing large file support (just enable DOLFS in your - Config file to enable it) and it is working just great, and greatly increases - the number of glibc applications that will work "out-of-the-tarball" without - needing any changes. - - - <li> <b>12 November 2001, powerpc shared lib support</b> - <br> - Thanks to David Schleef, uClibc now has full shared library support - on powerpc. This brings full shared library support to x86, ARM, and - now powerpc. Thanks Dave! - - - <p> - <li> <b>7 November 2001, uClibc application list</b> - <br> - uClibc now has a <a href="uClibc-apps.html">list of applications</a> - that are known to work. If you have any applications to add to the - list, submissions are welcome! - - - <p> - <li> <b>18 October 2001, buildroot uClibc example system</b> - <br> - - Those wanting an easy way to test out uClibc and give it - a test drive can download and compile - <a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a>. - This is a nifty buildsystem that will automagically download and build - a <a href="http://user-mode-linux.sourceforge.net/">User-Mode Linux</a> - kernel, and will then download source for and compile up a fully - working uClibc based root filesystem. This should make it easy for - people to create their own projects. I hope that this build system - will allow people to more easily use and build uClibc based systems. - As an example of how nicely this works, the - <a href="http://tuxscreen.net/">Tuxscreen Project</a> is using a - <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/tuxscreen/buildroot-tux/">slightly adjusted variant of the buildroot system</a> to cross - compile the blob bootloader, linux kernel, and a uClibc based jffs2 - root filesystem (busybox, tinylogin, udhcp, lrzsz, pcmcia-cs and - microwindows) for ARM. Pretty cool. - - - - <p> - <li> <b>11 October 2001, v850 architecture support</b> - <br> - - Miles Bader has contributed support for the v850 architecture. - - - <p> - <li> <b>25 Spetember 2001, header files updated</b> - <br> - - uClibc's header files are now in sync with glibc 2.2.4, - allowing better standards compliance, better portibility, and - better C++ support. - - <p> - <li> <b>4 July 2001, ARM shared library support</b> - <br> - - uClibc now has full shared library support on ARM. - - - <p> - <li> <b>9 May 2001, libm added</b> - <br> - - uClibc now has a very complete math library. - - - <p> - <p> <li> <b>9 May 2001, ld.so added</b> - <br> - - uClibc now has a native ld.so. It currently is only ported to work on x86, - but porting to other architectures should not be too difficult. - - - <p> <li> <b>15 March 2001, powerpc port added</b> - <br> - - David Schleef contributed a powerpc port, which is now in CVS. - - <p> <li> <b>19 February 2001, SH port added</b> - <br> - - Jean-Yves Avenard contributed an SH port. See his email - with the initial patch <a href="/lists/uclibc/2001-February/000409.html">here</a>. - - <p> <li> <b>16 January 2001, uClibc as a shared library</b> - <br> - - As if January 16, uClibc can now be used (at least on x86) as a shared - library. See the <a href="/lists/uclibc/2001-January/000126.html">email</a> - announcing this achievement. - - <p> <li> <b>11 January 2001, gcc wrapper added</b> - <br> - - Manuel Novoa III has created a wrapper for gcc that makes compiling apps vs uClibc - as simple as just setting "CC" to gcc-uClibc-< arch>. This even works when cross - compiling! Very cool. - - <p> <li> <b>3 January 2001, uClibc now has a web page</b> - <br> - - A lot of work has been going on under the hood with uClibc, - so I decided to put together this webpage to let the world know - that it exists and is getting to be usable. - -</ul> - - -<!--#include file="footer.html" --> - diff --git a/docs/uclibc.org/other_libs.html b/docs/uclibc.org/other_libs.html deleted file mode 100644 index 759c87f15..000000000 --- a/docs/uclibc.org/other_libs.html +++ /dev/null @@ -1,25 +0,0 @@ -<!--#include file="header.html" --> - - -<h3>Other Open Source C libraries</h3> -I am currently aware of the following open source C libraries. - -<ul> - - <li><a href="http://www.gnu.org/software/libc/libc.html">The GNU C Library</a> - <li> <a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/">The FreeBSD C Library</a> - <li> <a href="http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/">The NetBSD C Library</a> - <li> <a href="http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/">The OpenBSD C Library</a> - <li> <a href="http://cvs.opendarwin.org/index.cgi/src/Libc/">The OpenDarwin C Library</a> - <li><a href="http://www.fefe.de/dietlibc/">dietlibc</a> - <li> <a href="http://sources.redhat.com/newlib/">newlib</a> - <li> <a href="http://www.k9wk.com/cdoc.html">Al's FREE C Runtime Library</a> - <li>the <a href="http://www.cs.vu.nl/~ast/minix.html">minix</a> - <a href="http://www.cs.vu.nl/cgi-bin/raw/pub/minix/2.0.0/src.tar">C library</a> - <li>and there is a <a href="ftp://ecos.sourceware.org/pub/ecos/">C library</a>, - for <a href="http://ecos.sourceware.org/">eCos</a> as well. - -</ul> - -<!--#include file="footer.html" --> - diff --git a/docs/uclibc.org/products.html b/docs/uclibc.org/products.html deleted file mode 100644 index 3aad0a3b2..000000000 --- a/docs/uclibc.org/products.html +++ /dev/null @@ -1,25 +0,0 @@ -<!--#include file="header.html" --> - - -<h3>Products/Projects Using uClibc</h3> - -Do you use uClibc? I'd love to know about it and I'd be happy to link to you. - -<p> -I know of the following products and/or projects that use uClibc -- -listed in the order I happen to add them to the web page: - -<ul> - -<li><a href="/cgi-bin/viewcvs.cgi/trunk/buildroot/">buildroot</a> a configurable means for building your own busybox/uClibc based system systems.</li> -<li><a href="http://leaf.sourceforge.net/mod.php?mod=userpage&menu=910&page_id=36">LEAF Bering-uClibc</a> - <br>the sucessor of the Linux Router Project, supporting all sorts of gateways, routers, wireless routers, and firewalls.</li> -<li><a href="http://tuxscreen.net">Tuxscreen Linux Phone</a></li> -<li><a href="http://www.linksys.com/products/product.asp?prid=508">Linksys WRT54G - Wireless-G Broadband Router</a></li> -<li><a href="http://www.netgear.com/products/prod_details.asp?prodID=170">NetGear WG602 wireless router</a></li> -<li><a href="http://www.axis.com/">Almost all the Axis network cameras use uClibc</a></li> -<li><a href="http://embedded.gentoo.org/">Embedded Gentoo</a></li> - -</ul> - -<!--#include file="footer.html" --> diff --git a/docs/uclibc.org/subversion.html b/docs/uclibc.org/subversion.html deleted file mode 100644 index 8a171cf3f..000000000 --- a/docs/uclibc.org/subversion.html +++ /dev/null @@ -1,38 +0,0 @@ -<!--#include file="header.html" --> - - -<h3>Anonymous Subversion Access</h3> - -We allow anonymous (read-only) Subversion (svn) access to everyone. To -grab a copy of the latest version of uClibc using anonymous svn access is: - -<pre> -svn co svn://uclibc.org/trunk/uClibc</pre> - - -<p> - -If you are not already familiar with using Subversion, I recommend you visit <a -href="http://subversion.tigris.org/">the Subversion website</a>. You might -also want to read online or buy a copy of <a -href="http://svnbook.red-bean.com/">the Subversion Book</a>. If you are -already comfortable with using CVS, you may want to skip ahead to the <a -href="http://svnbook.red-bean.com/en/1.1/apa.html">Subversion for CVS Users</a> -part of the Subversion Book. - -<p> - -Once you've checked out a copy of the source tree, you can update your source -tree at any time so it is in sync with the latest and greatest by entering your -uClibc directory and running the command: - -<pre> -svn update</pre> - -Because you've only been granted anonymous access to the tree, you won't be -able to commit any changes. Changes can be submitted for inclusion by posting -them to the uClibc mailing list. For those that are actively contributing -<a href="developer.html">Subversion commit access</a> can be made available. - -<!--#include file="footer.html" --> - diff --git a/docs/uclibc.org/toolchains.html b/docs/uclibc.org/toolchains.html deleted file mode 100644 index d45098eb7..000000000 --- a/docs/uclibc.org/toolchains.html +++ /dev/null @@ -1,92 +0,0 @@ -<!--#include file="header.html" --> - - -<h3>Toolchains</h3> -To use uClibc, you need to have a toolchain. A toolchain consists -of <a href="http://sources.redhat.com/binutils/">GNU binutils</a>, -<a href="http://gcc.gnu.org/">the gcc compiler</a>, and uClibc, all -built to produce binaries for your target system linked with uClibc. -You can build your own native uClibc toolchain using the -<a href="http://buildroot.uclibc.org/">uClibc buildroot system</a>. - -<p> -To build your own uClibc toolchain, follow the following simple -steps: -<ul> - <li> Point your web browser <a href="http://buildroot.uclibc.org/">here</a>, - <li> Download of copy of buildroot - <li> Unpack the tarball on your Linux system somewhere - <li> Edit the Makefile as needed if you wish to change anything. - <li> run 'unset CC'. Then run 'unset CXX'. Some Linux systems - (i.e. Gentoo) set variables such as 'CC' in the system environment - which really messes things up when cross compiling. - <li> run 'make menuconfig' - <li> Select the things you want to build. If you <em>only</em> want a - toolchain, leave everything except the toolchain disabled. - <li> save your buildroot configuration. - <li> run 'make' - <li> go eat a nice wholesome sandwich, drink a pop, call a friend, - play a video game, and generally find something to do. While you - are waiting, buildroot will download all the needed source code and - then compile things up for you. - <li> You should now have a shiny new toolchain, and maybe even a shiny - new uClibc based root filesystem or development system, depending on - the options you selected. -</ul> - - - - -<p> - -If you want to be <em>really</em> 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 - -<a href="http://www.uclibc.org/downloads/root_fs_arm.ext2.bz2">arm</a>, -<a href="http://www.uclibc.org/downloads/root_fs_armeb.ext2.bz2">armeb</a>, -<a href="http://www.uclibc.org/downloads/root_fs_i386.ext2.bz2">i386</a>, -<a href="http://www.uclibc.org/downloads/root_fs_mips.ext2.bz2">mips</a>, -<a href="http://www.uclibc.org/downloads/root_fs_mipsel.ext2.bz2">mipsel</a>, -<a href="http://www.uclibc.org/downloads/root_fs_powerpc.ext2.bz2">powerpc</a>, and -<a href="http://www.uclibc.org/downloads/root_fs_sh4.ext2.bz2">sh4</a>. - -<p> - -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. - -<p> - -Each of these uClibc development systems was created using -<a href="http://buildroot.uclibc.org/">buildroot</a>, specifically, -<a href="http://buildroot.uclibc.org/downloads/buildroot-0.9.27.tar.bz2">buildroot-0.9.27.tar.bz2</a> -along with <a href="http://buildroot.uclibc.org/downloads/buildroot-sources">these sources</a>. - -<p> - -These development systems should provide 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. - -<p> -The quickest way to get started using a root_fs image (using the i386 -platform as an example) is: -<ul> - <li>Download root_fs_i386.bz2 from uclibc.org</li> - <li>bunzip2 root_fs_i386.bz2</li> - <li>mkdir root_fs</li> - <li>su root</li> - <li>mount -o loop root_fs_i386 root_fs</li> - <li>chroot root_fs /bin/su -</li> -</ul> -Type "exit" to end the chroot session and return to your host system. -<p> - - -<!--#include file="footer.html" --> - diff --git a/docs/uclibc.org/uClibc-apps.html b/docs/uclibc.org/uClibc-apps.html deleted file mode 100644 index eacd9d577..000000000 --- a/docs/uclibc.org/uClibc-apps.html +++ /dev/null @@ -1,135 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> - -<HTML> -<HEAD> -<TITLE>uClibc -- a C library for embedded systems</TITLE> -</HEAD> - -<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000"> - -<basefont face="lucida, helvetica, arial" size="3"> - - -<CENTER> -<p> - -<TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2> - <TR> - <td bgcolor="#000000"> - <FONT FACE="lucida, helvetica" COLOR="#ccccc0"> - <B>µ C l i b c</B> - </FONT> - </TD> - </TR> -</TABLE> -<p> - - -<!-- Begin NOT Working List --> - -<br> -When you are done, -<a href="http://www.uclibc.org/">you can click here to return to the uClibc home page.</a> - - - -<TABLE WIDTH=95% CELLSPACING=1 CELLPADDING=4 BORDER=1> -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="notworking"> <BIG><B> - uClibc -- NOT WORKING Application List - </font> - </A></B></BIG> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - -<p> The following applications are known to NOT work with uClibc. Please -tell us if you know of any applications that fall into this category! </p> - -<p> -NOTE: because basically everything works with uClibc these days, we -have removed the old "WORKING Application List" and from now on will -only be adding items to the NOT WORKING list, - - -<!-- Not Working List --> -<center> -<table width="100%" border=1> -<tr><th width="15%"> Program </th> - <th width="15%"> Version </th> - <th width="70%"> Comment </th> -</tr> -<!-- -------------------------------------------------------------------- --> -<tr> - <td> <a href="http://www.mozilla.org/">Mozilla</a> </td> - <td> </td> - <td> Might actually work now. Someone care to give it a try?</td> -</tr> -<tr> - <td> Dunno....</a> </td> - <td> </td> - <td> If you know of an application that <em>does not work</em> with uClibc, - PLEASE let us know! </td> -</tr> -<!-- -------------------------------------------------------------------- --> - -</table> -</center> -<!-- End of NOT Working List --> - - - -<!-- End of Table --> - -</TD></TR> -</TABLE> -</P> - - - -<!-- Footer --> -<HR> -<TABLE WIDTH="100%"> - <TR> - <TD> - <font size="-1" face="arial, helvetica, sans-serif"> - Mail all comments, insults, suggestions and bribes to - <a href="mailto:andersen@codepoet.org">Erik Andersen</a><BR> - </font> - </TD> - - <TD> - <a href="http://www.vim.org"><img border=0 width=90 height=36 - src="images/written.in.vi.png" - alt="This site created with the vi editor"></a> - </TD> - - <TD> - <a href="http://www.gimp.org/"><img border=0 width=90 height=36 - src="images/gfx_by_gimp.png" alt="Graphics by GIMP"></a> - </TD> - - <TD> - <a href="http://www.linuxtoday.com"><img width=90 height=36 - src="images/ltbutton2.png" alt="Linux Today"></a> - </TD> - - <TD> - <p><a href="http://slashdot.org"><img width=90 height=36 - src="images/sdsmall.png" alt="Slashdot"></a> - </TD> - - <TD> - <a href="http://freshmeat.net"><img width=90 height=36 - src="images/fm.mini.png" alt="Freshmeat"></a> - </TD> - - </TR> -</TABLE> - - -</CENTER> -</BODY> -</HTML> - - - |
