From 7037f0609e5350ac2c785fedd2c94c29a6b73bfd Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Thu, 11 Dec 2003 07:16:11 +0000 Subject: Rework the website --- docs/uclibc.org/FAQ.html | 332 +++++--------- docs/uclibc.org/cvs_anon.html | 185 +------- docs/uclibc.org/cvs_howto.html | 44 ++ docs/uclibc.org/cvs_write.html | 91 +--- docs/uclibc.org/download.html | 32 ++ docs/uclibc.org/footer.html | 18 + docs/uclibc.org/header.html | 80 ++++ docs/uclibc.org/index.html | 508 +++------------------ docs/uclibc.org/lists.html | 45 ++ docs/uclibc.org/news.html | 124 +++++ docs/uclibc.org/old-news.html | 988 ---------------------------------------- docs/uclibc.org/oldnews.html | 887 ++++++++++++++++++++++++++++++++++++ docs/uclibc.org/other_libs.html | 24 + docs/uclibc.org/products.html | 27 ++ docs/uclibc.org/robots.txt | 2 - docs/uclibc.org/toolchains.html | 52 +++ 16 files changed, 1529 insertions(+), 1910 deletions(-) create mode 100644 docs/uclibc.org/cvs_howto.html create mode 100644 docs/uclibc.org/download.html create mode 100644 docs/uclibc.org/footer.html create mode 100644 docs/uclibc.org/header.html create mode 100644 docs/uclibc.org/lists.html create mode 100644 docs/uclibc.org/news.html delete mode 100644 docs/uclibc.org/old-news.html create mode 100644 docs/uclibc.org/oldnews.html create mode 100644 docs/uclibc.org/other_libs.html create mode 100644 docs/uclibc.org/products.html delete mode 100644 docs/uclibc.org/robots.txt create mode 100644 docs/uclibc.org/toolchains.html diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html index 98f1b94aa..70dd14366 100644 --- a/docs/uclibc.org/FAQ.html +++ b/docs/uclibc.org/FAQ.html @@ -1,69 +1,49 @@ - + - - - uClibc FAQ-- a C library for embedded systems - - +

Frequently Asked Questions

- - - -
-

- - - - - -
- - µ C l i b c - -
-

- - - - - - - - - - - - - - - - - - - - - - - - - - -
- - uClibc Frequently Asked Questions (FAQ) - - -
- -

-This is a collection of some of the frequently asked questions +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, -
-When you are done, you can click here to return -to the uClibc home page. +

    +
  1. Why is it called uClibc? +
  2. What platforms does uClibc run on? +
  3. Why are you doing this? What's wrong with glibc? +
  4. So uClibc is smaller then glibc? Doesn't that mean it + completely sucks? How could it be smaller and not suck? +
  5. Why should I use uClibc? +
  6. 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. +
  7. Can I use it on my x86 development system? +
  8. Does uClibc support shared libraries? + +
  9. How do I compile programs with uClibc? +
  10. Why do I keep getting "sh: can't access tty; job control + turned off" errors? Why doesn't Control-C work within my shell? +
  11. How do I make autoconf and automake behave? +
  12. When I run 'ldd' to get a list of the library dependencies + for a uClibc binary, ldd segfaults! What should I do? +
  13. Why does localtime() return times in UTC even when I have my timezone set? +
  14. What is the history of uClibc? Where did it come from? +
  15. 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 Right Now! +
  16. 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? +
  17. I think you guys are great and I want to help support your work! + + +
+ + +

-

- - What platforms does uClibc run on? - -
- - Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300, - m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors. - - +

Why is it called uClibc?

-

- - Why is it called uClibc? - -
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 @@ -77,13 +57,20 @@ to the uClibc home page. 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. +
+

+

What platforms does uClibc run on?

+

+ + + Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300, + m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors. + + +


+

+

Why are you doing this? What's wrong with glibc?

-

- - Why are you doing this? What's wrong with glibc? - -
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 @@ -100,14 +87,12 @@ to the uClibc home page. +
+

+

So uClibc is smaller then glibc? Doesn't that mean it completely sucks? +How could it be smaller and not suck?

+

-

- - So uClibc is smaller then glibc? Doesn't that mean it completely sucks? - How could it be smaller and not suck? - -
uClibc and glibc have different goals. glibc strives for features and performance, and is targeted for desktops and servers with @@ -152,13 +137,10 @@ to the uClibc home page. +
+

+

Why should I use uClibc?

-

- - Why should I use uClibc? - -
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 @@ -175,15 +157,12 @@ to the uClibc home page. +
+

+

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.

-

- - 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. - -
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 those you gave the fully linked application. +
+

+

Can I use it on my x86 development system?

-

- - Can I use it on my x86 development system? - -
Sure! In fact, this can be very nice during development. By installing uClibc on your development system, you can be sure that @@ -225,13 +201,10 @@ to the uClibc home page. +
+

+

Does uClibc support shared libraries?

-

- - Does uClibc support shared libraries? - -
Yes. uClibc has native shared library support on i386, ARM, mips, SH, CRIS, and PowerPC processors. Other architectures can use shared @@ -243,13 +216,10 @@ to the uClibc home page. shared library support they may be able to help. +
+

+

How do I compile programs with uClibc?

-

- - How do I compile programs with uClibc? - -
You will need to have your own uClibc toolchain (i.e. GNU binutils and gcc configured to produce binaries linked with uClibc). @@ -281,14 +251,12 @@ to the uClibc home page. and use resize2fs to make them fill a partition... Whatever works best for you. + +
+

+

Why do I keep getting "sh: can't access tty; job control + turned off" errors? Why doesn't Control-C work within my shell?

-

- - Why do I keep getting "sh: can't access tty; job control turned off" errors? - Why doesn't Control-C work within my shell? - -
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 @@ -302,13 +270,10 @@ to the uClibc home page. run your shell on a real console... +
+

