1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>
<TITLE>uClibc -- a C library for embedded systems</TITLE>
</HEAD>
<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000">
<basefont face="lucida, helvetica, arial" size="3">
<CENTER>
<p>
<TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2>
<TR>
<td bgcolor="#000000">
<FONT FACE="lucida, helvetica" COLOR="#ccccc0">
<B>µ C l i b c</B>
</FONT>
</TD>
</TR>
</TABLE>
<p>
<!-- Begin 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
</font>
</A></B></BIG>
</TD></TR>
<TR><TD BGCOLOR="#eeeee0">
<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, 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 uClibc. If you are
building a huge fileserver with 12 Terabytes of storage, than using
glibc may be a better choice...
<p>
uClibc is maintained by
<a href="http://www.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
to give away all your source code just because you use uClibc and/or run on Linux.
<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!
<!-- Begin Latest News section -->
<TR><TD BGCOLOR="#ccccc0" ALIGN=center>
<A NAME="news">
<BIG><B>
Latest News</A>
</B></BIG>
</A>
</TD></TR>
<TR><TD BGCOLOR="#eeeee0">
<ul>
<p>
<li> <b>10 February 2003, development system updates</b>
<br>
A few problems have turned up in both uClibc and the development
systems since the last release. The development systems for
<a href="http://www.uclibc.org/downloads/root_fs_0.9.17-i386.bz2">i386</a>,
<a href="http://www.uclibc.org/downloads/root_fs_0.9.17-arm.bz2">arm</a>
and
<a href="http://www.uclibc.org/downloads/root_fs_0.9.17-powerpc.bz2">powerpc</a>,
have been updated to address these issues. The arm image also includes
the recent fix allowing gdb to properly debug arm binaries... Have Fun.
<p>
<p>
<li> <b>25 January 2003, uClibc 0.9.17 Released</b>
<br>
CodePoet Consulting is pleased to announce the immediate availability of
uClibc 0.9.17. The biggest piece of news with this release, thanks to
Manuel Novoa's continuing hard work, is that we now have fully standards
compliant locale support (optional of course). The support works nicely,
(though configuring the locales you wish to support is still manual -- a
task for the next release). Full locale data for over 300 locales adds
approximately 250k. The collation data for all supported locales is
roughly 180k. This may seem rather large to some -- but it is much smaller
than the approximately 40 MB needed by Glibc to provide the same data. And
if you don't need it, you can either disable locale support entirely, or
enable a smaller set of locales.
<p>
This release also fixes <em>lots and lots</em> of bugs. The arm
architecture support (I am embarrassed to note) was totally broken in the
last release, but is now working as expected. A security problem (a
buffer overflow in getlogin_r) was fixed. And there were architecture
updates across the board (x86, arm, powerpc, cris, h8300, sparc, and mips).
And of course, this release includes the usual pile of bug fixes. Many
thanks for the large number of patches and fixes that were contributed!
<p>
Unfortunately, this release is not binary compatible with earlier uClibc
releases. As noted as item 3 <a href="downloads/Glibc_vs_uClibc_Differences.txt">here</a>,
uClibc does not (yet) attempt to
ensure binary compatibility across releases. We will eventually do that
(once we reach the "1.0" release) but not yet. A few bugs turned up that
needed to be fixed, and the only good way to fix them was to change some
fundamental data structure sizes. As a result, this release is _NOT_
binary compatible with earlier releases -- you will need to recompile your
applications. The x86, arm, powerpc, and mips architectures (i.e. the
systems Erik has available in his office for testing) have been tested and
are known to work following this change. Other architectures <em>may</em>
need additional updates. Sorry about that, but it had to be done.
<p>
As usual, the
<a href="http://www.kernel.org/pub/linux/libs/uclibc/Changelog">Changelog</a>
and <a href="http://www.kernel.org/pub/linux/libs/uclibc/uClibc-0.9.17.tar.bz2">source code</a>
for this release are available <a href="http://www.kernel.org/pub/linux/libs/uclibc/">here</a>.
You might want to download uClibc from the closest
<a href="http://kernel.org/mirrors/">kernel.org mirror site</a>.
Just pick the closest mirror site, and then go to
<a href="http://www.kernel.org/pub/linux/libs/uclibc/">
http://www.XX.kernel.org/pub/linux/libs/uclibc/</a>
to download uClibc, where XX is your two letter country code.
<p>
<p>
<li> <b>25 January 2003, dev system updates, arm image released</b>
<br>
A number of additional problems have been fixed and the arm build
is now, finally, compiling and working as expected. As such,
I have updated the <a href="http://www.uclibc.org/downloads/root_fs_0.9.17-i386.bz2">
i386 development system image</a>, the
<a href="http://www.uclibc.org/downloads/root_fs_0.9.17-powerpc.bz2">
powerpc development system image</a>, and I am also releasing
upon an unsuspecting world the brand new
<a href="http://www.uclibc.org/downloads/root_fs_0.9.17-arm.bz2">
arm development system image</a>!
Have fun!
<p>
All three development system images were compiled and built using the stock
<a href="/cgi-bin/cvsweb/buildroot/">buildroot</a> system. These were also
built using the (about to be announced in a couple on minutes) uClibc
0.9.17 release, so if you want to begin compiling and testing stuff with
uClibc, but you don't feel like spending the _hours_ it takes to download,
configure, and build your own uClibc based development system -- then you
may want to download these and give them a try. They each contain a 100 MB
ext2 filesystem with everything you need to begin compiling your own
applications. I have (at least minimally) tested each of them and verified
that the included gcc and g++ compilers produce working uClibc linked
executables.
<p>
Oh, and I have also have updated the uClibc/gcc toolchain builders, so
if you just want a simple uClibc/gcc toolchain,
<a href="/cgi-bin/cvsweb/toolchain/">one of these should work for you.</a>
<p>
<p>
<li> <b>10 January 2003, dev system updates, powerpc image released</b>
<br>
A few problems showed up in yesterday's development system release
(adduser was broken, gdb didn't work, libstdc++ shared libs were missing,
etc). So I've updated the <a href="http://www.uclibc.org/downloads/root_fs_0.9.17-i386.bz2">
i386 development system image</a> to fix these problems.
Also, the <a href="http://www.uclibc.org/downloads/root_fs_0.9.17-powerpc.bz2">
powerpc development system image</a> has finally finished compiling
and is now released upon an unsuspecting world. Have fun!
<p>
<p>
<li> <b>9 January 2003, uClibc development system released</b>
<br>
CodePoet Consulting (i.e. Erik) has been working hard on <a
href="/cgi-bin/cvsweb/buildroot/">buildroot</a> recently, and is pleased to
offer a full stand-alone uClibc-only development system. This is an ext2
filesystem for i386 containing all the development software you need to
build your own uClibc applications. With bash, awk, make, gcc, g++,
autoconf, automake, ncurses, zlib, openssl, openssh, gdb, strace, valgrind,
busybox, GNU coreutils, and more, this should have pretty much everything
you need to get started building your own applications linked against
uClibc. By using a uClibc only system, you can avoid all the painful
cross-configuration problems that have made using uClibc somewhat painful
in the past. A powerpc and an arm version are in progress. Expect them
to be released shortly....
<p>
The <a href="http://www.uclibc.org/downloads/root_fs_0.9.17-i386.bz2">
uClibc development system is an 18MB bzip2 compressed ext2 filesystem</a>,
so be prepared to wait if you are on a slow link. If you wish to have more
space, you can loop mount it and 'cp -a' the contents to their own
partition, or do what I did... <EM>WARNING, the following can be very
dangerous. Please be sure you know what you are doing before trying this.
I am not responsible if you lose all your important data.</EM>I had a spare
hard drive (in my case /dev/hdg but you'll want to adapt this to your own
needs), so I partitioned it with a single ext2 partition filling the drive
(in my case /dev/hdg1). Then I ran:<PRE>
bzcat root_fs_0.9.17-i386.bz2 | dd of=/dev/hdg1
e2fsck -f /dev/hdg1
resize2fs -p /dev/hdg1</PRE>
which overwrote everything on /dev/hdg with the new uClibc devel system,
and then expanded the filesystem with the uClibc devel system till it
filled the whole drive.
<p>
<p> <li> <b>Old News</b>
<br>
<a href="old-news.html">Click here to read older news</a>.
<p>
</ul>
<!-- 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 feature
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> 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 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.uclinux.org/">The uClinux home page</a>
<p>
<li> <a href="http://cvs.uclinux.org/">The uClinux CVS repository</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>
</CENTER>
</BODY>
</HTML>
|
