This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Jon Ringle wrote:I do however, have __ARCH_HAS_MMU__ defined.Daniel Jacobowitz wrote:I just checked my uClibc-0.9.28 source tree and I can't find any reference to __UCLIBC_HAS_MMU__. So, __UCLIBC_HAS_MMU__ will not be defined for anyone that uses uClibc-0.9.28. Where does __UCLIBC_HAS_MMU__ come from?On Tue, Mar 06, 2007 at 12:22:29PM -0500, Jon Ringle wrote:The target is Linux-2.6.16.29. Processor is IXP455 (it has an MMU). The rootfs was built with buildroot using uClibc-0.9.28. Perhaps, I've got something misconfigured in buildroot or uClibc then...
Sending packet: $qOffsets#4b...Ack
Packet received: E01
warning: Remote failure reply: E01
#if defined(__UCLIBC__) && !defined(__UCLIBC_HAS_MMU__)
Is this really Linux, or uClinux? It seems to be configured as if it were uClinux, but it looks like Linux.
Members: extra/Configs/Config.alpha:1.17->1.18 extra/Configs/Config.cris:1.11->1.12 extra/Configs/Config.in.arch:1.13->1.14 extra/Configs/Config.powerpc:1.34->1.35 extra/Configs/Config.sh:1.48->1.49 libc/inet/rpc/rcmd.c:1.9->1.10 libc/sysdeps/linux/common/bits/posix_opt.h:1.2->1.3 libc/unistd/daemon.c:1.7->1.8 libpthread/linuxthreads/manager.c:1.7->1.8
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |