From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4001 invoked by alias); 6 Mar 2007 18:26:31 -0000 Received: (qmail 3992 invoked by uid 22791); 6 Mar 2007 18:26:30 -0000 X-Spam-Check-By: sourceware.org Received: from sccrmhc11.comcast.net (HELO sccrmhc11.comcast.net) (63.240.77.81) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Mar 2007 18:26:23 +0000 Received: from [172.22.0.103] (c-71-63-50-10.hsd1.va.comcast.net[71.63.50.10]) by comcast.net (sccrmhc11) with ESMTP id <2007030618262001100d7ec3e>; Tue, 6 Mar 2007 18:26:20 +0000 Message-ID: <45EDB24C.1050009@ringle.org> Date: Tue, 06 Mar 2007 18:26:00 -0000 From: Jon Ringle User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Jon Ringle CC: gdb@sourceware.org Subject: Re: [SPAM] Re: gdbserver-6.6 threading support References: <45ED9DDD.3040202@ringle.org> <20070306170854.GA6757@caradoc.them.org> <45EDA355.8060708@ringle.org> <20070306173841.GA8625@caradoc.them.org> <45EDAA43.1020507@ringle.org> <45EDAC9B.9070607@ringle.org> In-Reply-To: <45EDAC9B.9070607@ringle.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00099.txt.bz2 Jon Ringle wrote: > Jon Ringle wrote: >> Daniel Jacobowitz wrote: >>> On Tue, Mar 06, 2007 at 12:22:29PM -0500, Jon Ringle wrote: >>> >>>> 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. >>> >>> >> 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... >> > 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? I do however, have __ARCH_HAS_MMU__ defined. I found the following Changelog entry in uClibc-0.9.28/Changelog.full interesting: --------------------- PatchSet 3180 Date: 2004/01/16 12:43:01 Author: andersen Branch: HEAD Tag: (none) Log: s/UCLIBC_HAS_MMU/ARCH_HAS_MMU/g 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 Jon