From: Jon Ringle <jon@ringle.org>
To: Jon Ringle <jon@ringle.org>
Cc: gdb@sourceware.org
Subject: Re: [SPAM] Re: gdbserver-6.6 threading support
Date: Tue, 06 Mar 2007 18:02:00 -0000 [thread overview]
Message-ID: <45EDAC9B.9070607@ringle.org> (raw)
In-Reply-To: <45EDAA43.1020507@ringle.org>
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
next prev parent reply other threads:[~2007-03-06 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 16:59 Jon Ringle
2007-03-06 17:09 ` Daniel Jacobowitz
2007-03-06 17:23 ` [SPAM] " Jon Ringle
2007-03-06 17:38 ` Daniel Jacobowitz
2007-03-06 17:52 ` Jon Ringle
2007-03-06 18:02 ` Jon Ringle [this message]
2007-03-06 18:17 ` Daniel Jacobowitz
2007-03-07 18:34 ` Nathan Sidwell
2007-03-06 18:26 ` Jon Ringle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45EDAC9B.9070607@ringle.org \
--to=jon@ringle.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox