3 files changed, 107 insertions, 0 deletions
diff --git a/docs/man/ldconfig.8 b/docs/man/ldconfig.8
new file mode 100644
index 000000000..208d63df1
--- /dev/null
+++ b/docs/man/ldconfig.8
@@ -0,0 +1,73 @@
+.TH LDCONFIG 8 2005-08-15 uClibc "Linux Programmer's Manual"
+.SH NAME
+ldconfig \- updates symlinks and cache for shared libraries
+.SH SYNOPSIS
+.B ldconfig
+[
+.B -DvqnNX
+] [
+.B -f conf
+] [
+.B -C cache
+] [
+.B -r root
+] 
+.B dir ...
+.br
+.B ldconfig -l
+[
+.B -Dv
+] 
+.B lib ...
+.br
+.B ldconfig -p
+.SH DESCRIPTION
+.B ldconfig 
+creates the necessary links and cache to the most recent shared libraries 
+found in the directories specified on the command line, in the file 
+\fI/etc/ld.so.conf\fR, and in the default trusted directories (\fI/lib\fR and 
+\fI/usr/lib\fR).  The cache is used by the run-time linker.
+.B ldconfig
+checks the header and file names of the libraries it encounters when 
+determining which versions should have their links updated.
+
+.B Note:
+Some features may not exist depending on how uClibc was built
+.SH OPTIONS
+.TP
+.B -C cache
+use specified \fIcache\fR instead of default
+.TP
+.B -D
+debug mode, do not update links
+.TP
+.B -f conf
+use specified \fIconf\fR instead of default
+.TP
+.B -l
+library mode, manually link libraries
+.TP
+.B -n
+do not process standard trusted directories
+.TP
+.B -N
+do not update the library cache
+.TP
+.B -p
+print the current library cache
+.TP
+.B -q
+quiet mode, do not print warnings you should actually be reading
+.TP
+.B -r root
+chroot to \fIroot\fR before running
+.TP
+.B -v
+verbose mode, print things as we go, and generally be annoying
+.TP
+.B -X
+do not update the library links
+.SH BUGS
+Probably, make sure you complain when you find them:
+.br
+http://bugs.uclibc.org/
diff --git a/docs/man/ldd.1 b/docs/man/ldd.1
new file mode 100644
index 000000000..0b69f730d
--- /dev/null
+++ b/docs/man/ldd.1
@@ -0,0 +1,17 @@
+.TH LDD 1 2005-08-15 uClibc "Linux Programmer's Manual"
+.SH NAME
+ldd \- Print shared library dependencies
+.SH SYNOPSIS
+.B ldd
+[
+.B OPTIONS
+]
+.B FILE ...
+.SH DESCRIPTION
+Prints shared library dependencies.
+.SH OPTIONS
+None actually, we lied about that part.
+.SH BUGS
+Probably, make sure you complain when you find them:
+.br
+http://bugs.uclibc.org/
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html
index 03dfe4f5b..313fc82b3 100644
--- a/docs/uclibc.org/FAQ.html
+++ b/docs/uclibc.org/FAQ.html
@@ -24,6 +24,8 @@ have additions to this FAQ document, we would love to add them,
 <li><a href="#wrapper">What happened to the old toolchain wrapper?</a>
 <li><a href="#dev_systems">Is a pre-compiled uClibc development system available?</a>
 <li><a href="#bugs">I think I found a bug in uClibc!  What should I do?!</a>
+<li><a href="#miscompile">My package builds fine but link fails with errors like "undefined reference 
+	to __fputc_unlocked", who do I blame?!</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>
@@ -379,6 +381,21 @@ How could it be smaller and not suck?</a></h2>
     strace, ltrace, and or valgrind to create a logfile showing the problem
     behavior.
 
+
+<hr />
+<p>
+<h2><a name="miscompile">My package builds fine but link fails with errors like 
+	"undefined reference to __fputc_unlocked", who do I blame?!</h2>
+<p>
+
+    This error crops up when a build system mixes system headers (say glibc) 
+    with the target headers (say uClibc).  Make sure your build system is not 
+    including extraneous include options (-I) and double check that it is using 
+    the correct compiler.  Many build systems incorrectly force things like 
+    -I/usr/include or -I/usr/local/include or -I${prefix}/include (which usually 
+    just expands to -I/usr/include).
+
+
 <hr />
 <p>
 <h2><a name="job_control">Why do I keep getting "sh: can't access tty; job control