diff options
Diffstat (limited to 'docs/uclibc.org')
| -rw-r--r-- | docs/uclibc.org/FAQ.html | 332 | ||||
| -rw-r--r-- | docs/uclibc.org/cvs_anon.html | 185 | ||||
| -rw-r--r-- | docs/uclibc.org/cvs_howto.html | 44 | ||||
| -rw-r--r-- | docs/uclibc.org/cvs_write.html | 91 | ||||
| -rw-r--r-- | docs/uclibc.org/download.html | 32 | ||||
| -rw-r--r-- | docs/uclibc.org/footer.html | 18 | ||||
| -rw-r--r-- | docs/uclibc.org/header.html | 80 | ||||
| -rw-r--r-- | docs/uclibc.org/index.html | 508 | ||||
| -rw-r--r-- | docs/uclibc.org/lists.html | 45 | ||||
| -rw-r--r-- | docs/uclibc.org/news.html | 124 | ||||
| -rw-r--r-- | docs/uclibc.org/oldnews.html (renamed from docs/uclibc.org/old-news.html) | 109 | ||||
| -rw-r--r-- | docs/uclibc.org/other_libs.html | 24 | ||||
| -rw-r--r-- | docs/uclibc.org/products.html | 27 | ||||
| -rw-r--r-- | docs/uclibc.org/robots.txt | 2 | ||||
| -rw-r--r-- | docs/uclibc.org/toolchains.html | 52 |
15 files changed, 646 insertions, 1027 deletions
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 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> +<!--#include file="header.html" --> -<HTML> -<HEAD> - <TITLE>uClibc FAQ-- a C library for embedded systems</TITLE> -</HEAD> -<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000"> +<h3>Frequently Asked Questions</h3> -<basefont face="lucida, helvetica, arial" size="3"> - - -<CENTER> -<p> - -<TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2> - <TR> - <td bgcolor="#000000"> - <FONT FACE="lucida, helvetica" COLOR="#ccccc0"> - <B>µ C l i b c</B> - </FONT> - </TD> - </TR> -</TABLE> -<p> - - -<!-- Begin NOT Working List --> - - -<TABLE WIDTH=95% CELLSPACING=1 CELLPADDING=4 BORDER=1> -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="notworking"> <BIG><B> - uClibc Frequently Asked Questions (FAQ) - </font> - </A></B></BIG> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - -<p> -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, -<br> -When you are done, <a href="http://uclibc.org/">you can click here to return -to the uClibc home page.</a> +<ol> + <li><a href="#naming">Why is it called uClibc?</a> + <li><a href="#platforms">What platforms does uClibc run on?</a> + <li><a href="#why">Why are you doing this? What's wrong with glibc?</a> + <li><a href="#doesnt_suck">So uClibc is smaller then glibc? Doesn't that mean it + completely sucks? How could it be smaller and not suck?</a> + <li><a href="#why_should_i">Why should I use uClibc?</a> + <li><a href="#licensing">If I use uClibc, do I have to release all my source code to the world for + free? I want to create a closed source commercial application and I want + to protect my intellectual property.</a> + <li><a href="#development">Can I use it on my x86 development system?</a> + <li><a href="#shared"> Does uClibc support shared libraries?</a> + + <li><a href="#compiling">How do I compile programs with uClibc?</a> + <li><a href="#job_control">Why do I keep getting "sh: can't access tty; job control + turned off" errors? Why doesn't Control-C work within my shell?</a> + <li><a href="#autoconf">How do I make autoconf and automake behave?</a> + <li><a href="#ldd">When I run 'ldd' to get a list of the library dependencies + for a uClibc binary, ldd segfaults! What should I do?</a> + <li><a href="#timezones">Why does localtime() return times in UTC even when I have my timezone set?</a> + <li><a href="#history">What is the history of uClibc? Where did it come from?</a> + <li><a href="#demanding">I demand that you to add <favorite feature> right now! How come + you don't answer all my questions on the mailing list instantly? I demand + that you help me with all of my problems <em>Right Now</em>!</a> + <li><a href="#contracts">I need you to add <favorite feature>! Are the uClibc developers willing to + be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide + support contracts?</a> + <li><a href="#support">I think you guys are great and I want to help support your work!</a> + + +</ol> + + +<hr /> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - What platforms does uClibc run on? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - - Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300, - m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors. - - +<h2><a name="naming">Why is it called uClibc?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Why is it called uClibc? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> ARM7TDMI. These days, uClibc also works just fine on normal Linux systems (such as i386, ARM, and PowerPC), but we couldn't think of a better name. +<hr /> +<p> +<h2><a name="platforms">What platforms does uClibc run on?</a></h2> +<p> + + + Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300, + m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors. + + +<hr /> +<p> +<h2><a name="why">Why are you doing this? What's wrong with glibc?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Why are you doing this? What's wrong with glibc? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> +<hr /> +<p> +<h2><a name="doesnt_suck">So uClibc is smaller then glibc? Doesn't that mean it completely sucks? +How could it be smaller and not suck?</a></h2> +<p> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - So uClibc is smaller then glibc? Doesn't that mean it completely sucks? - How could it be smaller and not suck? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> +<hr /> +<p> +<h2><a name="why_should_i">Why should I use uClibc?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Why should I use uClibc? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> +<hr /> +<p> +<h2><a name="licensing">If I use uClibc, do I have to release all my source code to the world for + free? I want to create a closed source commercial application and I want + to protect my intellectual property.</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - 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. - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> No, you do not need to give away your application source code just because you use uClibc and/or run on Linux. uClibc is licensed under the <a @@ -210,13 +189,10 @@ to the uClibc home page.</a> those you gave the fully linked application. +<hr /> +<p> +<h2><a name="development">Can I use it on my x86 development system?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Can I use it on my x86 development system? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> +<hr /> +<p> +<h2><a name="shared"> Does uClibc support shared libraries?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Does uClibc support shared libraries? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> shared library support they may be able to help. +<hr /> +<p> +<h2><a name="compiling">How do I compile programs with uClibc?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - How do I compile programs with uClibc? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> and use resize2fs to make them fill a partition... Whatever works best for you. + +<hr /> +<p> +<h2><a name="job_control">Why do I keep getting "sh: can't access tty; job control + turned off" errors? Why doesn't Control-C work within my shell?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Why do I keep getting "sh: can't access tty; job control turned off" errors? - Why doesn't Control-C work within my shell? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> run your shell on a real console... +<hr /> +<p> +<h2><a name="autoconf">How do I make autoconf and automake behave?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - How do I make autoconf and automake behave? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> configure scripts. +<hr /> +<p> +<h2><a name="ldd">When I run 'ldd' to get a list of the library dependencies + for a uClibc binary, ldd segfaults! What should I do?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - When I run 'ldd' to get a list of the library dependencies for a uClibc - binary, ldd segfaults! What should I do? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> cross compiling. +<hr /> +<p> +<h2><a name="timezones">Why does localtime() return times in UTC even when I have my timezone set?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Why does localtime() return times in UTC even when I have my timezone set? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> The uClibc time functions get timezone information from the TZ environment @@ -359,13 +318,11 @@ to the uClibc home page.</a> automagically use the specified setting. +<hr /> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - What is the history of uClibc? Where did it come from? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> +<h2><a name="history">What is the history of uClibc? Where did it come from?</a></h2> +<p> + The history and origin of uClibc is long and twisty. In the beginning, there was <a href="http://www.gnu.org/software/libc/libc.html">GNU libc</a>. Then, libc4 @@ -421,15 +378,12 @@ to the uClibc home page.</a> +<hr /> +<p> +<h2><a name="demanding">I demand that you to add <favorite feature> right now! How come + you don't answer all my questions on the mailing list instantly? I demand + that you help me with all of my problems <em>Right Now</em>!</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - I demand that you to add <favorite feature> right now! How come - you don't answer all my questions on the mailing list instantly? I demand - that you help me with all of my problems <em>Right Now</em>! - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> ignore you. + + +<hr /> +<p> +<h2><a name="contracts">I need you to add <favorite feature>! Are the uClibc developers willing to + be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide + support contracts?</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - 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? - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> Sure! Now you have our attention! What you should do is contact <a href="mailto:andersen@codepoet.org">Erik Andersen</a> of <a @@ -455,14 +408,11 @@ to the uClibc home page.</a> are several other active uClibc contributors who will almost certainly be able to help you out. Erik can contact them and ask them about their availability. - + +<hr /> +<p> +<h2><a name="support">I think you guys are great and I want to help support your work!</a></h2> <p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - I think you guys are great and I want to help support your work! - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> 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.</a> support requests, etc., you can contact <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> here. -<p> -<TR><TD BGCOLOR="#ccccc0" ALIGN=left> - <B> - Ok, I'm done reading all this stuff. - </B> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - -<a href="http://uclibc.org/">Well then, click here to return to the uClibc home page.</a> - - - -<!-- End things --> - -</TD></TR> -</TABLE> -</P> - - - -<!-- Footer --> -<HR> -<TABLE WIDTH="100%"> - <TR> - <TD> - <font size="-1" face="arial, helvetica, sans-serif"> - Mail all comments, insults, suggestions and bribes to - <a href="mailto:andersen@codepoet.org">Erik Andersen</a><BR> - </font> - </TD> - - <TD> - <a href="http://www.vim.org"><img border=0 width=90 height=36 - src="images/written.in.vi.png" - alt="This site created with the vi editor"></a> - </TD> - - <TD> - <a href="http://www.gimp.org/"><img border=0 width=90 height=36 - src="images/gfx_by_gimp.png" alt="Graphics by GIMP"></a> - </TD> - - <TD> - <a href="http://www.linuxtoday.com"><img width=90 height=36 - src="images/ltbutton2.png" alt="Linux Today"></a> - </TD> - - <TD> - <p><a href="http://slashdot.org"><img width=90 height=36 - src="images/sdsmall.png" alt="Slashdot"></a> - </TD> - - <TD> - <a href="http://freshmeat.net"><img width=90 height=36 - src="images/fm.mini.png" alt="Freshmeat"></a> - </TD> - - </TR> -</TABLE> +<hr /> -</CENTER> -</BODY> -</HTML> +<!--#include file="footer.html" --> - - 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 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> +<!--#include file="header.html" --> -<HTML> -<HEAD> -<title>uClibc Anonymous CVS Instructions</title> -</HEAD> -<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000"> - -<basefont face="lucida, helvetica, arial" size="3"> - - -<H3>Accessing the uClibc CVS Repository</H3> - -<CENTER> - <TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2> - <TR> - <td bgcolor="#000000"> - <FONT FACE="lucida, helvetica" COLOR="#ccccc0"> - <B>u C l i b c</B> - </FONT> - </TD> - </TR> - </TABLE> - - -</CENTER> - -<TABLE WIDTH="95%" CELLSPACING=1 CELLPADDING=4 BORDER=1> -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="intro"> <BIG><B> - Anonymous CVS - </B></BIG></A> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> +<h3>Anonymous CVS</h3> We allow anonymous (read-only) CVS access to everyone. The first command you need to run for anonymous CVS access is: <pre> cvs -d:pserver:anonymous@uclibc.org:/var/cvs login</pre> <p> -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. <p> 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 </pre> <p> 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: <pre> cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc</pre> This will create a directory called <b>uClibc</b> 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. + +<p> +If you are not already familiar with using CVS, I recommend you visit +this quick <a href="/cvs_howto.html">Introduction to CVS</a>. <p> I usually create a ~/.cvsrc file with the following things in it, and I @@ -76,137 +50,8 @@ cvs update</pre> Because you've only been granted anonymous access to the tree, you won't be able to commit any changes. Changes can be submitted for inclusion by posting -them to the appropriate <a -href="http://www.uclibc.org/mailman/listinfo/uclibc">mailing list</a>. - -<!-- End of Table --> - -</TD></TR> -</TABLE> - - - -<TABLE WIDTH="95%" CELLSPACING=1 CELLPADDING=4 BORDER=1> -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="howto"> <BIG><B> - How to use CVS - </B></BIG></A> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - - -If you want to know all the gory details, you will want to visit -<a href="http://www.cvshome.org/">the CVS main web page</a>.<p> -For the impatient, the following is probably about all you need to know: -<p> - -<dl> - <dt><pre>cvs checkout -c</pre> - <dd>Will list the modules available for checkout - <dt><pre>cvs checkout < module name ></pre> - <dd>Will checkout the named module - <dt><pre>cvs co < module name ></pre> - <dd>Same thing - <dt><pre>cvs update</pre> - - <dd>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. - <dt><pre>cvs up</pre> - <dd>Same thing - <dt><pre>cvs update < file name ></pre> - <dd>Same thing but for just the named file(s)/directory(s). - <dt><pre>cvs commit</pre> - <dd>Will check in all your work. - <dt><pre>cvs add < file name ></pre> - - <dd>Adds the named file/directory into CVS - <dt><pre>cvs remove < file name ></pre> - <dd>Removes the named file/directory from the upstream repository. - <dt><pre>cvs rm < file name ></pre> - <dd>Same thing - <dt><pre>cvs log < file name ></pre> - - <dd>Gives you the complete version history of what has happened to the named file(s). - Along with all tags, all commit messages, etc... - <dt><pre>cvs status < file name ></pre> - <dd>Gives you the current version number of the file(s) in question. - <dt><pre>cvs tag TAGNAME</pre> - <dd>Tags the versions of everything in the repository with the TAGNAME label. - <dt><pre>cvs tag TAGNAME < file name ></pre> - <dd>Tags the named file(s) in the repository with the TAGNAME label. - <dt><pre>cvs diff</pre> - - <dd>Gives you the difference between the local repository and the upstream repository. - <dt><pre>cvs diff < file name ></pre> - <dd>Same but for the named file(s). - <dt><pre>cvs diff -r 1.5 < file name ></pre> - <dd>Same but gives you the difference between the named file(s) and - version 1.5 of the named file(s). - <dt><pre>cvs diff -r TAGNAME < file name ></pre> - - <dd>Same but gives you the difference between the named file(s) and the - of the file tagged TAGNAME in the upstream repository. - <dt><pre>cvs rdiff -r TAGNAME module</pre> - <dd>Gives you a diff (that you can actually use with patch) between the current - version of module and the specified tagged version. - <dt><pre>cvs import < directory to import > < name for new module > start</pre> - <dd>Add a new module into the CVS archive. - <p> - -</dl> - -<!-- End of Table --> - -</TD></TR> -</TABLE> - - - -<!-- Footer --> -<HR> -<TABLE WIDTH="100%"> - <TR> - <TD> - <font size="-1" face="arial, helvetica, sans-serif"> - Mail all comments, insults, suggestions and bribes to - <a href="mailto:andersen@codepoet.org">Erik Andersen</a><BR> - </font> - </TD> - - <TD> - <a href="http://www.vim.org"><img border=0 width=90 height=36 - src="images/written.in.vi.png" - alt="This site created with the vi editor"></a> - </TD> - - <TD> - <a href="http://www.gimp.org/"><img border=0 width=90 height=36 - src="images/gfx_by_gimp.png" alt="Graphics by GIMP"></a> - </TD> - - <TD> - <a href="http://www.linuxtoday.com"><img width=90 height=36 - src="images/ltbutton2.png" alt="Linux Today"></a> - </TD> - - <TD> - <p><a href="http://slashdot.org"><img width=90 height=36 - src="images/sdsmall.png" alt="Slashdot"></a> - </TD> - - <TD> - <a href="http://freshmeat.net"><img width=90 height=36 - src="images/fm.mini.png" alt="Freshmeat"></a> - </TD> - - </TR> -</TABLE> - - -</BODY> -</HTML> +them to the appropriate mailing list. For those that are actively contributing +<a href="cvs_write.html">CVS write access</a> can be made available. +<!--#include file="footer.html" --> 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 @@ +<!--#include file="header.html" --> + + +<h3>How to use CVS</h3> + + +If you want to know all the gory details, you will want to visit +<a href="http://www.cvshome.org/">the CVS main web page</a>.<p> +For the impatient, the following is probably about all you need to know: +<p> + +<dl> + <dt><pre>cvs checkout -c</pre> + <dd>Will list the modules available for checkout + <dt><pre>cvs checkout < module name ></pre> + <dd>Will checkout the named module + <dt><pre>cvs co < module name ></pre> + <dd>Same thing + <dt><pre>cvs update</pre> + + <dd>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. + <dt><pre>cvs up</pre> + <dd>Same thing + <dt><pre>cvs update < file name ></pre> + <dd>Same thing but for just the named file(s)/directory(s). + <dt><pre>cvs commit</pre> + <dd>Will check in all your work. + <dt><pre>cvs add < file name ></pre> + + <dd>Adds the named file/directory into CVS + <dt><pre>cvs remove < file name ></pre> + <dd>Removes the named file/directory from the upstream repository. + <dt><pre>cvs rm < file name ></pre> + <dd>Same thing + <dt><pre>cvs log < file name ></pre> +</dl> + + +<!--#include file="footer.html" --> + 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 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> +<!--#include file="header.html" --> -<HTML> -<HEAD> -<title>uClibc CVS Read/Write Instructions</title> -</HEAD> - -<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000"> - -<basefont face="lucida, helvetica, arial" size="3"> - - -<H3>Accessing the uClibc CVS Repository</H3> - -<CENTER> - <TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2> - <TR> - <td bgcolor="#000000"> - <FONT FACE="lucida, helvetica" COLOR="#ccccc0"> - <B>u C l i b c</B> - </FONT> - </TD> - </TR> - </TABLE> - - -</CENTER> - -<TABLE WIDTH="95%" CELLSPACING=1 CELLPADDING=4 BORDER=1> -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="intro"> <BIG><B> - CVS Read/Write Access - </B></BIG></A> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> +<h3>CVS Read/Write Access</h3> 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: <pre> $ export CVS_RSH=/usr/bin/ssh -$ export CVSROOT='username@cvs.uclibc.org:/var/cvs'</pre> +$ export CVSROOT='username@cvs.busybox.net:/var/cvs'</pre> <br> It goes without saying you must change <em>username</em> 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 <a href="http://www.codepoet.org/~andersen/erik/gpg.asc">public key</a>. - -<!-- End of Table --> - -</TD></TR> -</TABLE> - - - -<!-- Footer --> -<HR> -<TABLE WIDTH="100%"> - <TR> - <TD> - <font size="-1" face="arial, helvetica, sans-serif"> - Mail all comments, insults, suggestions and bribes to - <a href="mailto:andersen@codepoet.org">Erik Andersen</a><BR> - </font> - </TD> - - <TD> - <a href="http://www.vim.org"><img border=0 width=90 height=36 - src="images/written.in.vi.png" - alt="This site created with the vi editor"></a> - </TD> - - <TD> - <a href="http://www.gimp.org/"><img border=0 width=90 height=36 - src="images/gfx_by_gimp.png" alt="Graphics by GIMP"></a> - </TD> - - <TD> - <a href="http://www.linuxtoday.com"><img width=90 height=36 - src="images/ltbutton2.png" alt="Linux Today"></a> - </TD> - - <TD> - <p><a href="http://slashdot.org"><img width=90 height=36 - src="images/sdsmall.png" alt="Slashdot"></a> - </TD> - - <TD> - <a href="http://freshmeat.net"><img width=90 height=36 - src="images/fm.mini.png" alt="Freshmeat"></a> - </TD> - - </TR> -</TABLE> - - -</BODY> -</HTML> - +<!--#include file="footer.html" --> 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 @@ +<!--#include file="header.html" --> + + + +<h3>Download</h3> + +Source for the latest release can always be +downloaded from <a href="downloads/">http://www.uclibc.org/downloads</a> + +<p> +You can also obtain <a href= "downloads/snapshots/">Daily Snapshots</a> of +the latest CVS source tree for those wishing to follow uClibc development, +but cannot or do not wish to use CVS. + +<p> + +<ul> + <li> Click here to <a href="/cgi-bin/cvsweb/uClibc/"> + browsable the CVS tree</a>. + </li> + + <li>Anonymous <a href="cvs_anon.html">CVS access</a> is available. + </li> + + <li>For those that are actively contributing there is + even <a href="cvs_write.html">CVS write access</a>. + </li> + +</ul> + +<!--#include file="footer.html" --> + 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 @@ +<!-- Footer --> + + + </td> + </tr> + </table> + + <p> + <font face="arial, helvetica, sans-serif" size="-1"> + <a HREF="/copyright.txt">Copyright © 1999-2003 Erik Andersen</a> + <br> + Mail all comments, insults, suggestions and bribes to + <br> + Erik Andersen <A HREF="mailto:andersen@codepoet.org">andersen@codepoet.org</A><BR> + </font> + + </body> +</html> 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 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" +"http://www.w3.org/TR/REC-html40/loose.dtd"> + +<html> + <head> + <title>uClibc</title> + <style type="text/css"> + body { + background-color: #DEE2DE; + color: #000000; + } + :link { color: #660000 } + :visited { color: #660000 } + :active { color: #660000 } + td.c2 {font-family: arial, helvetica, sans-serif; font-size: 80%} + td.c1 {font-family: lucida, helvetica; font-size: 248%} + </style> + </head> + + <body> + <basefont face="lucida, helvetica, arial" size="3"> + + + + +<table border="0" cellpadding="0" cellspacing="0"> + + +<tr> +<td width="16%"> + <div class="c3"> + <table border="0" cellspacing="1" cellpadding="2"> + <tr> + <td class="c1">uClibc</td> + </tr> + </table> + </div> +</td> +</tr> + +<tr> + +<td valign="TOP"> + <br><a href="/">Home</a> + <br><a href="/lists.html">Mailing Lists</a> + <br><a href="/FAQ.html">FAQ</a> + <br><a href="/news.html">Latest News</a> + <br><a href="/download.html">Download</a> + <br><a href="/toolchains.html">Toolchains</a> + <br><a href="/cvs_anon.html">Accessing CVS</a> + <br><a href="/cgi-bin/cvsweb/uClibc/">Browse CVS</a> + <br><a href="/products.html">Products</a> + <br><a href="/other_libs.html">Other libcs</a> + + </dl> + <dl> + <dt><b>Related Sites</b> + <br><a href="http://busybox.net/">BusyBox</a> + <br><a href="http://udhcp.busybox.net/">udhcp</a> + <br><a href="http://tinylogin.busybox.net/">tinylogin</a> + <br><a href="http://www.ucdot.org/">uCdot</a> + <br><a href="http://www.linuxdevices.com">LinuxDevices</a> + <br><a href="http://slashdot.org/">Slashdot</a> + <br><a href="http://freshmeat.net/">Freshmeat</a> + <br><a href="http://linuxtoday.com/">Linux Today</a> + <br><a href="http://lwn.net/">Linux Weekly News</a> + <br><a href="http://www.linuxdoc.org/HOWTO/">Linux HOWTOs</a> + +<!-- + + <a href="http://validator.w3.org/check/referer"><img + src="/images/vh40.gif" height=31 width=88 + align=left border=0 alt="Valid HTML 4.0!"></a> +--> + +</td> + + +<td Valign="TOP"> + diff --git a/docs/uclibc.org/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 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> - -<HTML> -<HEAD> -<TITLE>uClibc -- a C library for embedded systems</TITLE> -</HEAD> - -<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000"> - -<basefont face="lucida, helvetica, arial" size="3"> - - -<p> - -<CENTER> -<TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2> - <TR> - <td bgcolor="#000000"> - <FONT FACE="lucida, helvetica" COLOR="#ccccc0"> - <B>µ C l i b c</B> - </FONT> - </TD> - </TR> -</TABLE> -<p> -</CENTER> +<!--#include file="header.html" --> <!-- Begin Introduction section --> +<h3>A C library for embedded Linux</h3> -<TABLE WIDTH=95% CELLSPACING=1 CELLPADDING=4 BORDER=1> -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="intro"> <BIG><B> - uClibc -- a C library for embedded systems - </font> - </A></B></BIG> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> +uClibc (aka µClibc/pronounced yew-see-lib-see) is a C library for developing +embedded Linux systems. It is much smaller than the <a +href="http://www.gnu.org/software/libc/libc.html">GNU C Library</a>, but nearly +all applications supported by glibc also work perfectly with uClibc. Porting +applications from glibc to uClibc typically involves just recompiling the +source code. uClibc even supports shared libraries and threading. It currently +runs on <a href="http://kernel.org/">standard Linux</a> and <a +href="http://www.uclinux.org">MMU-less (also known as µClinux)</a> systems with +support for alpha, ARM, cris, i386, i960, h8300, m68k, mips/mipsel, PowerPC, +SH, SPARC, and v850 processors. -<a href="http://www.uclibc.org">uClibc</a> (aka µClibc/pronounced -yew-see-lib-see) is a C library for developing embedded Linux systems. -It is much smaller than the -<a href="http://www.gnu.org/software/libc/libc.html">GNU C Library</a>, -but nearly all applications supported by glibc also work perfectly with -uClibc. Porting applications from glibc to uClibc typically involves -just recompiling the source code. uClibc even supports shared libraries -and threading. It currently runs on <a href="http://kernel.org/">standard Linux</a> -and <a href="http://www.uclinux.org">MMU-less (also known as µClinux)</a> -systems with support for alpha, ARM, cris, i386, i960, h8300, m68k, mips/mipsel, -PowerPC, SH, SPARC, and v850 processors. <p> If you are building an embedded Linux system and you find that -glibc is eating up too much space, you 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 <a href="http://www.codepoet.org/andersen/erik/erik.html">Erik Andersen</a> + + +<p> + +uClibc is maintained by <a href= +"http://codepoet.org/andersen/erik/erik.html">Erik Andersen</a> and is licensed under the <a href="http://www.gnu.org/copyleft/lgpl.html">GNU LIBRARY GENERAL PUBLIC LICENSE</a> . This license allows you to make closed source commercial applications using -uClibc (Please consider sharing some of the money you make ;-). You do not need +uClibc. (Please consider sharing some of the money you make ;-). You do not need to give away all your source code just because you use uClibc and/or run on Linux. +See the <a href="FAQ.html">list of Frequently Asked Questions</a> for details. <p> -<h3>Mailing List Information</h3> - -uClibc has a <a href="/lists/uclibc/">mailing list</a>.<br> -To subscribe, go and visit -<a href="http://www.uclibc.org/mailman/listinfo/uclibc">this page</a>. - -<p> - -<h3>Frequently Asked Questions</h3> - -Before asking questions on the uClibc mailing list, -you might want to take a look at the -<a href="FAQ.html">list of Frequently Asked Questions</a> -or -you might want to search the mailing list archives... -<form method="GET" action="http://www.google.com/custom"> -<input type="hidden" name="domains" value="uclibc.org"> -<input type="hidden" name="sitesearch" value="uclibc.org"> -<a href="http://www.google.com"><img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google" height="32" width="75" align="middle"></a> <input type="text" name="q" size="31" maxlength="255" value=""> <input type="submit" name="sa" value="search the mailing list archives">... -</form> - -<h3>Working Applications List</h3> - - These days, pretty much everything compiles with uClibc. This - is a <a href="uClibc-apps.html">list of applications</a> 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 <em>do not compile</em> or <em>do not work</em> - properly with uClibc. Submissions are welcome! +<h3>Sponsors</h3> - - -<!-- Begin Latest News section --> +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! -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="news"> - <BIG><B> - Latest News</A> - </B></BIG> - </A> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> <ul> + <li><a href="http://www.penguru.net">Penguru Consulting</a><br> + Custom development for embedded Linux systems and multimedia platforms + </li> - <p> - <li> <b>13 November 2003, uClibc 0.9.23 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.23. Of course, we are somewhat less than pleased that there - were configuration problems in the previous release that made such it - necessary to release .23 so quickly. Updated uClibc development systems - using uClibc 0.9.23 are being built and will be posted shortly. And Erik - has built Debian stable (woody) for x86 with uClibc and it runs great. - - <p> - - This release continues to be binary compatible with uClibc 0.9.21 and - 0.9.22 -- as long as you pick compatible configuration options. Enabling - or disabling things like soft-float, locale, wide char support, or changing - cpu optimizations are all good examples of binary incompatible - configuration options. If have changed any of those sorts of options (or - if you are not sure!) you will need to recompile all your applications and - libraries. - - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.23.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - <p> - - - <p> - <li> <b>8 November 2003, uClibc 0.9.22 Released</b> - <br> - - CodePoet Consulting is pleased to announce the immediate availability of - uClibc 0.9.22. This release has been cooking for a couple of months now - and is looking quite solid. We have done quite a lot of testing with this - release and things are looking good. And Erik has built Debian stable - (woody) for x86 with uClibc and it runs great. Expect that to be released - in the next few days. - - <p> - - This release is binary compatible with uClibc 0.9.21 -- as long as you pick - compatible configuration options. Enabling or disabling things like - soft-float, locale, wide char support, or changing cpu optimizations are - all good examples of binary incompatible configuration options. If have - changed any of those sorts of options (or if you are not sure!) you will - need to recompile all your applications and libraries. - - <p> - - Updated uClibc development systems using uClibc 0.9.22 will be made - available within a few days. Meanwhile, we invite you to try out uClibc - with the latest <a href="http://ltp.sourceforge.net/">Linux Test Project - test suite</a> (you will need to apply a small <a - href="http://www.uclibc.org/cgi-bin/cvsweb/buildroot/sources/ltp-testsuite.patch?rev=1.3">patch</a>. - And also give the latest Perl and Python test suites a try as well. - If you find any bugs in uClibc, PLEASE let us know! - <p> - - As usual, the - <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, - <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, - and <a href="http://www.uclibc.org/downloads/uClibc-0.9.22.tar.bz2">source code for this release</a> - are available <a href="http://www.uclibc.org/downloads/">here</a>. - - <p> - - - <p> - <li> <b>30 September 2003, dev systems updated to uClibc 0.9.21+</b> - <br> - - The uClibc development systems for - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a>, - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mips</a>, - have been updated to uClibc 0.9.21 (plus all the CVS updates up to - today). Several problems have been fixed up, - gcc has been updated to version 3.3.1, binutils was updated to 2.14.90.0.6, and - <em>tada</em> everything finally works for cross compiling. These were - all cross compiled (which really makes things faster since the older - mipsel releases used to take 2 days to build!) - - <p> - These are ~100 MB ext2 filesystems that run natively on the specified - architecture. They contains all the development software you need to build - your own uClibc applications, including bash, coreutils, findutils, - diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace, - make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh perl, - and more. And of course, everything is dynamically linked against uClibc. - By using a uClibc only system, you can avoid all the painful - cross-configuration problems that have made using uClibc somewhat painful - in the past. If you want to quickly get started with testing or using - uClibc you should give these images a try. You can loop mount and them - you can chroot into them, you can boot into with using user-mode Linux, - and you can even 'dd' them to a spare partition and use resize2fs to make - them fill the drive. Whatever works for you. - - <p> If you would like to build your own custom uClibc system, you can - use <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>, which is - how these uClibc development systems were created. - <p> - - - <p> <li> <b>Old News</b> - <br> - - <a href="old-news.html">Click here to read older news</a>. - <p> + <li><a href="http://opensource.se/">opensource.se</a><br> + Embedded open source consulting in Europe. + </li> + <li><a href="http://www.codepoet-consulting.com">Codepoet Consulting</a><br> + Custom Linux, embedded Linux, BusyBox, and uClibc + development. + </li> </ul> +If you wish to be a sponsor, or if you have already contributed and would like +your name added here, email <a href= "mailto:andersen@codepoet.org">Erik</a>. -<!-- Begin Sponsors section --> - -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="sponsors"><BIG><B> - Sponsors - </A></B></BIG> -</TD></TR> -<tr><td bgcolor="#EEEEE0"> - - 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). - - <ul> - <li><a href="http://www.penguru.net">Penguru Consulting</a><br> - Custom development for embedded Linux systems and multimedia platforms</li> - - <li><a href="http://opensource.se/">opensource.se</a><br> - Embedded open source consulting in Europe.</li> - - <li><a href="http://www.codepoet-consulting.com">Codepoet Consulting</a><br> - Custom Linux, embedded Linux, BusyBox, and uClibc development.</li> - </ul> - - <table CELLSPACING=6 CELLPADDING=6 BORDER=0><tr> - <td> - Do you like uClibc? Do you need support? Do you need some features - added? Then why not help out? We are happy to accept donations - (such as bandwidth, mirrors sites, and hardware for the various - architectures). We can also provide support contracts, and implement - funded feature requests. To contribute, you can either click on the - Donate image to donate using PayPal, or you can contact Erik at - <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> - (we have a credit card machine so you can avoid PayPal if you wish). - </td> - - <td> - <!-- Begin PayPal Logo --> - <form action="https://www.paypal.com/cgi-bin/webscr" method="post"> - <input type="hidden" name="cmd" value="_xclick"> - <input type="hidden" name="business" value="andersen@codepoet.org"> - <input type="hidden" name="item_name" value="Support uClibc"> - <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png"> - <input type="hidden" name="no_shipping" value="1"> - <input type="image" src="images/donate.png" border="0" name="submit" alt="Make donation using PayPal"> - </form> - </td> - <!-- End PayPal Logo --> - - </tr> - </table> - - - -<!-- Begin Download section --> - -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="download"><BIG><B> - Download - </A></B></BIG> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> -<ul> - <li> Source for the latest release can always be downloaded from - <a href="downloads/">http://www.uclibc.org/downloads</a> - - <li> You may want to download uClibc from the closest - <a href="http://kernel.org/mirrors/">kernel.org mirror site</a>. - Just pick the closest mirror site, and then go to the - <a href="http://www.kernel.org/pub/linux/libs/uclibc/">/pub/linux/libs/uclibc/</a> - directory to download uClibc. - - <li> A <a href="downloads/snapshots/">daily snapshot of the source</a> is - available for those wishing to follow uClibc developments, but cannot - or do not wish to use CVS. - - <li> uClibc has a publically <a href="/cgi-bin/cvsweb/uClibc/">browsable CVS tree</a>. - - <li> <a href="cvs_anon.html">Anonymous CVS access</a> is available to let you track development. - <li> <a href="cvs_write.html">CVS write access</a> is also available for those that are actively - contributing. -</ul> - - - -<!-- Begin Toolchain section --> - -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="toolchain"><BIG><B> - Toolchains - </A></B></BIG> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> -<ul> - - <li>Steven J. Hill has kindly provided - <a href="ftp://ftp.realitydiluted.com/linux/MIPS/toolchains">RPMs and SRPMs</a> - with toolchains for mips. - - <li>You can build your own - <a href="/cgi-bin/cvsweb/toolchain/">uClibc toolchain</a> - using these Makefiles which automagically download all the source - needed code and compile it for you. - - <li>uClibc development systems for - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a> - and - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, - and - <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a> - are available and contain complete gcc 3.2.2 toolchains. - - <li>You can compile your own uClibc development system using - <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>. - -</ul> - - - -<!-- Begin Links section --> - -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="links"> - <BIG><B> - Other Open Source C libraries: - </A> - </B></BIG> - </A> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - - -I am currently aware of the following open source C libraries. - -<ul> - - -<li><a href="http://www.gnu.org/software/libc/libc.html">GNU C Library (aka glibc)</a> -<li> <a href="http://www.k9wk.com/cdoc.html">Al's FREE C Runtime Library</a> -<li><a href="http://www.fefe.de/dietlibc/">diet libc </a> -<li>the <a href="http://www.cs.vu.nl/~ast/minix.html">minix</a> - <a href="http://www.cs.vu.nl/cgi-bin/raw/pub/minix/2.0.0/src.tar" - >C library</a> -<li> <a href="http://sources.redhat.com/newlib/">newlib</a> -<li>and there is a - <a href="ftp://sourceware.cygnus.com/pub/ecos/">C library</a>, for - <a href="http://sources.redhat.com/ecos/">eCos</a> as well. - -<ul> - - - -<!-- Begin Links section --> - -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="links"> - <BIG><B> - Links to other useful stuff - </A> - </B></BIG> - </A> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - -<ul> - - <li> <a href="http://www.uclibc.org/">The uClibc home page</a> - <p> - - <li> <a href="/cgi-bin/cvsweb/uClibc/">The uClibc CVS tree</a> - <p> - - <li> <a href="http://busybox.net/">BusyBox</a> - <p> - - <li> <a href="http://udhcp.busybox.net/">udhcp</a> - <p> - - <li> <a href="http://www.uCdot.org/">Embedded Linux Developer Forum</a> - <p> - - <li> <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> - <p> - -</ul> - - - -<!-- End of Table --> - -</TD></TR> -</TABLE> -</P> - - - -<!-- Footer --> -<HR> -<TABLE WIDTH="100%"> - <TR> - <TD> - <font size="-1" face="arial, helvetica, sans-serif"> - Mail all comments, insults, suggestions and bribes to - <a href="mailto:andersen@codepoet.org">Erik Andersen</a><BR> - </font> - </TD> - - <TD> - <a href="http://www.vim.org"><img border=0 width=90 height=36 - src="images/written.in.vi.png" - alt="This site created with the vi editor"></a> - </TD> - - <TD> - <a href="http://www.gimp.org/"><img border=0 width=90 height=36 - src="images/gfx_by_gimp.png" alt="Graphics by GIMP"></a> - </TD> - - <TD> - <a href="http://www.linuxtoday.com"><img width=90 height=36 - src="images/ltbutton2.png" alt="Linux Today"></a> - </TD> - - <TD> - <p><a href="http://slashdot.org"><img width=90 height=36 - src="images/sdsmall.png" alt="Slashdot"></a> - </TD> - - <TD> - <a href="http://freshmeat.net"><img width=90 height=36 - src="images/fm.mini.png" alt="Freshmeat"></a> - </TD> - - </TR> -</TABLE> +<p> +<table BORDER=0> +<tr> +<td> +Do you like uClibc? Do you need support? Do you need some features +added? Then why not help out? We are happy to accept donations +(such as bandwidth, mirrors sites, and hardware for the various +architectures). We can also provide support contracts, and implement +funded feature requests. To contribute, you can either click on the +Donate image to donate using PayPal, or you can contact Erik at +<a href="http://codepoet-consulting.com/">CodePoet Consulting</a> +(we have a credit card machine so you can avoid PayPal if you wish). +</td> + +<td> +<!-- Begin PayPal Logo --> +<form action="https://www.paypal.com/cgi-bin/webscr" method="post"> + <input type="hidden" name="cmd" value="_xclick"> + <input type="hidden" name="business" value="andersen@codepoet.org"> + <input type="hidden" name="item_name" value="Support uClibc"> + <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png"> + <input type="hidden" name="no_shipping" value="1"> + <input type="image" src="images/donate.png" border="0" name="submit" alt="Make donation using PayPal"> +</form> +</td> +<!-- End PayPal Logo --> +</tr> +</table> -</BODY> -</HTML> - +<!--#include file="footer.html" --> 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 @@ +<!--#include file="header.html" --> + + +<!-- Begin Introduction section --> + +<h3>Mailing List Information</h3> +uClibc has a <a href="/lists/uclibc/">mailing list</a> for discussion and +development. You can subscribe by visiting +<a href="http://codepoet.org/mailman/listinfo/uclibc">this page</a>. + +<p> +There is also a mailing list for <a href="/lists/uclibc-cvs/">active developers</a> +wishing to read the complete diff of each and every change to uClibc -- not for the +faint of heart. Active developers can subscribe by visiting +<a href="http://codepoet.org/mailman/listinfo/uclibc-cvs">this page</a>. + +<p> + + +<h3>Search the List Archives</h3> +Please search the mailing list archives before asking questions on the mailing +list, since there is a good chance someone else has asked the same question +before. Checking the archives is a great way to avoid annoying everyone on the +list with frequently asked questions... You should also check the +<a href="FAQ.html">list of Frequently Asked Questions</a>, since the answer +you need may very well be listed there. + +<p> + +<center> +<form method="GET" action="http://www.google.com/custom"> +<input type="hidden" name="domains" value="uclibc.org"> +<input type="hidden" name="sitesearch" value="uclibc.org"> +<input type="text" name="q" size="31" maxlength="255" value=""> +<br> +<input type="submit" name="sa" value="search the mailing list archives"> +<br> +<a href="http://www.google.com"><img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google" height="32" width="75" align="middle"></a> +<br> +</form> +</center> + + + +<!--#include file="footer.html" --> 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 @@ +<!--#include file="header.html" --> + + +<ul> + + <p> + <li> <b>13 November 2003, uClibc 0.9.23 Released</b> + <br> + + CodePoet Consulting is pleased to announce the immediate availability of + uClibc 0.9.23. Of course, we are somewhat less than pleased that there + were configuration problems in the previous release that made such it + necessary to release .23 so quickly. Updated uClibc development systems + using uClibc 0.9.23 are being built and will be posted shortly. And Erik + has built Debian stable (woody) for x86 with uClibc and it runs great. + + <p> + + This release continues to be binary compatible with uClibc 0.9.21 and + 0.9.22 -- as long as you pick compatible configuration options. Enabling + or disabling things like soft-float, locale, wide char support, or changing + cpu optimizations are all good examples of binary incompatible + configuration options. If have changed any of those sorts of options (or + if you are not sure!) you will need to recompile all your applications and + libraries. + + <p> + + As usual, the + <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, + <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, + and <a href="http://www.uclibc.org/downloads/uClibc-0.9.23.tar.bz2">source code for this release</a> + are available <a href="http://www.uclibc.org/downloads/">here</a>. + + <p> + + + <p> + <li> <b>8 November 2003, uClibc 0.9.22 Released</b> + <br> + + CodePoet Consulting is pleased to announce the immediate availability of + uClibc 0.9.22. This release has been cooking for a couple of months now + and is looking quite solid. We have done quite a lot of testing with this + release and things are looking good. And Erik has built Debian stable + (woody) for x86 with uClibc and it runs great. Expect that to be released + in the next few days. + + <p> + + This release is binary compatible with uClibc 0.9.21 -- as long as you pick + compatible configuration options. Enabling or disabling things like + soft-float, locale, wide char support, or changing cpu optimizations are + all good examples of binary incompatible configuration options. If have + changed any of those sorts of options (or if you are not sure!) you will + need to recompile all your applications and libraries. + + <p> + + Updated uClibc development systems using uClibc 0.9.22 will be made + available within a few days. Meanwhile, we invite you to try out uClibc + with the latest <a href="http://ltp.sourceforge.net/">Linux Test Project + test suite</a> (you will need to apply a small <a + href="http://www.uclibc.org/cgi-bin/cvsweb/buildroot/sources/ltp-testsuite.patch?rev=1.3">patch</a>. + And also give the latest Perl and Python test suites a try as well. + If you find any bugs in uClibc, PLEASE let us know! + <p> + + As usual, the + <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, + <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, + and <a href="http://www.uclibc.org/downloads/uClibc-0.9.22.tar.bz2">source code for this release</a> + are available <a href="http://www.uclibc.org/downloads/">here</a>. + + <p> + + + <p> + <li> <b>30 September 2003, dev systems updated to uClibc 0.9.21+</b> + <br> + + The uClibc development systems for + <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a>, + <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>, + <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a>, + <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mips</a>, + have been updated to uClibc 0.9.21 (plus all the CVS updates up to + today). Several problems have been fixed up, + gcc has been updated to version 3.3.1, binutils was updated to 2.14.90.0.6, and + <em>tada</em> everything finally works for cross compiling. These were + all cross compiled (which really makes things faster since the older + mipsel releases used to take 2 days to build!) + + <p> + These are ~100 MB ext2 filesystems that run natively on the specified + architecture. They contains all the development software you need to build + your own uClibc applications, including bash, coreutils, findutils, + diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace, + make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh perl, + and more. And of course, everything is dynamically linked against uClibc. + By using a uClibc only system, you can avoid all the painful + cross-configuration problems that have made using uClibc somewhat painful + in the past. If you want to quickly get started with testing or using + uClibc you should give these images a try. You can loop mount and them + you can chroot into them, you can boot into with using user-mode Linux, + and you can even 'dd' them to a spare partition and use resize2fs to make + them fill the drive. Whatever works for you. + + <p> If you would like to build your own custom uClibc system, you can + use <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>, which is + how these uClibc development systems were created. + <p> + + + <p> <li> <b>Old News</b> + <br> + <a href="/oldnews.html">Click here to read older news</a> + <p> + + +</ul> + +<!--#include file="footer.html" --> + diff --git a/docs/uclibc.org/old-news.html b/docs/uclibc.org/oldnews.html index d7f0e6e42..ccdda769b 100644 --- a/docs/uclibc.org/old-news.html +++ b/docs/uclibc.org/oldnews.html @@ -1,56 +1,8 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> +<!--#include file="header.html" --> -<HTML> -<HEAD> -<TITLE>uClibc -- a C library for embedded systems</TITLE> -</HEAD> -<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000"> +<ul> -<basefont face="lucida, helvetica, arial" size="3"> - - -<CENTER> -<p> - -<TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2> - <TR> - <td bgcolor="#000000"> - <FONT FACE="lucida, helvetica" COLOR="#ccccc0"> - <B>µ C l i b c</B> - </FONT> - </TD> - </TR> -</TABLE> -<p> - - -<!-- Begin Introduction section --> - - -<TABLE WIDTH=95% CELLSPACING=1 CELLPADDING=4 BORDER=1> - <TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="intro"> <BIG><B> - uClibc -- a C library for embedded systems - </A></B></BIG> - </TD></TR> - <TR><TD BGCOLOR="#eeeee0"> - - <a href="index.html">Click Here to Return to the main uClibc webpage</a>. - <p> - -<!-- Begin Older News section --> - -<TR><TD BGCOLOR="#ccccc0" ALIGN=center> - <A NAME="news"> - <BIG><B> - Older News</A> - </B></BIG> - </A> -</TD></TR> -<TR><TD BGCOLOR="#eeeee0"> - - <ul> <p> <li> <b>9 September 2003, uClibc 0.9.21 Released</b> @@ -926,63 +878,10 @@ 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. - + that it exists and is getting to be usable. </ul> -<!-- End of Table --> - -</TD></TR> -</TABLE> -</P> - - - -<!-- Footer --> -<HR> -<TABLE WIDTH="100%"> - <TR> - <TD> - <font size="-1" face="arial, helvetica, sans-serif"> - Mail all comments, insults, suggestions and bribes to - <a href="mailto:andersen@codepoet.org">Erik Andersen</a><BR> - </font> - </TD> - - <TD> - <a href="http://www.vim.org"><img border=0 width=90 height=36 - src="images/written.in.vi.png" - alt="This site created with the vi editor"></a> - </TD> - - <TD> - <a href="http://www.gimp.org/"><img border=0 width=90 height=36 - src="images/gfx_by_gimp.png" alt="Graphics by GIMP"></a> - </TD> - - <TD> - <a href="http://www.linuxtoday.com"><img width=90 height=36 - src="images/ltbutton2.png" alt="Linux Today"></a> - </TD> - - <TD> - <p><a href="http://slashdot.org"><img width=90 height=36 - src="images/sdsmall.png" alt="Slashdot"></a> - </TD> - - <TD> - <a href="http://freshmeat.net"><img width=90 height=36 - src="images/fm.mini.png" alt="Freshmeat"></a> - </TD> - - </TR> -</TABLE> - - -</CENTER> -</BODY> -</HTML> +<!--#include file="footer.html" --> - 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 @@ +<!--#include file="header.html" --> + + +<h3>Other Open Source C libraries</h3> +I am currently aware of the following open source C libraries. + +<ul> + + <li><a href="http://www.gnu.org/software/libc/libc.html">The GNU C Library</a> + <li> <a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/">The FreeBSD C Library</a> + <li> <a href="http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/">The NetBSD C Library</a> + <li> <a href="http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/">The OpenBSD C Library</a> + <li><a href="http://www.fefe.de/dietlibc/">dietlibc</a> + <li> <a href="http://sources.redhat.com/newlib/">newlib</a> + <li> <a href="http://www.k9wk.com/cdoc.html">Al's FREE C Runtime Library</a> + <li>the <a href="http://www.cs.vu.nl/~ast/minix.html">minix</a> + <a href="http://www.cs.vu.nl/cgi-bin/raw/pub/minix/2.0.0/src.tar">C library</a> + <li>and there is a <a href="ftp://ecos.sourceware.org/pub/ecos/">C library</a>, + for <a href="http://ecos.sourceware.org/">eCos</a> as well. + +<ul> + +<!--#include file="footer.html" --> + diff --git a/docs/uclibc.org/products.html b/docs/uclibc.org/products.html new file mode 100644 index 000000000..0525fcfb4 --- /dev/null +++ b/docs/uclibc.org/products.html @@ -0,0 +1,27 @@ +<!--#include file="header.html" --> + + +<h3>Products/Projects Using uClibc</h3> + +Do you use uClibc? I'd love to know about it and I'd be happy to link to you. + +<p> +I know of the following products and/or projects that use uClibc -- +listed in the order I happen to add them to the web page: + +<ul> + + +<li><a href="/cgi-bin/cvsweb/buildroot/">buildroot</a> a configurable +means for building your own busybox/uClibc based system systems. + +</li><li><a href="http://tuxscreen.net">Tuxscreen Linux Phone</a> + +</li><li><a href="http://www.linksys.com/products/product.asp?prid=508">Linksys WRT54G - Wireless-G Broadband Router</a> + + +</ul> + + +<!--#include file="footer.html" --> + 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 @@ +<!--#include file="header.html" --> + + +<h3>Toolchains</h3> +To use uClibc, you need to have a toolchain, which is composed +of <a href="http://sources.redhat.com/binutils/">binutils</a>, +<a href="http://gcc.gnu.org/">gcc</a>, and of course uClibc. + +<ul> + + <li>You can build your own + <a href="/cgi-bin/cvsweb/toolchain/gcc-3.3.x/">uClibc toolchain</a> + using this to automagically download all the needed source code + and compile everything for you. + <p> + + <li>Steven J. Hill has kindly provided + <a href="ftp://ftp.realitydiluted.com/linux/MIPS/toolchains">RPMs and SRPMs</a> + with toolchains for mips. + <p> + + <li>You can compile your own uClibc development system using + <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>. + <p> + + <li>Prebuilt uClibc development systems for + <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a> + and + <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a> + and + <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mipsel</a> + 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. + <p> + +</ul> + +<!--#include file="footer.html" --> + |