+

How do I make autoconf and automake behave?

-

- - How do I make autoconf and automake behave? - -
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 @@ -319,14 +284,11 @@ to the uClibc home page. configure scripts. +
+

+

When I run 'ldd' to get a list of the library dependencies + for a uClibc binary, ldd segfaults! What should I do?

-

- - When I run 'ldd' to get a list of the library dependencies for a uClibc - binary, ldd segfaults! What should I do? - -
Use the ldd that is built by uClibc, not your system's one. When your system's ldd looks for library dependencies, it actually _runs_ that @@ -338,13 +300,10 @@ to the uClibc home page. cross compiling. +
+

+

Why does localtime() return times in UTC even when I have my timezone set?

-

- - Why does localtime() return times in UTC even when I have my timezone set? - -
The uClibc time functions get timezone information from the TZ environment @@ -359,13 +318,11 @@ to the uClibc home page. automagically use the specified setting. +

-

- - What is the history of uClibc? Where did it come from? - -
+

What is the history of uClibc? Where did it come from?

+

+ The history and origin of uClibc is long and twisty. In the beginning, there was GNU libc. Then, libc4 @@ -421,15 +378,12 @@ to the uClibc home page. +


+

+

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 Right Now!

-

- - 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 Right Now! - -
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 @@ -438,15 +392,14 @@ to the uClibc home page. ignore you. + + +
+

+

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?

-

- - 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? - -
Sure! Now you have our attention! What you should do is contact Erik Andersen of 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. - + +
+

+

I think you guys are great and I want to help support your work!

-

- - I think you guys are great and I want to help support your work! - -
Wow, that would be great! You can click here to help support uClibc and/or request features. @@ -483,70 +433,8 @@ to the uClibc home page. support requests, etc., you can contact CodePoet Consulting here. -

-

- - Ok, I'm done reading all this stuff. - -
- -Well then, click here to return to the uClibc home page. - - - - - -
-

- - - - -
- - - - - - - - - - - - - - - -
- - Mail all comments, insults, suggestions and bribes to - Erik Andersen
-
-
- This site created with the vi editor - - Graphics by GIMP - - Linux Today - -

Slashdot -

- Freshmeat -
+
-
- - + - - diff --git a/docs/uclibc.org/cvs_anon.html b/docs/uclibc.org/cvs_anon.html index 388626f39..e5ed5b80a 100644 --- a/docs/uclibc.org/cvs_anon.html +++ b/docs/uclibc.org/cvs_anon.html @@ -1,46 +1,16 @@ - + - - -uClibc Anonymous CVS Instructions - - - - - - -

Accessing the uClibc CVS Repository

- -
- - - - -
- - u C l i b c - -
- - -
- - - - -
- - Anonymous CVS - -
+

Anonymous CVS

We allow anonymous (read-only) CVS access to everyone. The first command you need to run for anonymous CVS access is:
 cvs -d:pserver:anonymous@uclibc.org:/var/cvs login

-CVS will prompt you for a password. Just press Enter. This step only -needs to be done once, the first time you attempt to access CVS. +CVS will prompt you for a password. Just press the Enter key (there is no +password for anonymous access). This step only needs to be done once, the first +time you attempt to access CVS.

Once the login is complete, you can then check the list of available CVS modules by running the following command (all on one line): @@ -50,12 +20,16 @@ cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -c

If you wish, you can then check out a local copy of any of the available modules. The following is an example of how to grab -a copy of the uClibc source code: +a copy of uClibc:

     cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc
This will create a directory called uClibc in the current -directory which contains the latest and greatest source code for -uClibc. +directory. This directory will contain the latest and greatest source +code for uClibc. + +

+If you are not already familiar with using CVS, I recommend you visit +this quick Introduction to CVS.

I usually create a ~/.cvsrc file with the following things in it, and I @@ -76,137 +50,8 @@ cvs update 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 appropriate mailing list. - - - -

- - - - - - -
- - How to use CVS - -
- - -If you want to know all the gory details, you will want to visit -the CVS main web page.

-For the impatient, the following is probably about all you need to know: -

- -

-
cvs checkout -c
-
Will list the modules available for checkout -
cvs checkout < module name >
-
Will checkout the named module -
cvs co < module name >
-
Same thing -
cvs update
- -
Updates your local archive so it is in sync with the repository - -- your local updates are left intact. Tries to merge upstream updates - into your local updates. You will see the following tags when it is - updating your local repository: C means conflict, U means update, - P means patched, and M means modified. -
cvs up
-
Same thing -
cvs update < file name >
-
Same thing but for just the named file(s)/directory(s). -
cvs commit
-
Will check in all your work. -
cvs add < file name >
- -
Adds the named file/directory into CVS -
cvs remove < file name >
-
Removes the named file/directory from the upstream repository. -
cvs rm < file name >
-
Same thing -
cvs log < file name >
- -
Gives you the complete version history of what has happened to the named file(s). - Along with all tags, all commit messages, etc... -
cvs status < file name >
-
Gives you the current version number of the file(s) in question. -
cvs tag TAGNAME
-
Tags the versions of everything in the repository with the TAGNAME label. -
cvs tag TAGNAME < file name >
-
Tags the named file(s) in the repository with the TAGNAME label. -
cvs diff
- -
Gives you the difference between the local repository and the upstream repository. -
cvs diff < file name >
-
Same but for the named file(s). -
cvs diff -r 1.5 < file name >
-
Same but gives you the difference between the named file(s) and - version 1.5 of the named file(s). -
cvs diff -r TAGNAME < file name >
- -
Same but gives you the difference between the named file(s) and the - of the file tagged TAGNAME in the upstream repository. -
cvs rdiff -r TAGNAME module
-
Gives you a diff (that you can actually use with patch) between the current - version of module and the specified tagged version. -
cvs import < directory to import > < name for new module > start
-
Add a new module into the CVS archive. -

