From bd06e565ca8c0032355facfe155b49a4bfe244d2 Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Sat, 29 Oct 2005 07:50:20 +0000 Subject: close tags like they should be for valid html --- docs/uclibc.org/FAQ.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html index d129089e7..631944fd9 100644 --- a/docs/uclibc.org/FAQ.html +++ b/docs/uclibc.org/FAQ.html @@ -262,7 +262,7 @@ How could it be smaller and not suck?

-

Do I really need to build a uClibc toolchain?

+

Do I really need to build a uClibc toolchain?

Yes, you really do need to build a toolchain to produce uClibc binaries. @@ -283,7 +283,7 @@ How could it be smaller and not suck?


-

What happened to the old toolchain wrapper?

+

What happened to the old toolchain wrapper?

It is possible in some limited cases to re-use an existing glibc toolchain @@ -366,7 +366,7 @@ How could it be smaller and not suck?


-

I think I found a bug in uClibc! What should I do?

+

I think I found a bug in uClibc! What should I do?

If you find a problem with uClibc, please submit a detailed bug report to @@ -387,7 +387,7 @@ How could it be smaller and not suck?


My package builds fine but link fails with errors like - "undefined reference to __fputc_unlocked", who do I blame?!

+ "undefined reference to __fputc_unlocked", who do I blame?!

This error crops up when a build system mixes system headers (say glibc) @@ -401,7 +401,7 @@ How could it be smaller and not suck?


My package builds fine but link fails with errors like "undefined reference - to rpl_realloc / rpl_malloc", who do I blame?!

+ to rpl_realloc / rpl_malloc", who do I blame?!

This error crops up because you didn't enable MALLOC_GLIBC_COMPAT support. -- cgit v1.2.3