summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2003-02-12 13:10:00 +0000
committerEric Andersen <andersen@codepoet.org>2003-02-12 13:10:00 +0000
commit314ed0a58bff27fb2753395d2e42174f12fc1f55 (patch)
tree9ac85e7102c379dd51d7ad6ec7e38228804922ef /docs
parent8f9a9c49991b10b589c4d75f8531ee89332afcb1 (diff)
Some minor doc updates
Diffstat (limited to 'docs')
-rw-r--r--docs/Glibc_vs_uClibc_Differences.txt18
-rw-r--r--docs/uclibc.org/FAQ.html59
2 files changed, 22 insertions, 55 deletions
diff --git a/docs/Glibc_vs_uClibc_Differences.txt b/docs/Glibc_vs_uClibc_Differences.txt
index e8d5dfa89..89edd6e4f 100644
--- a/docs/Glibc_vs_uClibc_Differences.txt
+++ b/docs/Glibc_vs_uClibc_Differences.txt
@@ -36,15 +36,15 @@ provided by glibc's libresolv is provided internal to uClibc. Other functions
are not at all implemented.
8) libnsl provides support for Network Information Service (NIS) which was
-originally called "Yellow Pages" or "YP", which is an extension of RPC
-invented by Sun to share Unix password files over the network. I personally
-think NIS is an evil abomination, and should be avoided. These days, using
-ldap is much more effective mechanism for doing the same thing. uClibc does
-not provide libnsl.so.1, and has no support for Network Information Service
-(NIS). We therefore, also do not provide any of the headers files provided by
-glibc under /usr/include/rpcsvc. I am open to implementing ldap based
-password authentication, but I do not personally intend to implement it (since
-I have no use for it).
+originally called "Yellow Pages" or "YP", which is an extension of RPC invented
+by Sun to share Unix password files over the network. I personally think NIS
+is an evil abomination, and should be avoided. These days, using ldap is much
+more effective mechanism for doing the same thing. uClibc provides a stub
+libnsl, but and has no actuall support for Network Information Service (NIS).
+We therefore, also do not provide any of the headers files provided by glibc
+under /usr/include/rpcsvc. I am open to implementing ldap based password
+authentication, but I do not personally intend to implement it (since I have no
+use for it).
9) uClibc's locale support is not 100% complete yet. We are working on it.
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html
index 39861a018..11a3cef33 100644
--- a/docs/uclibc.org/FAQ.html
+++ b/docs/uclibc.org/FAQ.html
@@ -236,7 +236,7 @@ to the uClibc home page.</a>
builder from <a href="http://www.uclibc.org/downloads/toolchain/">
http://www.uclibc.org/downloads/toolchain/</a>, or the uClibc buildroot
system from <a href="http://www.uclibc.org/downloads/buildroot/">
- http://www.uclibc.org/downloads/buildroot/</a>, ajust the Makefile
+ http://www.uclibc.org/downloads/buildroot/</a>, adjust the Makefile
settings to match your target system, and then run 'make'.
<p>
@@ -263,47 +263,6 @@ to the uClibc home page.</a>
<p>
<TR><TD BGCOLOR="#ccccc0" ALIGN=left>
<B>
- I have code that uses constructors and destructors. Why is it
- when I use uClibc, the ctors/dtors do not run?
- </B>
-</TD></TR>
-<TR><TD BGCOLOR="#eeeee0">
-
- The uClibc compiler wrapper toolchain by default, does not
- enable constructor and destructor support for C code. It
- only enables ctors/dtors support by default for C++ code.
- If you have C code that uses ctors/dtors and you wish to use
- the uClibc compiler wrapper toolchain, you will need to add
- the <b>--uclibc-ctors</b> option to the gcc command line. i.e.
-
-<PRE>
- $ cat test.c
- #include <unistd.h>
-
- void __attribute__((constructor)) my_ctor(void)
- {
- char msg[]="I am a constructor!\n";
- write(2, msg, sizeof(msg));
- }
-
- int main(void)
- {
- _exit(42);
- }
-
- $ /usr/i386-linux-uclibc/bin/i386-uclibc-gcc --uclibc-ctors ./test.c -o test
- $ ./test
- I am a constructor!
-</PRE>
-
- Another option is to build a native uClibc toolchain. Native toolchains
- always enable ctors/dtors support, even for C code.
-
-
-
-<p>
-<TR><TD BGCOLOR="#ccccc0" ALIGN=left>
- <B>
How do I make autoconf and automake behave?
</B>
</TD></TR>
@@ -312,7 +271,13 @@ to the uClibc home page.</a>
First run
<pre>export PATH=/usr/i386-linux-uclibc/bin:$PATH</pre>
(or similar adjusted for your target architecture) then run you can simply
- run autoconf/automake and it should _just work_.
+ run autoconf/automake and it should _just work_. Unfortunately, a large
+ number of configure scripts (such as the one from openssh) try to execute
+ test applications using your target C library, even if you are cross-
+ compiling. This is bad, since it will prevent these programs from compiling.
+ You need to complain to the authors of these programs and ask them to fix
+ their broken configure scripts.
+
@@ -352,6 +317,8 @@ to the uClibc home page.</a>
<a href="http://www.uclibc.org/lists/uclibc/2002-August/006261.html">
http://www.uclibc.org/lists/uclibc/2002-August/006261.html</a> in the uClibc
mailing list archive.
+ You can store the value of TZ in the file '/etc/TZ' and uClibc will then
+ automagically use the specified setting.
<p>
@@ -470,9 +437,9 @@ to the uClibc home page.</a>
</center>
<!-- End PayPal Logo -->
- If you prefer to contact us directly for payments (Erik has a credit card machine so
- you can avoid making payments online), hardware donations, support requests, etc., you can
- contact <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> here.
+ If you prefer to contact us directly for payments, hardware donations,
+ support requests, etc., you can contact
+ <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> here.
<p>
<TR><TD BGCOLOR="#ccccc0" ALIGN=left>