- -

- - - -
- - - - -
- - - - - - - - - - - - - - - -
- - Mail all comments, insults, suggestions and bribes to - Erik Andersen
-
-
- This site created with the vi editor - - Graphics by GIMP - - Linux Today - -

Slashdot -

- Freshmeat -
- - - - +them to the appropriate mailing list. For those that are actively contributing +CVS write access can be made available. + diff --git a/docs/uclibc.org/cvs_howto.html b/docs/uclibc.org/cvs_howto.html new file mode 100644 index 000000000..cff3a353c --- /dev/null +++ b/docs/uclibc.org/cvs_howto.html @@ -0,0 +1,44 @@ + + + +

How to use CVS

+ + +If you want to know all the gory details, you will want to visit +the CVS main web page.

+For the impatient, the following is probably about all you need to know: +

+ +

+
cvs checkout -c
+
Will list the modules available for checkout +
cvs checkout < module name >
+
Will checkout the named module +
cvs co < module name >
+
Same thing +
cvs update
+ +
Updates your local archive so it is in sync with the repository + -- your local updates are left intact. Tries to merge upstream updates + into your local updates. You will see the following tags when it is + updating your local repository: C means conflict, U means update, + P means patched, and M means modified. +
cvs up
+
Same thing +
cvs update < file name >
+
Same thing but for just the named file(s)/directory(s). +
cvs commit
+
Will check in all your work. +
cvs add < file name >
+ +
Adds the named file/directory into CVS +
cvs remove < file name >
+
Removes the named file/directory from the upstream repository. +
cvs rm < file name >
+
Same thing +
cvs log < file name >
+
+ + + + diff --git a/docs/uclibc.org/cvs_write.html b/docs/uclibc.org/cvs_write.html index 6a75138c1..f7c642f7d 100644 --- a/docs/uclibc.org/cvs_write.html +++ b/docs/uclibc.org/cvs_write.html @@ -1,39 +1,7 @@ - + - - -uClibc CVS Read/Write Instructions - - - - - - - -

Accessing the uClibc CVS Repository

- -
- - - - -
- - u C l i b c - -
- - -
- - - - -
- - CVS Read/Write Access - -
+

CVS Read/Write Access

If you want to be able to commit things to CVS, first contribute some stuff to show you are serious. Then, very nicely ask @@ -41,7 +9,7 @@ stuff to show you are serious. Then, very nicely ask an account. To access CVS, you will want to add the following to set up your environment:
 $ export CVS_RSH=/usr/bin/ssh
-$ export CVSROOT='username@cvs.uclibc.org:/var/cvs'
+$ export CVSROOT='username@cvs.busybox.net:/var/cvs'
It goes without saying you must change username to your own username... @@ -59,57 +27,6 @@ Note that if you would prefer to keep your communications with me private, you can encrypt your email using my public key. - - - -
- - - - -
- - - - - - - - - - - - - - - -
- - Mail all comments, insults, suggestions and bribes to - Erik Andersen
-
-
- This site created with the vi editor - - Graphics by GIMP - - Linux Today - -

Slashdot -

- Freshmeat -
- - - - - + diff --git a/docs/uclibc.org/download.html b/docs/uclibc.org/download.html new file mode 100644 index 000000000..cf888fc2f --- /dev/null +++ b/docs/uclibc.org/download.html @@ -0,0 +1,32 @@ + + + + +

Download

+ +Source for the latest release can always be +downloaded from http://www.uclibc.org/downloads + +

+You can also obtain Daily Snapshots of +the latest CVS source tree for those wishing to follow uClibc development, +but cannot or do not wish to use CVS. + +

+ +

+ + + diff --git a/docs/uclibc.org/footer.html b/docs/uclibc.org/footer.html new file mode 100644 index 000000000..0c7adb18a --- /dev/null +++ b/docs/uclibc.org/footer.html @@ -0,0 +1,18 @@ + + + + + + + +

+ + Copyright © 1999-2003 Erik Andersen +
+ Mail all comments, insults, suggestions and bribes to +
+ Erik Andersen andersen@codepoet.org
+
+ + + diff --git a/docs/uclibc.org/header.html b/docs/uclibc.org/header.html new file mode 100644 index 000000000..fc818727e --- /dev/null +++ b/docs/uclibc.org/header.html @@ -0,0 +1,80 @@ + + + + + uClibc + + + + + + + + + + + + + + + + + + + + + +
+
+ + + + +
uClibc
+
+
+
Home +
Mailing Lists +
FAQ +
Latest News +
Download +
Toolchains +
Accessing CVS +
Browse CVS +
Products +
Other libcs + + +
+
Related Sites +
BusyBox +
udhcp +
tinylogin +
uCdot +
LinuxDevices +
Slashdot +
Freshmeat +
Linux Today +
Linux Weekly News +
Linux HOWTOs + + + +
+ diff --git a/docs/uclibc.org/index.html b/docs/uclibc.org/index.html index e4caceb07..45d9479ad 100644 --- a/docs/uclibc.org/index.html +++ b/docs/uclibc.org/index.html @@ -1,58 +1,25 @@ - - - - -uClibc -- a C library for embedded systems - - - - - - - -

- -

- - - - -
- - µ C l i b c - -
-

-

+ +

A C library for embedded Linux

