diff options
Diffstat (limited to 'docs/uclibc.org/FAQ.html')
| -rw-r--r-- | docs/uclibc.org/FAQ.html | 28 |
1 files changed, 24 insertions, 4 deletions
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html index c3505a785..631944fd9 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> @@ -260,7 +262,7 @@ How could it be smaller and not suck?</a></h2> <hr /> <p> -<h2><a name="toolchain">Do I really need to build a uClibc toolchain?</h2> +<h2><a name="toolchain">Do I really need to build a uClibc toolchain?</a></h2> <p> Yes, you really do need to build a toolchain to produce uClibc binaries. @@ -281,7 +283,7 @@ How could it be smaller and not suck?</a></h2> <hr /> <p> -<h2><a name="wrapper">What happened to the old toolchain wrapper?</h2> +<h2><a name="wrapper">What happened to the old toolchain wrapper?</a></h2> <p> It is possible in some limited cases to re-use an existing glibc toolchain @@ -364,7 +366,7 @@ How could it be smaller and not suck?</a></h2> <hr /> <p> -<h2><a name="bugs">I think I found a bug in uClibc! What should I do?</h2> +<h2><a name="bugs">I think I found a bug in uClibc! What should I do?</a></h2> <p> If you find a problem with uClibc, please submit a detailed bug report to @@ -385,7 +387,7 @@ How could it be smaller and not suck?</a></h2> <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> + "undefined reference to __fputc_unlocked", who do I blame?!</a></h2> <p> This error crops up when a build system mixes system headers (say glibc) @@ -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?!</a></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> |