[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    question about config of Ash shell..
From:       Brad Walker <bwalker () musings ! com>
Date:       2014-04-14 22:58:39
Message-ID: CAPKZHbXGh3RHEPChrJV_TJGDsAVOex=vuMgmPcqVqRFG58CQsQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I am working on an embedded system that does not have a MMU. It's a Kinetis
K61 based system running ucLinux. The system works quite well..

I noticed the following in ash.c

#if !BB_MMU
# error "Do not even bother, ash will not run on NOMMU machine"
#endif

and

//config:	depends on !NOMMU

I have compiled the Ash shell and executed on the system. It runs really
well.

So my question is why does BusyBox continue to have these set? I would be
happy to make the changes, test them out, and then submit a pull request if
that is helpful.

Thanks.

-brad w.

[Attachment #5 (text/html)]

<div dir="ltr"><div><div><br></div>I am working on an embedded system that does not \
have a MMU. It&#39;s a Kinetis K61 based system running ucLinux. The system works \
quite well..<br><br></div><div>I noticed the following in ash.c<br> \
<br><pre><code>#if !BB_MMU # error &quot;Do not even bother, ash will not run on \
NOMMU machine&quot; #endif<br></code></pre><pre><code>and<br><br></code><code>//config:	depends \
on !NOMMU<br><br></code></pre><pre><code></code></pre>I have compiled the Ash shell \
and executed on the system. It runs really well.<br><br></div> <div>So my question is \
why does BusyBox continue to have these set? I would be happy to make the changes, \
test them out, and then submit a pull request if that is \
helpful.<br><br></div><div>Thanks.<br><br>-brad w.<br></div> \
<div><div><br><br><br><br><br><br><br></div></div></div>



_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

[prev in list] [next in list] [prev in thread] [next in thread]