- - - - - - - - - -
- - uClibc -- a C library for embedded systems - - -
+uClibc (aka µClibc/pronounced yew-see-lib-see) is a C library for developing +embedded Linux systems. It is much smaller than the GNU C Library, 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 standard Linux and MMU-less (also known as µClinux) systems with +support for alpha, ARM, cris, i386, i960, h8300, m68k, mips/mipsel, PowerPC, +SH, SPARC, and v850 processors. -uClibc (aka µClibc/pronounced -yew-see-lib-see) is a C library for developing embedded Linux systems. -It is much smaller than the -GNU C Library, -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 standard Linux -and MMU-less (also known as µClinux) -systems with support for alpha, ARM, cris, i386, i960, h8300, m68k, mips/mipsel, -PowerPC, SH, SPARC, and v850 processors.

If you are building an embedded Linux system and you find that -glibc is eating up too much space, you should consider using +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 @@ -62,418 +29,77 @@ you plan to burn Linux into the system's firmware... uClibc is maintained by Erik Andersen + + +

+ +uClibc is maintained by Erik Andersen and is licensed under the GNU LIBRARY GENERAL PUBLIC LICENSE . 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 +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 list of Frequently Asked Questions for details.

-

Mailing List Information

- -uClibc has a mailing list.
-To subscribe, go and visit -this page. - -

- -

Frequently Asked Questions

- -Before asking questions on the uClibc mailing list, -you might want to take a look at the -list of Frequently Asked Questions -or -you might want to search the mailing list archives... -
- - -Google  ... -
- -

Working Applications List

- - These days, pretty much everything compiles with uClibc. This - is a list of applications that are known - to work just fine with uClibc. Since most applications work just - fine with uClibc, we are especially interested in knowing about any - applications that either do not compile or do not work - properly with uClibc. Submissions are welcome! +

Sponsors

- - - +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! -
- - - Latest News - - -
    +
  • Penguru Consulting
    + Custom development for embedded Linux systems and multimedia platforms +
  • -

    -

  • 13 November 2003, uClibc 0.9.23 Released -
    - - 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. - -

    - - 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. - -

    - - As usual, the - Changelog, - detailed changelog, - and source code for this release - are available here. - -

    - - -

    -

  • 8 November 2003, uClibc 0.9.22 Released -
    - - 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. - -

    - - 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. - -

    - - 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 Linux Test Project - test suite (you will need to apply a small patch. - 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! -

    - - As usual, the - Changelog, - detailed changelog, - and source code for this release - are available here. - -

    - - -

    -

  • 30 September 2003, dev systems updated to uClibc 0.9.21+ -
    - - The uClibc development systems for - i386, - powerpc, - arm, - mips, - 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 - tada 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!) - -

    - 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. - -

    If you would like to build your own custom uClibc system, you can - use buildroot, which is - how these uClibc development systems were created. -

    - - -

  • Old News -
    - - Click here to read older news. -

    +

  • opensource.se
    + Embedded open source consulting in Europe. +
  • +
  • Codepoet Consulting
    + Custom Linux, embedded Linux, BusyBox, and uClibc + development. +
+If you wish to be a sponsor, or if you have already contributed and would like +your name added here, email Erik. - - -
- - Sponsors - -
- - Please visit our sponsors and thank them for their support! They have - provided money, equipment, bandwidth, etc. Next time you need help with a - project, consider these fine companies! Several individuals have also - contributed (If you have contributed and would like your name added here, - just email Erik and let him know). - - - - - - - - - - -
- 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 - CodePoet Consulting - (we have a credit card machine so you can avoid PayPal if you wish). - - -
- - - - - - -
-
- - - - - -
- - Download - -
- - - - - - -
- - Toolchains - -
-
    - -
  • Steven J. Hill has kindly provided - RPMs and SRPMs - with toolchains for mips. - -
  • You can build your own - uClibc toolchain - using these Makefiles which automagically download all the source - needed code and compile it for you. - -
  • uClibc development systems for - i386 - and - powerpc, - and - arm - are available and contain complete gcc 3.2.2 toolchains. - -
  • You can compile your own uClibc development system using - buildroot. - -
- - - - - -
- - - Other Open Source C libraries: - - - -
- - -I am currently aware of the following open source C libraries. - -
- - - Links to other useful stuff - - - -
- - - - - - - -
-

- - - - -
- - - - - - - - - - - - - - - -
- - Mail all comments, insults, suggestions and bribes to - Erik Andersen
-
-
- This site created with the vi editor - - Graphics by GIMP - - Linux Today - -

Slashdot -

- Freshmeat -
+

+ + + + + + + +
+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 +CodePoet Consulting +(we have a credit card machine so you can avoid PayPal if you wish). + + +
+ + + + + + +
+
- - - + diff --git a/docs/uclibc.org/lists.html b/docs/uclibc.org/lists.html new file mode 100644 index 000000000..d47c6cb0e --- /dev/null +++ b/docs/uclibc.org/lists.html @@ -0,0 +1,45 @@ + + + + + +

Mailing List Information

+uClibc has a mailing list for discussion and +development. You can subscribe by visiting +this page. + +

+There is also a mailing list for active developers +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 +this page. + +

+ + +

Search the List Archives

+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 +list of Frequently Asked Questions, since the answer +you need may very well be listed there. + +

+ +

+
+ + + +
+ +
+Google +
+
+
+ + + + diff --git a/docs/uclibc.org/news.html b/docs/uclibc.org/news.html new file mode 100644 index 000000000..d5b7052cd --- /dev/null +++ b/docs/uclibc.org/news.html @@ -0,0 +1,124 @@ + + + +
    + +

    +

  • 13 November 2003, uClibc 0.9.23 Released +
    + + 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. + +

    + + 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. + +

    + + As usual, the + Changelog, + detailed changelog, + and source code for this release + are available here. + +

    + + +

    +

  • 8 November 2003, uClibc 0.9.22 Released +
    + + 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. + +

    + + 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. + +

    + + 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 Linux Test Project + test suite (you will need to apply a small patch. + 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! +

    + + As usual, the + Changelog, + detailed changelog, + and source code for this release + are available here. + +

    + + +

    +

  • 30 September 2003, dev systems updated to uClibc 0.9.21+ +
    + + The uClibc development systems for + i386, + powerpc, + arm, + mips, + 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 + tada 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!) + +

    + 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. + +

    If you would like to build your own custom uClibc system, you can + use buildroot, which is + how these uClibc development systems were created. +

    + + +

  • Old News +
    + Click here to read older news +

    + + +

