summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2005-10-29 06:34:54 +0000
committerMike Frysinger <vapier@gentoo.org>2005-10-29 06:34:54 +0000
commit3b50ad308fc09092440466535502c3167835b36e (patch)
tree372479653ee5b38e6706255867b5e466577b6ada
parent01c9aec794f83a774ce2268236273ed4e6b9ad5d (diff)
add an entry about gnu malloc compat option
-rw-r--r--docs/uclibc.org/FAQ.html20
1 files changed, 20 insertions, 0 deletions
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html
index c3505a785..d129089e7 100644
--- a/docs/uclibc.org/FAQ.html
+++ b/docs/uclibc.org/FAQ.html
@@ -26,6 +26,8 @@ have additions to this FAQ document, we would love to add them,
<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="#gnu_malloc">My package builds fine but link fails with errors like "undefined reference
+ to rpl_realloc / rpl_malloc", 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>
@@ -398,6 +400,24 @@ How could it be smaller and not suck?</a></h2>
<hr />
<p>
+<h2><a name="gnu_malloc">My package builds fine but link fails with errors like "undefined reference
+ to rpl_realloc / rpl_malloc", who do I blame?!</h2>
+<p>
+
+ This error crops up because you didn't enable MALLOC_GLIBC_COMPAT support.
+ Configure scripts detect whether your libc supports "GNU malloc" features by
+ seeing whether malloc(0) returns NULL (glibc malloc(0) will return a non NULL
+ pointer). uClibc defaults to malloc(0) returning NULL so autoconf will assume
+ malloc from your libc sucks and procede to try and compile the malloc replacement
+ version in the gnulib addon. However, since not many packages include gnulib,
+ they will fail to link with rpl_realloc / rpl_malloc errors. You could force
+ configure to assume working behavior by exporting the variables 'jm_cv_func_working_malloc'
+ (older autoconf) and 'ac_cv_func_malloc_0_nonnull' (newer autoconf) to 'yes'
+ before running `./configure`.
+
+
+<hr />
+<p>
<h2><a name="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></h2>
<p>