FAQ.html 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658
  1. <!--#include file="header.html" -->
  2. <h3>Frequently Asked Questions</h3>
  3. This is a collection of some of the most frequently asked questions
  4. about uClibc. Some of the questions even have answers. If you
  5. have additions to this FAQ document, we would love to add them,
  6. <ol>
  7. <li><a href="#naming">Why is it called uClibc?</a>
  8. <li><a href="#platforms">What platforms does uClibc run on?</a>
  9. <li><a href="#why">Why are you doing this? What's wrong with glibc?</a>
  10. <li><a href="#doesnt_suck">So uClibc is smaller then glibc? Doesn't that mean it
  11. completely sucks? How could it be smaller and not suck?</a>
  12. <li><a href="#why_should_i">Why should I use uClibc?</a>
  13. <li><a href="#licensing">If I use uClibc, do I have to release all my source code to the world for
  14. free? I want to create a closed source commercial application and I want
  15. to protect my intellectual property.</a>
  16. <li><a href="#development">Can I use it on my x86 development system?</a>
  17. <li><a href="#shared"> Does uClibc support shared libraries?</a>
  18. <li><a href="#compiling">How do I compile programs with uClibc?</a>
  19. <li><a href="#toolchain">Do I really need to build a uClibc toolchain?</a>
  20. <li><a href="#wrapper">What happened to the old toolchain wrapper?</a>
  21. <li><a href="#dev_systems">Is a pre-compiled uClibc development system available?</a>
  22. <li><a href="#bugs">I think I found a bug in uClibc! What should I do?!</a>
  23. <li><a href="#job_control">Why do I keep getting "sh: can't access tty; job control
  24. turned off" errors? Why doesn't Control-C work within my shell?</a>
  25. <li><a href="#autoconf">How do I make autoconf and automake behave?</a>
  26. <li><a href="#ldd">When I run 'ldd' to get a list of the library dependencies
  27. for a uClibc binary, ldd segfaults! What should I do?</a>
  28. <li><a href="#timezones">Why does localtime() return times in UTC even when I have my timezone set?</a>
  29. <li><a href="#history">What is the history of uClibc? Where did it come from?</a>
  30. <li><a href="#demanding">I demand that you to add &lt;favorite feature&gt; right now! How come
  31. you don't answer all my questions on the mailing list instantly? I demand
  32. that you help me with all of my problems <em>Right Now</em>!</a>
  33. <li><a href="#helpme">I need help with uClibc! What should I do?</a>
  34. <li><a href="#contracts">I need you to add &lt;favorite feature&gt;! Are the uClibc developers willing to
  35. be paid in order to fix bugs or add in &lt;favorite feature&gt;? Are you willing to provide
  36. support contracts?</a>
  37. <li><a href="#support">I think you guys are great and I want to help support your work!</a>
  38. </ol>
  39. <hr />
  40. <p>
  41. <h2><a name="naming">Why is it called uClibc?</a></h2>
  42. <p>
  43. The letter 'u' is short for µ (the greek letter "mu"). µ is commonly used
  44. as the abbreviation for the word "micro". The capital "C" is short for
  45. "controller". So the name uClibc is sortof an abbreviation for "the
  46. microcontroller C library". For simplicity, uClibc is pronounced
  47. "yew-see-lib-see".
  48. <p>
  49. The name is partly historical, since uClibc was originally
  50. created to support <a href="http://www.uclinux.org">µClinux</a>, a port of
  51. Linux for MMU-less microcontrollers such as the Dragonball, Coldfire, and
  52. ARM7TDMI. These days, uClibc also works just fine on normal Linux systems
  53. (such as i386, ARM, and PowerPC), but we couldn't think of a better name.
  54. <hr />
  55. <p>
  56. <h2><a name="platforms">What platforms does uClibc run on?</a></h2>
  57. <p>
  58. Currently uClibc runs on alpha, ARM, cris, i386, i960, h8300,
  59. m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors.
  60. <hr />
  61. <p>
  62. <h2><a name="why">Why are you doing this? What's wrong with glibc?</a></h2>
  63. <p>
  64. Initially, the project began since the GNU C library lacked support for
  65. MMU-less systems, and because glibc is very large. The GNU C library is
  66. designed with a very different set of goals then uClibc. The GNU C library
  67. is a great piece of software, make no mistake. It is compliant with just
  68. about every standard ever created, and runs on just about every operating
  69. system and architecture -- no small task! But there is a price to be paid
  70. for that. It is quite a large library, and keeps getting larger with each
  71. release. It does not even pretend to target embedded systems. To quote
  72. from Ulrich Drepper, the maintainer of GNU libc: "...glibc is not the right
  73. thing for [an embedded OS]. It is designed as a native library (as opposed
  74. to embedded). Many functions (e.g., printf) contain functionality which is
  75. not wanted in embedded systems." 24 May 1999
  76. <hr />
  77. <p>
  78. <h2><a name="doesnt_suck">So uClibc is smaller then glibc? Doesn't that mean it completely sucks?
  79. How could it be smaller and not suck?</a></h2>
  80. <p>
  81. <p>
  82. uClibc and glibc have different goals. glibc strives for features
  83. and performance, and is targeted for desktops and servers with
  84. (these days) lots of resources. It also strives for ABI stability.
  85. <p>
  86. On the other hand, the goal of uClibc is to provide as much functionality
  87. as possible in a small amount of space, and it is intended primarily for
  88. embedded use. It is also highly configurable in supported features, at the
  89. cost of ABI differences for different configurations. uClibc has been
  90. designed from the ground up to be a C library for embedded Linux. We don't
  91. need to worry about things like MS-DOS support, or BeOS, or AmigaOs any
  92. other system. This lets us cut out a lot of complexity and very carefully
  93. optimize for Linux.
  94. <p>
  95. In other cases, uClibc leaves certain features (such as full C99 Math
  96. library support, wordexp, IPV6, and RPC support) disabled by default.
  97. Those features can be enabled for people that need them, but are otherwise
  98. disabled to save space.
  99. <p>
  100. Some of the space savings in uClibc is obtained at the cost of performance,
  101. and some is due to sacrificing features. Much of it comes from aggressive
  102. refactoring of code to eliminate redundancy. In regards to locale data,
  103. elimination of redundant data storage resulted in substantial space
  104. savings. The result is a libc that currently includes the features needed
  105. by nearly all applications and yet is considerably smaller than glibc. To
  106. compare "apples to apples", if you take uClibc and compile in locale data
  107. for about 170 UTF-8 locales, then uClibc will take up about 570k. If you
  108. take glibc and add in locale data for the same 170 UTF-8 locales, you will
  109. need over 30MB!!!
  110. <p>
  111. The end result is a C library that will compile just about everything you
  112. throw at it, that looks like glibc to application programs when you
  113. compile, and is many times smaller.
  114. <hr />
  115. <p>
  116. <h2><a name="why_should_i">Why should I use uClibc?</a></h2>
  117. <p>
  118. I don't know if you should use uClibc or not. It depends on your needs.
  119. If you are building an embedded Linux system and you are tight on space, then
  120. using uClibc instead if glibc may be a very good idea.
  121. <p>
  122. If you are building an embedded Linux system and you find that
  123. glibc is eating up too much space, you should consider using
  124. uClibc. If you are building a huge fileserver with 12 Terabytes
  125. of storage, then using glibc may make more sense. Unless, for
  126. example, that 12 Terabytes will be Network Attached Storage and
  127. you plan to burn Linux into the system's firmware...
  128. <hr />
  129. <p>
  130. <h2><a name="licensing">If I use uClibc, do I have to release all my source code to the world for
  131. free? I want to create a closed source commercial application and I want
  132. to protect my intellectual property.</a></h2>
  133. <p>
  134. No, you do not need to give away your application source code just because
  135. you use uClibc and/or run on Linux. uClibc is licensed under the <a
  136. href="http://www.gnu.org/copyleft/lesser.html">Lesser GPL</a> licence, just
  137. like the GNU C library (glibc). Please read this licence, or have a lawyer
  138. read this licence if you have any questions. Here is my brief summary...
  139. Using shared libraries makes complying with the license easy. You can
  140. distribute a closed source application which is linked with an unmodified
  141. uClibc shared library. In this case, you do not need to give away any
  142. source code for your application. Please consider sharing some of the
  143. money you make with us! :-)
  144. <p>
  145. If you make any changes to uClibc, and distribute uClibc or distribute any
  146. applications using your modified version, you must also distribute the
  147. source code for uClibc containing all of your changes.
  148. <p>
  149. If you distribute an application which has uClibc statically linked, you
  150. must also make your application available as an object file which can later
  151. be re-linked against updated versions of uClibc. This will (in theory)
  152. allow your customers to apply uClibc bug fixes to your application. You do
  153. not need to make the application object file available to everyone, just to
  154. those you gave the fully linked application.
  155. <hr />
  156. <p>
  157. <h2><a name="development">Can I use it on my x86 development system?</a></h2>
  158. <p>
  159. Sure! In fact, this can be very nice during development. By
  160. installing uClibc on your development system, you can be sure that
  161. the code you are working on will actually run when you deploy it on
  162. your target system.
  163. <hr />
  164. <p>
  165. <h2><a name="shared"> Does uClibc support shared libraries?</a></h2>
  166. <p>
  167. Yes. uClibc has native shared library support on i386, ARM, mips,
  168. SH, CRIS, and PowerPC processors. Other architectures can use shared
  169. libraries but will need to use the GNU libc shared library loader.
  170. <p>
  171. Shared Libraries are not currently supported by uClibc on MMU-less systems.
  172. <a href="http://www.snapgear.com/">SnapGear</a> has implemented
  173. shared library support for MMU-less systems, however, so if you need MMU-less
  174. shared library support they may be able to help.
  175. <hr />
  176. <p>
  177. <h2><a name="compiling">How do I compile programs with uClibc?</a></h2>
  178. <p>
  179. You will need to have your own uClibc toolchain. A toolchain consists
  180. of <a href="http://sources.redhat.com/binutils/">GNU binutils</a>,
  181. <a href="http://gcc.gnu.org/">the gcc compiler</a>, and uClibc, all
  182. built to produce binaries for your target system linked with uClibc.
  183. You can build your own native uClibc toolchain using the
  184. <a href="http://buildroot.uclibc.org/">uClibc buildroot system</a>.
  185. <p>
  186. To build your own uClibc toolchain, follow the following simple
  187. steps:
  188. <ul>
  189. <li> Point your web browser <a href="http://buildroot.uclibc.org/">here</a>,
  190. <li> Download of copy of buildroot
  191. <li> Unpack the tarball on your Linux system somewhere
  192. <li> Edit the Makefile as needed if you wish to change anything.
  193. <li> run 'unset CC'. Then run 'unset CXX'. Some Linux systems
  194. (i.e. Gentoo) set variables such as 'CC' in the system environment
  195. which really messes things up when cross compiling.
  196. <li> run 'make menuconfig'
  197. <li> Select the things you want to build. If you <em>only</em> want a
  198. toolchain, leave everything except the toolchain disabled.
  199. <li> save your buildroot configuration.
  200. <li> run 'make'
  201. <li> go eat a nice wholesome sandwich, drink a pop, call a friend,
  202. play a video game, and generally find something to do. While you
  203. are waiting, buildroot will download all the needed source code and
  204. then compile things up for you.
  205. <li> You should now have a shiny new toolchain, and maybe even a shiny
  206. new uClibc based root filesystem or development system, depending on
  207. the options you selected.
  208. </ul>
  209. <hr />
  210. <p>
  211. <h2><a name="toolchain">Do I really need to build a uClibc toolchain?</h2>
  212. <p>
  213. Yes, you really do need to build a toolchain to produce uClibc binaries.
  214. We used to provide a toolchain wrapper, but that has been removed due to
  215. numerous problems. The uClibc developers have gone to a lot of trouble
  216. to produce the
  217. <a href="http://buildroot.uclibc.org/">uClibc buildroot system</a>,
  218. which makes it easy to build your own uClibc toolchain and/or an initial
  219. uClibc based system.
  220. <p>
  221. Feel free to take the gcc and binutils patches we provide and use them in
  222. your own toolchain build system. If you choose to use your own toolchain
  223. build system, you will need to use these patches since the upstream GNU
  224. binutils and gcc releases do not currently have full support for building a
  225. uClibc toolchain.
  226. <hr />
  227. <p>
  228. <h2><a name="wrapper">What happened to the old toolchain wrapper?</h2>
  229. <p>
  230. It is possible in some limited cases to re-use an existing glibc toolchain
  231. and subvert it into building uClibc binaries by using gcc commands such as
  232. "-nostdlib" and "-nostdinc". In fact, this used to be the recommended
  233. method for compiling programs with uClibc, and we made this easy to do by
  234. providing a uClibc toolchain wrapper, which attempted to automagically subvert
  235. an existing glibc toolchain.
  236. <p>
  237. This toolchain wrapper was removed from uClibc 0.9.22, and it will not be
  238. coming back. This is because it proved impossible to completely subvert an
  239. existing toolchain in many cases, and therefore proved to be a real
  240. maintainence burder. As uClibc became more capable, the many problems with
  241. re-using an existing glibc toolchain led us to conclude that the only safe
  242. and sane way to build uClibc binaries was to use a uClibc toolchain.
  243. <p>
  244. Some discussion on the reasoning behind this decision can be found here:
  245. <a href="http://www.uclibc.org/lists/uclibc/2003-October/007315.html">
  246. http://www.uclibc.org/lists/uclibc/2003-October/007315.html</a>
  247. in the uClibc mailing list archives.
  248. <hr />
  249. <p>
  250. <h2><a name="dev_systems">Is a pre-compiled uClibc development system available?</a></h2>
  251. <p>
  252. If you want to be <em>really</em> lazy and start using uClibc right away
  253. without needing to compile your own toolchain or anything, you can grab a
  254. pre-compiled uClibc development system. These are currently available for
  255. <a href="http://www.uclibc.org/downloads/root_fs_arm.ext2.bz2">arm</a>,
  256. <a href="http://www.uclibc.org/downloads/root_fs_armeb.ext2.bz2">armeb</a>,
  257. <a href="http://www.uclibc.org/downloads/root_fs_i386.ext2.bz2">i386</a>,
  258. <a href="http://www.uclibc.org/downloads/root_fs_mips.ext2.bz2">mips</a>,
  259. <a href="http://www.uclibc.org/downloads/root_fs_mipsel.ext2.bz2">mipsel</a>,
  260. <a href="http://www.uclibc.org/downloads/root_fs_powerpc.ext2.bz2">powerpc</a>, and
  261. <a href="http://www.uclibc.org/downloads/root_fs_sh4.ext2.bz2">sh4</a>.
  262. <p>
  263. These are bzip2 compressed ext2 filesystems containing all the development
  264. software you need to build your own uClibc applications, including: bash, awk,
  265. make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh, gdb,
  266. strace, busybox, GNU coreutils, GNU tar, GNU grep, etc.
  267. <p>
  268. Each of these uClibc development systems was created using
  269. <a href="http://buildroot.uclibc.org/">buildroot</a>, specifically,
  270. <a href="http://www.uclibc.org/downloads/buildroot.tar.bz2">buildroot.tar.bz2</a>
  271. along with <a href="http://www.uclibc.org/downloads/buildroot-sources">these sources</a>.
  272. <p>
  273. These development systems should provide pretty much everything you need to get
  274. started building your own applications with uClibc. Once you download one of
  275. these systems, you can then boot into it, loop mount it, dd it to a spare drive
  276. and use a tool such as resize2fs to make it fill a partition... Whatever works
  277. best for you.
  278. <p>
  279. The quickest way to get started using a root_fs image (using the i386
  280. platform as an example) is:
  281. <ul>
  282. <li>Download root_fs_i386.bz2 from uclibc.org</li>
  283. <li>bunzip2 root_fs_i386.bz2</li>
  284. <li>mkdir root_fs</li>
  285. <li>su root</li>
  286. <li>mount -o loop root_fs_i386 root_fs</li>
  287. <li>chroot root_fs /bin/su -</li>
  288. </ul>
  289. Type "exit" to end the chroot session and return to the host system.
  290. <p>
  291. <hr />
  292. <p>
  293. <h2><a name="bugs">I think I found a bug in uClibc! What should I do?</h2>
  294. <p>
  295. If you find a problem with uClibc, please submit a detailed bug report to
  296. the uClibc mailing list at <a href="mailto:uclibc@mail.uclibc.org">
  297. uclibc@mail.uclibc.org</a>. Please do not send private email to Erik
  298. (the maintainer of uClibc) asking for private help unless you are planning
  299. on paying for consulting services. When we answer questions on the uClibc
  300. mailing list, it helps everyone, while private answers help only you...
  301. A well-written bug report should include an example that demonstrates the
  302. problem behaviors and enables anyone else to duplicate the bug on their own
  303. machine. For larger applications where it may prove difficult to provide
  304. an example application, we recommend that you use a tool such as gdb,
  305. strace, ltrace, and or valgrind to create a logfile showing the problem
  306. behavior.
  307. <hr />
  308. <p>
  309. <h2><a name="job_control">Why do I keep getting "sh: can't access tty; job control
  310. turned off" errors? Why doesn't Control-C work within my shell?</a></h2>
  311. <p>
  312. This isn't really a uClibc question, but I'll answer it here anyways. Job
  313. control will be turned off since your shell can not obtain a controlling
  314. terminal. This typically happens when you run your shell on /dev/console.
  315. The kernel will not provide a controlling terminal on the /dev/console
  316. device. Your should run your shell on a normal tty such as tty1 or ttyS0
  317. and everything will work perfectly. If you <em>REALLY</em> want your shell
  318. to run on /dev/console, then you can hack your kernel (if you are into that
  319. sortof thing) by changing drivers/char/tty_io.c to change the lines where
  320. it sets "noctty = 1;" to instead set it to "0". I recommend you instead
  321. run your shell on a real console...
  322. <hr />
  323. <p>
  324. <h2><a name="autoconf">How do I make autoconf and automake behave?</a></h2>
  325. <p>
  326. When you are cross-compiling, autoconf and automake are known to behave
  327. badly. This is because a large number of configure scripts (such as the
  328. one from openssh) try to actually execute applications that were cross
  329. compiled for your target system. This is bad, since of course these won't
  330. run, and this will also prevent your programs from compiling. You need to
  331. complain to the authors of these programs and ask them to fix their broken
  332. configure scripts.
  333. <hr />
  334. <p>
  335. <h2><a name="ldd">When I run 'ldd' to get a list of the library dependencies
  336. for a uClibc binary, ldd segfaults! What should I do?</a></h2>
  337. <p>
  338. Use the ldd that is built by uClibc, not your system's one. You can build
  339. uClibc'd ldd for your host system by going into the uClibc/utils/ directory
  340. in the uClibc source and running 'make ldd.host'.
  341. <p>
  342. When your system's ldd looks for library dependencies, it actually _runs_
  343. that program. This works fine -- usually. It generally will not work at
  344. all when you have been cross compiling (which is why ldd segfaults). The
  345. ldd program created by uClibc is cross platform and doesn't mind at all if
  346. it cannot execute the target program. If you use the uClibc version of
  347. 'ldd', it will do the right thing and produce correct results, even when it
  348. is used on cross compiled binaries.
  349. <hr />
  350. <p>
  351. <h2><a name="timezones">Why does localtime() return times in UTC even when I have my timezone set?</a></h2>
  352. <p>
  353. The uClibc time functions get timezone information from the TZ environment
  354. variable, as described in the Single Unix Specification Version 3. See
  355. <a href="http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html">
  356. http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html</a>
  357. for details on valid settings of TZ. For some additional examples, read
  358. <a href="http://www.uclibc.org/lists/uclibc/2002-August/006261.html">
  359. http://www.uclibc.org/lists/uclibc/2002-August/004010.html</a> in the uClibc
  360. mailing list archive.
  361. You can store the value of TZ in the file '/etc/TZ' and uClibc will then
  362. automagically use the specified setting.
  363. <hr />
  364. <p>
  365. <h2><a name="history">What is the history of uClibc? Where did it come from?</a></h2>
  366. <p>
  367. uClibc started off as a fork on the <a
  368. href="http://www.cix.co.uk/~mayday/">Linux-8086 C library</a>, which is
  369. part of the <a href="http://www.elks.ecs.soton.ac.uk/">elks project</a>.
  370. The Linux-8086 C library was, apparently, largely written from scratch but
  371. also borrowed code from libc4, glibc, some Atari library code, with bits
  372. and pieces from about 20 other places.
  373. <p>
  374. I had for some time been despairing over the state of C libraries in Linux.
  375. GNU libc, the standard, is very poorly suited to embedded systems and has
  376. been getting bigger with every release. I spent quite a bit of time
  377. looking over the available Open Source C libraries that I knew of, and none
  378. of them really impressed me. I felt there was a real vacancy in the
  379. embedded Linux ecology. The closest library to what I imagined an embedded
  380. C library should be was uClibc. But it had a lot of problems too -- not
  381. the least of which was that, traditionally, uClibc required a complete
  382. source tree fork in order to support each and every new platform. This
  383. resulted in a big mess of twisty versions, all different. I decided to fix
  384. it and the result is what you see here.
  385. <p>
  386. To start with, (with some initial help from <a
  387. href="http://www.uclinux.org/developers/">D. Jeff Dionne</a>), I ported
  388. uClibc to run on i386. I then grafted in the header files from glibc and
  389. cleaned up the resulting breakage. This (plus some additional work) has
  390. made it much less dependant on kernel headers, a large departure from its
  391. traditional tightly-coupled-to-the-kernel origins. I have written and/or
  392. rewritten a number of things that were missing or broken, and sometimes
  393. grafted in bits of code from the current glibc and libc5. I have also
  394. added a proper configuration system which allows you to easily select your
  395. target architecture and enable and disable various features. Many people
  396. have helped by testing, contributing ports to new architectures, and adding
  397. support for missing features.
  398. <p>
  399. In particular, around the end of 2000, Manuel Novoa III got involved with
  400. uClibc. One of his first contributions was the original gcc wrapper (which
  401. has since been removed). Since then, he has written virtually all of the
  402. current uClibc stdio, time, string, ctype, locale, and wchar-related code,
  403. as well as much of stdlib and various other bits throught the library.
  404. <p>
  405. These days, uClibc is being developed and enhanced by Erik Andersen
  406. and Manuel Novoa III of
  407. <a href="http://codepoet-consulting.com/">CodePoet Consulting</a>
  408. along with the rest of the embedded Linux community.
  409. <hr />
  410. <p>
  411. <h2><a name="demanding">I demand that you to add &lt;favorite feature&gt; right now! How come
  412. you don't answer all my questions on the mailing list instantly? I demand
  413. that you help me with all of my problems <em>Right Now</em>!</a></h2>
  414. <p>
  415. You have not paid us a single cent and yet you still have the
  416. product of several years of work from Erik and Manuel and
  417. many other people. We are not your slaves! We work on uClibc
  418. because we find it interesting. If you go off flaming us, we will
  419. ignore you.
  420. <hr />
  421. <p>
  422. <h2><a name="helpme">I need help with uClibc! What should I do?</a></h2>
  423. <p>
  424. If you find that you need help with uClibc, you can ask for help on the
  425. uClibc mailing list at uclibc@mail.uclibc.org. In addition to the uClibc
  426. mailing list, Erik and Manuel are also known to sometimes hang out on the
  427. uClibc IRC channel: #uclibc on irc.freenode.net.
  428. <p>
  429. <b>Please do not send private email to Erik and/or Manuel asking for
  430. private help unless you are planning on paying for consulting services.</b>
  431. When we answer questions on the uClibc mailing list, it helps everyone
  432. since people with similar problems in the future will be able to get help
  433. by searching the mailing list archives. Private help is reserved as a paid
  434. service. If you need to use private communication, or if you are serious
  435. about getting timely assistance with uClibc, you should seriously consider
  436. paying for consulting time.
  437. <p>
  438. <hr />
  439. <p>
  440. <h2><a name="contracts">I need you to add &lt;favorite feature&gt;! Are the uClibc developers willing to
  441. be paid in order to fix bugs or add in &lt;favorite feature&gt;? Are you willing to provide
  442. support contracts?</a></h2>
  443. <p>
  444. Sure! Now you have our attention! What you should do is contact <a
  445. href="mailto:andersen@codepoet.org">Erik Andersen</a> of <a
  446. href="http://codepoet-consulting.com/">CodePoet Consulting</a> to bid
  447. on your project. If Erik is too busy to personally add your feature, there
  448. are several other active uClibc contributors who will almost certainly be able
  449. to help you out. Erik can contact them and ask them about their availability.
  450. <hr />
  451. <p>
  452. <h2><a name="support">I think you guys are great and I want to help support your work!</a></h2>
  453. <p>
  454. Wow, that would be great! You can click here to help support uClibc and/or request features.
  455. <!-- Begin PayPal Logo -->
  456. <center>
  457. <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
  458. <input type="hidden" name="cmd" value="_xclick">
  459. <input type="hidden" name="business" value="andersen@codepoet.org">
  460. <input type="hidden" name="item_name" value="Support uClibc and/or request features">
  461. <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png">
  462. <input type="hidden" name="no_shipping" value="1">
  463. <input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal">
  464. </form>
  465. </center>
  466. <!-- End PayPal Logo -->
  467. If you prefer to contact us directly for payments, hardware donations,
  468. support requests, etc., you can contact
  469. <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> here.
  470. <hr />
  471. <br>
  472. <br>
  473. <br>
  474. <br>
  475. <br>
  476. <br>
  477. <br>
  478. <br>
  479. <br>
  480. <br>
  481. <br>
  482. <br>
  483. <br>
  484. <br>
  485. <br>
  486. <br>
  487. <br>
  488. <br>
  489. <br>
  490. <br>
  491. <br>
  492. <br>
  493. <br>
  494. <br>
  495. <br>
  496. <br>
  497. <br>
  498. <br>
  499. <br>
  500. <br>
  501. <br>
  502. <br>
  503. <br>
  504. <br>
  505. <br>
  506. <br>
  507. <br>
  508. <br>
  509. <br>
  510. <br>
  511. <br>
  512. <br>
  513. <br>
  514. <br>
  515. <br>
  516. <br>
  517. <br>
  518. <br>
  519. <br>
  520. <br>
  521. <br>
  522. <br>
  523. <br>
  524. <br>
  525. <br>
  526. <br>
  527. <br>
  528. <br>
  529. <br>
  530. <br>
  531. <br>
  532. <br>
  533. <br>
  534. <br>
  535. <!--#include file="footer.html" -->