+ + + diff --git a/docs/uclibc.org/old-news.html b/docs/uclibc.org/old-news.html deleted file mode 100644 index d7f0e6e42..000000000 --- a/docs/uclibc.org/old-news.html +++ /dev/null @@ -1,988 +0,0 @@ - - - - -uClibc -- a C library for embedded systems - - - - - - - -
-

- - - - - -
- - µ C l i b c - -
-

- - - - - - - - - -
- - uClibc -- a C library for embedded systems - -
- - Click Here to Return to the main uClibc webpage. -

- - - -

- - - Older News - - -
- -
    - -

    -

  • 9 September 2003, uClibc 0.9.21 Released -
    - - 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. - -

    - - 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. - -

    - - 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 Linux Test Project test suite and - give uClibc some abuse. We are not yet perfect, but we are getting pretty - darn close. - -

    - - 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... - -

    - - As usual, the - Changelog, - detailed changelog, - and source code for this release - are available here. - -

    - - Updated uClibc development systems using uClibc 0.9.21 will be made - available within a few days. -

    - - -

    -

  • 30 June 2003, uClibc 0.9.20 Released -
    - - 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. -

    - - 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. -

    - - 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.... - -

    - As usual, the - Changelog, - detailed changelog, - and source code for this release - are available here. -

    - - -

    -

  • 30 June 2003, dev systems updated to uClibc 0.9.20 -
    - - The uClibc development systems for - i386, - powerpc, - arm, - mips, - 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. -

    - - 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. - -

    If you would like to build your own custom uClibc system, you can - use buildroot, which is - how the uClibc development systems were created. -

    - - -

    -

  • 6 March 2003, development system updates -
    - - The uClibc development systems for - i386, - powerpc, - arm, - and now for the first time - mips, - have been updated to uClibc 0.9.19. Several smaller problems - have also been fixed up. -

    - - 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. -

    - - Have Fun. -

    - - -

    -

  • 3 March 2003, uClibc 0.9.19 Released -
    - - 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. - -

    - As usual, the - Changelog and source code for this release - are available here. -

    - - - - -

    -

  • 17 February 2003, development system updates -
    - - The uClibc development systems for - i386 - and - powerpc, - and - arm - 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. -

    - - -

    -

  • 12 February 2003, development system updates -
    - - The uClibc development system has had a number of problems - fixed, and has been updated for uClibc 0.9.18. The - i386 - and - powerpc, - and - arm - devel systems are updated and ready to download and use. - Have Fun. -

    - - -

    -

  • 12 February 2003, uClibc 0.9.18 Released -
    - - 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...) - -

    - As usual, the - Changelog - and source code - for this release are available here. - You might want to download uClibc from the closest - kernel.org mirror site. - Just pick the closest mirror site, and then go to - - http://www.XX.kernel.org/pub/linux/libs/uclibc/ - to download uClibc, where XX is your two letter country code. -

    -

    - -

    -

  • 25 January 2003, uClibc 0.9.17 Released -
    - - 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. - -

    - - This release also fixes lots and lots 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! - -

    - - Unfortunately, this release is not binary compatible with earlier uClibc - releases. As noted as item 3 here, - 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 may - need additional updates. Sorry about that, but it had to be done. - -

    - As usual, the - Changelog - and source code - for this release are available here. - You might want to download uClibc from the closest - kernel.org mirror site. - Just pick the closest mirror site, and then go to - - http://www.XX.kernel.org/pub/linux/libs/uclibc/ - to download uClibc, where XX is your two letter country code. -

    - -

    -

  • 25 January 2003, dev system updates, arm image released -
    - - 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 - i386 development system image, the - - powerpc development system image, and I am also releasing - upon an unsuspecting world the brand new - - arm development system image! - Have fun! -

    - - All three development system images were compiled and built using the stock - buildroot 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. - -

    - Oh, and I have also have updated the uClibc/gcc toolchain builders, so - if you just want a simple uClibc/gcc toolchain, - one of these should work for you. -

    - - -

    -

  • 10 January 2003, dev system updates, powerpc image released -
    - - 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 - i386 development system image to fix these problems. - Also, the - powerpc development system image has finally finished compiling - and is now released upon an unsuspecting world. Have fun! -

    - - -

    -

  • 9 January 2003, uClibc development system released -
    - - CodePoet Consulting (i.e. Erik) has been working hard on buildroot 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.... - -

    - - The - uClibc development system is an 18MB bzip2 compressed ext2 filesystem, - 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... 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.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:

    -    bzcat root_fs_i386.bz2 | dd of=/dev/hdg1
    -    e2fsck -f /dev/hdg1
    -    resize2fs -p /dev/hdg1
    - - 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. -

    - - -

    -

  • 8 November 2002, uClibc 0.9.16 Released -
    - - 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! -

    - - Erik and Manuel have been working on a - - document describing some of the differences between uClibc and glibc. - 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. -

    - - 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 LinuxKernelConf, - 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. -

    - As usual, the - Changelog - and source code - for this release are available here. - You might want to download uClibc from the closest - kernel.org mirror site. - Just pick the closest mirror site, and then go to - - http://www.XX.kernel.org/pub/linux/libs/uclibc/ - to download uClibc, where XX is your two letter country code. -

    - Updated gcc-3.2 and gcc-2.95 toolchains will be released shortly. -

    - - -

    -

  • 16 September 2002, gcc-3.2 and gcc-2.95 toolchains released -
    - - 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 - STLport standard C++ library. -

    - - This toolchain should make it easy for anyone to build uClibc based - applications. - Source code can be downloaded here. - 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). -

    - - - -

    -

  • 27 August 2002, uClibc 0.9.15 Released -
    - - 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.... -

    - The - Changelog - and source code - for this release are available here. -

    - Have fun! -

    - - -

    -

  • 12 August 2002, uClibc 0.9.14 Released -
    - - 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. -

    - The - Changelog - and source code - for this release are available here. -

    - Have fun! -

    - - -

  • 12 August 2002, Native uClibc/gcc-3.1.1 toolchain released -
    - - 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. -

    - - This toolchain should make it easy for anyone to build uClibc based - applications. - Source code can be downloaded here. - 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... -

    - -

  • 9 August 2002, uClibc now mirrored on kernel.org! -
    - 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 kernel.org mirror sites. - 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 - - http://www.XX.kernel.org/pub/linux/libs/uclibc/ to download the latest - uClibc release from a nice fast system. -

    -

    - -

    -

  • 9 August 2002, uClibc 0.9.13 Released -
    - - 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(). -

    - - 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 lot of work done to make uClibc a cleaner, more - capable, library. Most applications now compile and run without - any trouble. -

    - The - Changelog - and source code - for this release are available here. -

    - Have fun! -

    - - -

  • 11 July 2002, Native uClibc toolchains updated -
    - 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. -

    - - These toolchains should make it easy to anyone to build uClibc based - applications. - Source code can be downloaded here. - 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... -

    - - -

    -

  • 20 June 2002, uClibc 0.9.12 Released -
    - 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 much 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! -

    - The Changelog - and source code - for this release are available here. - -

  • 28 May 2002, Native uClibc/gcc-3.1 toolchain -
    - 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. - Source code can be downloaded here. - 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. - -

    -

  • 10 April 2002, uClibc 0.9.11 Released -
    - 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 working applications list . -

    - The Changelog - and source code - for this release are available here. - - - -

    -

  • 10 April 2002, Native uClibc/gcc-3.0.4 toolchain -
    - 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). - Source code can be downloaded here. -

    - 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. - - -

    -

  • 21 March 2002, uClibc 0.9.10 Released! -
    - - 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. - -

    - - 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. - -

    - The Changelog - and Source code - for this release are available here. -

    - - -

    -

  • 4 February 2002, uClibc 0.9.9 Released! -
    - - CodePoet Consulting is pleased to announce the immediate - availability of uClibc 0.9.9. With this release, - just about - everything we have tested now compiles and runs. 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 not working list. Most applications - on the not working list 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. -

    - The Changelog - and Source code - for this release are available here. -

    - 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... -

    - Have Fun! - -

    -

  • 22 December 2001, uClibc 0.9.8 Released! -
    - - 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. -

    - The source code for this release is available - here. - - -

    -

  • 26 November 2001, powerpc shared libraries fully working -
    - 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. - -

    -

  • 14 November 2001, m68 compiles again, Large file support working -
    - 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. -

    - 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. - - -

  • 12 November 2001, powerpc shared lib support -
    - 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! - - -

    -

  • 7 November 2001, uClibc application list -
    - uClibc now has a list of applications - that are known to work. If you have any applications to add to the - list, submissions are welcome! - - -

    -

  • 18 October 2001, buildroot uClibc example system -
    - - Those wanting an easy way to test out uClibc and give it - a test drive can download and compile - buildroot. - This is a nifty buildsystem that will automagically download and build - a User-Mode Linux - 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 - Tuxscreen Project is using a - slightly adjusted variant of the buildroot system 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. - - - -

    -

  • 11 October 2001, v850 architecture support -
    - - Miles Bader has contributed support for the v850 architecture. - - -

    -

  • 25 Spetember 2001, header files updated -
    - - uClibc's header files are now in sync with glibc 2.2.4, - allowing better standards compliance, better portibility, and - better C++ support. - -

    -

  • 4 July 2001, ARM shared library support -
    - - uClibc now has full shared library support on ARM. - - -

    -

  • 9 May 2001, libm added -
    - - uClibc now has a very complete math library. - - -

    -

  • 9 May 2001, ld.so added -
    - - 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. - - -

  • 15 March 2001, powerpc port added -
    - - David Schleef contributed a powerpc port, which is now in CVS. - -

  • 19 February 2001, SH port added -
    - - Jean-Yves Avenard contributed an SH port. See his email - with the initial patch here. - -

  • 16 January 2001, uClibc as a shared library -
    - - As if January 16, uClibc can now be used (at least on x86) as a shared - library. See the email - announcing this achievement. - -

  • 11 January 2001, gcc wrapper added -
    - - 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. - -

  • 3 January 2001, uClibc now has a web page -
    - - 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 very usable. - - -
