From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12169 invoked by alias); 6 Mar 2007 18:02:29 -0000 Received: (qmail 12151 invoked by uid 22791); 6 Mar 2007 18:02:28 -0000 X-Spam-Check-By: sourceware.org Received: from sccrmhc12.comcast.net (HELO sccrmhc12.comcast.net) (63.240.77.82) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Mar 2007 18:02:16 +0000 Received: from [172.22.0.103] (failure[71.63.50.10]) by comcast.net (sccrmhc12) with ESMTP id <2007030618021301200ais99e>; Tue, 6 Mar 2007 18:02:13 +0000 Message-ID: <45EDAC9B.9070607@ringle.org> Date: Tue, 06 Mar 2007 18:02: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> In-Reply-To: <45EDAA43.1020507@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/msg00097.txt.bz2 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? ringlej@crossdev:~/src/uClibc-0.9.28$ grep -r __UCLIBC_HAS_MMU__ . ringlej@crossdev:~/src/uClibc-0.9.28$ grep -r __UCLIBC__ . ./libc/stdio/vfprintf.c:#if defined(__UCLIBC__) && !defined(__UCLIBC_HAS_FLOATS__) ./libc/stdio/_stdio.c:#ifndef __UCLIBC__ ./libc/stdio/_stdio.c:#endif /* __UCLIBC__ */ ./libc/sysdeps/linux/common/ssp.c:#ifdef __UCLIBC__ ./test/dlopen/test1.c:#ifdef __UCLIBC__ ./test/dlopen/test2.c:#ifdef __UCLIBC__ ./test/dlopen/dltest.c:#ifdef __UCLIBC__ ./extra/locale/tst_nl_langinfo.c:#if !defined(__UCLIBC__) && 0 ./README: #ifdef __UCLIBC__ ./include/features.h:#define __UCLIBC__ 1