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 (limited to 'docs') 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 l