- - - - -
-

- - - - -
- - - - - - - - - - - - - - - -
- - Mail all comments, insults, suggestions and bribes to - Erik Andersen
-
-
- This site created with the vi editor - - Graphics by GIMP - - Linux Today - -

Slashdot -

- Freshmeat -
- - -
- - - - diff --git a/docs/uclibc.org/oldnews.html b/docs/uclibc.org/oldnews.html new file mode 100644 index 000000000..ccdda769b --- /dev/null +++ b/docs/uclibc.org/oldnews.html @@ -0,0 +1,887 @@ + + + +
    + + +

    +

  • 9 September 2003, uClibc 0.9.21 Released +
    + + 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. + +

    + + 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. + +

    + + 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 Linux Test Project test suite and + give uClibc some abuse. We are not yet perfect, but we are getting pretty + darn close. + +

    + + 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... + +

    + + As usual, the + Changelog, + detailed changelog, + and source code for this release + are available here. + +

    + + Updated uClibc development systems using uClibc 0.9.21 will be made + available within a few days. +

    + + +

    +

  • 30 June 2003, uClibc 0.9.20 Released +
    + + 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. +

    + + 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. +

    + + 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.... + +

    + As usual, the + Changelog, + detailed changelog, + and source code for this release + are available here. +

    + + +

    +

  • 30 June 2003, dev systems updated to uClibc 0.9.20 +
    + + The uClibc development systems for + i386, + powerpc, + arm, + mips, + 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. +

    + + 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. + +

    If you would like to build your own custom uClibc system, you can + use buildroot, which is + how the uClibc development systems were created. +

    + + +

    +

  • 6 March 2003, development system updates +
    + + The uClibc development systems for + i386, + powerpc, + arm, + and now for the first time + mips, + have been updated to uClibc 0.9.19. Several smaller problems + have also been fixed up. +

    + + 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. +

    + + Have Fun. +

    + + +

    +

  • 3 March 2003, uClibc 0.9.19 Released +
    + + 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. + +

    + As usual, the + Changelog and source code for this release + are available here. +

    + + + + +

    +

  • 17 February 2003, development system updates +
    + + The uClibc development systems for + i386 + and + powerpc, + and + arm + 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. +

    + + +

    +

  • 12 February 2003, development system updates +
    + + The uClibc development system has had a number of problems + fixed, and has been updated for uClibc 0.9.18. The + i386 + and + powerpc, + and + arm + devel systems are updated and ready to download and use. + Have Fun. +

    + + +

    +

  • 12 February 2003, uClibc 0.9.18 Released +
    + + 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...) + +

    + As usual, the + Changelog + and source code + for this release are available here. + You might want to download uClibc from the closest + kernel.org mirror site. + Just pick the closest mirror site, and then go to + + http://www.XX.kernel.org/pub/linux/libs/uclibc/ + to download uClibc, where XX is your two letter country code. +

    +

    + +

    +

  • 25 January 2003, uClibc 0.9.17 Released +
    + + 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. + +

    + + This release also fixes lots and lots 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! + +

    + + Unfortunately, this release is not binary compatible with earlier uClibc + releases. As noted as item 3 here, + 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 may + need additional updates. Sorry about that, but it had to be done. + +

    + As usual, the + Changelog + and source code + for this release are available here. + You might want to download uClibc from the closest + kernel.org mirror site. + Just pick the closest mirror site, and then go to + + http://www.XX.kernel.org/pub/linux/libs/uclibc/ + to download uClibc, where XX is your two letter country code. +

    + +

    +

  • 25 January 2003, dev system updates, arm image released +
    + + 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 + i386 development system image, the + + powerpc development system image, and I am also releasing + upon an unsuspecting world the brand new + + arm development system image! + Have fun! +

    + + All three development system images were compiled and built using the stock + buildroot 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. + +

    + Oh, and I have also have updated the uClibc/gcc toolchain builders, so + if you just want a simple uClibc/gcc toolchain, + one of these should work for you. +

    + + +

    +

  • 10 January 2003, dev system updates, powerpc image released +
    + + 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 + i386 development system image to fix these problems. + Also, the + powerpc development system image has finally finished compiling + and is now released upon an unsuspecting world. Have fun! +

    + + +

    +

  • 9 January 2003, uClibc development system released +
    + + CodePoet Consulting (i.e. Erik) has been working hard on buildroot 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.... + +

    + + The + uClibc development system is an 18MB bzip2 compressed ext2 filesystem, + 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... 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.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:

    +    bzcat root_fs_i386.bz2 | dd of=/dev/hdg1
    +    e2fsck -f /dev/hdg1
    +    resize2fs -p /dev/hdg1
    + + 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. +

    + + +

    +

  • 8 November 2002, uClibc 0.9.16 Released +
    + + 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! +

    + + Erik and Manuel have been working on a + + document describing some of the differences between uClibc and glibc. + 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. +

    + + 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 LinuxKernelConf, + 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. +

    + As usual, the + Changelog + and source code + for this release are available here. + You might want to download uClibc from the closest + kernel.org mirror site. + Just pick the closest mirror site, and then go to + + http://www.XX.kernel.org/pub/linux/libs/uclibc/ + to download uClibc, where XX is your two letter country code. +

    + Updated gcc-3.2 and gcc-2.95 toolchains will be released shortly. +

    + + +

    +

  • 16 September 2002, gcc-3.2 and gcc-2.95 toolchains released +
    + + 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 + STLport standard C++ library. +

    + + This toolchain should make it easy for anyone to build uClibc based + applications. + Source code can be downloaded here. + 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). +

    + + + +

    +

  • 27 August 2002, uClibc 0.9.15 Released +
    + + 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.... +

    + The + Changelog + and source code + for this release are available here. +

    + Have fun! +

    + + +

    +

  • 12 August 2002, uClibc 0.9.14 Released +
    + + 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. +

    + The + Changelog + and source code + for this release are available here. +

    + Have fun! +

    + + +

  • 12 August 2002, Native uClibc/gcc-3.1.1 toolchain released +
    + + 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. +

    + + This toolchain should make it easy for anyone to build uClibc based + applications. + Source code can be downloaded here. + 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... +

    + +

  • 9 August 2002, uClibc now mirrored on kernel.org! +
    + 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 kernel.org mirror sites. + 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 + + http://www.XX.kernel.org/pub/linux/libs/uclibc/ to download the latest + uClibc release from a nice fast system. +

    +

    + +

    +

  • 9 August 2002, uClibc 0.9.13 Released +
    + + 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(). +

    + + 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 lot of work done to make uClibc a cleaner, more + capable, library. Most applications now compile and run without + any trouble. +

    + The + Changelog + and source code + for this release are available here. +

    + Have fun! +

    + + +

  • 11 July 2002, Native uClibc toolchains updated +
    + 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. +

    + + These toolchains should make it easy to anyone to build uClibc based + applications. + Source code can be downloaded here. + 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... +

    + + +

    +

  • 20 June 2002, uClibc 0.9.12 Released +
    + 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 much 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! +

    + The Changelog + and source code + for this release are available here. + +

  • 28 May 2002, Native uClibc/gcc-3.1 toolchain +
    + 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. + Source code can be downloaded here. + 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. + +

    +

  • 10 April 2002, uClibc 0.9.11 Released +
    + 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 working applications list . +

    + The Changelog + and source code + for this release are available here. + + + +

    +

  • 10 April 2002, Native uClibc/gcc-3.0.4 toolchain +
    + 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). + Source code can be downloaded here. +

    + 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. + + +

    +

  • 21 March 2002, uClibc 0.9.10 Released! +
    + + 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. + +

    + + 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. + +

    + The Changelog + and Source code + for this release are available here. +

    + + +

    +

  • 4 February 2002, uClibc 0.9.9 Released! +
    + + CodePoet Consulting is pleased to announce the immediate + availability of uClibc 0.9.9. With this release, + just about + everything we have tested now compiles and runs. 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 not working list. Most applications + on the not working list 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. +

    + The Changelog + and Source code + for this release are available here. +

    + 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... +

    + Have Fun! + +

    +

  • 22 December 2001, uClibc 0.9.8 Released! +
    + + 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. +

    + The source code for this release is available + here. + + +

    +

  • 26 November 2001, powerpc shared libraries fully working +
    + 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. + +

    +

  • 14 November 2001, m68 compiles again, Large file support working +
    + 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. +

    + 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. + + +

  • 12 November 2001, powerpc shared lib support +
    + 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! + + +

    +

  • 7 November 2001, uClibc application list +
    + uClibc now has a list of applications + that are known to work. If you have any applications to add to the + list, submissions are welcome! + + +

    +

  • 18 October 2001, buildroot uClibc example system +
    + + Those wanting an easy way to test out uClibc and give it + a test drive can download and compile + buildroot. + This is a nifty buildsystem that will automagically download and build + a User-Mode Linux + 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 + Tuxscreen Project is using a + slightly adjusted variant of the buildroot system 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. + + + +

    +

  • 11 October 2001, v850 architecture support +
    + + Miles Bader has contributed support for the v850 architecture. + + +

    +

  • 25 Spetember 2001, header files updated +
    + + uClibc's header files are now in sync with glibc 2.2.4, + allowing better standards compliance, better portibility, and + better C++ support. + +

    +

  • 4 July 2001, ARM shared library support +
    + + uClibc now has full shared library support on ARM. + + +

    +

  • 9 May 2001, libm added +
    + + uClibc now has a very complete math library. + + +

    +

  • 9 May 2001, ld.so added +
    + + 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. + + +

  • 15 March 2001, powerpc port added +
    + + David Schleef contributed a powerpc port, which is now in CVS. + +

  • 19 February 2001, SH port added +
    + + Jean-Yves Avenard contributed an SH port. See his email + with the initial patch here. + +

  • 16 January 2001, uClibc as a shared library +
    + + As if January 16, uClibc can now be used (at least on x86) as a shared + library. See the email + announcing this achievement. + +

  • 11 January 2001, gcc wrapper added +
    + + 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. + +

  • 3 January 2001, uClibc now has a web page +
    + + 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. + +
