[uClibc]Re: malloc, munmap, etc...
Miles Bader
miles at gnu.org
Thu Nov 7 22:35:52 UTC 2002
On Thu, Nov 07, 2002 at 10:50:18PM +0100, Uwe Beutin wrote:
> The problem is that with the new top-level uClibc/Makefile I cannot
> simply recompile, I have to cvs the whole uClibc directory because of
> different dependencies.
I think it's better to just use the old tree/Makefile (with the updated
malloc dir), and apply this patch:
Index: Makefile
===================================================================
RCS file: /var/cvs/uClibc/Makefile,v
retrieving revision 1.183
retrieving revision 1.185
diff -u -r1.183 -r1.185
--- Makefile 8 Oct 2002 22:21:28 -0000 1.183
+++ Makefile 18 Oct 2002 23:01:46 -0000 1.185
@@ -164,7 +164,11 @@
@if [ "$(HAS_MMU)" = "true" ] ; then \
echo "#define __UCLIBC_HAS_MMU__ 1" >> include/bits/uClibc_config.h ; \
else \
+ echo "For now we make the assumption that a linux system without an"; \
+ echo "MMU must be uClinux, and must have a broken munmap (both"; \
+ echo "assumptions are a bit dodgy, but can be changed in the future)."; \
echo "#undef __UCLIBC_HAS_MMU__" >> include/bits/uClibc_config.h ; \
+ echo "#define __UCLIBC_UCLINUX_BROKEN_MUNMAP__ 1" >> include/bits/uClibc_config.h ; \
fi
@if [ "$(HAS_FLOATING_POINT)" = "true" ] ; then \
echo "#define __UCLIBC_HAS_FLOATS__ 1" >> include/bits/uClibc_config.h ; \
> So I got the whole tree, did an update but I'm stuck with the new Config
> concept. What did I miss? I cannot simply link the
> ./extras/Configs/Config.m68k into my uClinux dir, can I?! Whoa, why am I
> so stupid? :)
I don't know if the new config system even works on m68k targets, and I think
it would be better to get your problems all solved using the old source tree
(with the above patch, and the new malloc dir).
-Miles
--
P.S. All information contained in the above letter is false,
for reasons of military security.
More information about the uClibc
mailing list