All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sangjung <sangjung.woo@samsung.com>
To: buildroot@busybox.net
Subject: [Buildroot] NPTL compile error without MMU (ARM)
Date: Thu, 27 Mar 2014 16:11:29 +0900	[thread overview]
Message-ID: <5333CF21.8040503@samsung.com> (raw)
In-Reply-To: <20140327074058.4059aa56@skate>

Dear Thomas.


On 03/27/2014 03:40 PM, Thomas Petazzoni wrote:
> Thanks for your report. The problem really looks like a uClibc problem,
> so I would suggest you to take the uClibc configuration file in
> output/build/uclibc-<version>/.config, and sent the report to the
> uClibc developers. I am also on the uClibc mailing list, so I will be
> able to add additional Buildroot-specific details if requested by the
> uClibc developers.

Thank you for your quick reply.
I will also report this issue to uClibc mailing list ASAP.

>
> Outside of this, it is interesting to see that you are looking at the
> ARM non-MMU support. Do you have an actual hardware platform? In fact,
> I have been interested by looking into ARM non-MMU support in Buildroot
> for a long time, but I have never found a hardware platform, or
> emulated platform, to test things on. If this is something you can help
> with, I'm pretty sure the ARM non-MMU support would make more
> significant progress.

Our target device is for very small wearable thing.
Because of various issue such as power consumption and cost,
ARM Cortex M (that is MMU-less) series are commonly used.


BRs
Sangjung

  reply	other threads:[~2014-03-27  7:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27  6:33 [Buildroot] NPTL compile error without MMU (ARM) Sangjung
2014-03-27  6:40 ` Thomas Petazzoni
2014-03-27  7:11   ` Sangjung [this message]
2014-03-27  7:21     ` Thomas Petazzoni
2014-03-27 14:48   ` Sangjung Woo

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=5333CF21.8040503@samsung.com \
    --to=sangjung.woo@samsung.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.