+ + + + diff --git a/docs/uclibc.org/other_libs.html b/docs/uclibc.org/other_libs.html new file mode 100644 index 000000000..d66d16110 --- /dev/null +++ b/docs/uclibc.org/other_libs.html @@ -0,0 +1,24 @@ + + + +

Other Open Source C libraries

+I am currently aware of the following open source C libraries. + +
    + +
  • The GNU C Library +
  • The FreeBSD C Library +
  • The NetBSD C Library +
  • The OpenBSD C Library +
  • dietlibc +
  • newlib +
  • Al's FREE C Runtime Library +
  • the minix + C library +
  • and there is a C library, + for eCos as well. + +
      + + + diff --git a/docs/uclibc.org/products.html b/docs/uclibc.org/products.html new file mode 100644 index 000000000..0525fcfb4 --- /dev/null +++ b/docs/uclibc.org/products.html @@ -0,0 +1,27 @@ + + + +

      Products/Projects Using uClibc

      + +Do you use uClibc? I'd love to know about it and I'd be happy to link to you. + +

      +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: + +

      + + + + diff --git a/docs/uclibc.org/robots.txt b/docs/uclibc.org/robots.txt deleted file mode 100644 index 052dac4d7..000000000 --- a/docs/uclibc.org/robots.txt +++ /dev/null @@ -1,2 +0,0 @@ -# go away -User-agent: * diff --git a/docs/uclibc.org/toolchains.html b/docs/uclibc.org/toolchains.html new file mode 100644 index 000000000..132270b6b --- /dev/null +++ b/docs/uclibc.org/toolchains.html @@ -0,0 +1,52 @@ + + + +

      Toolchains

      +To use uClibc, you need to have a toolchain, which is composed +of binutils, +gcc, and of course uClibc. + +
        + +
      • You can build your own + uClibc toolchain + using this to automagically download all the needed source code + and compile everything for you. +

        + +

      • Steven J. Hill has kindly provided + RPMs and SRPMs + with toolchains for mips. +

        + +

      • You can compile your own uClibc development system using + buildroot. +

        + +

      • Prebuilt uClibc development systems for + i386 + and + arm + and + mipsel + are available and contain complete native gcc 3.3.2 toolchains. These + are development systems are ext2 filesystems that runs natively on the + specified architecture. They contain 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 them 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, and then boot + into them. Whatever works for you. +

        + +

      + + + -- cgit v1.2.3