summaryrefslogtreecommitdiff
path: root/docs/uclibc.org/news.html
blob: 4bc851b155f9cff1aaa601a08a8b57ac039a4bf0 (plain)
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
<!--#include file="header.html" -->


<ul>

    <li> <b>19 December 2003, dev systems updated to uClibc 0.9.24</b>
    <br>

    Current uClibc development systems have been posted for
    <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_i386.bz2">i386</a>,
    <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_powerpc.bz2">powerpc</a>,
    <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_arm.bz2">arm</a>,
    <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mips.bz2">mips</a>,
    <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_mipsel.bz2">mipsel</a>, and
    <a href="http://www.kernel.org/pub/linux/libs/uclibc/root_fs_sh4.bz2">sh4</a>.
    The powerpc dev system mostly works, but there is still some sortof
    problem with the shared library loader that has not yet been resolved.
    Details on what these are and how to use them can be found in the
    <a href="/FAQ.html#dev_systems">FAQ</a>


    <p>
    <li> <b>15 December 2003, uClibc 0.9.24 Released</b>
    <br>

    CodePoet Consulting is pleased to announce the immediate availability of
    uClibc 0.9.24.  This contains various minor updates and fixes for a few
    silly configuration problems.  Arm users should notice a speed increase
    since some arm optimized string functions have been added.  And several
    bugs have been fixed.

    <p>
    
    This release continues to be binary compatible with uClibc 0.9.21 to 0.9.23
    -- as long as you pick compatible configuration options.  The next release
    will <b>not</b> be binary compatible.  We've been saving up a few needed
    changes that will be going into the next release, so while you will not
    need to recompile all your applications and libraries just yet, keep in
    mind we will have a flag day soon...

    <p>

    As usual, the 
    <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, 
    <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, 
    and <a href="http://www.uclibc.org/downloads/uClibc-0.9.24.tar.bz2">source code for this release</a> 
    are available <a href="http://www.uclibc.org/downloads/">here</a>.

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