Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/7] mongoose: needs mmu
Date: Thu, 10 Oct 2013 07:46:38 -0300	[thread overview]
Message-ID: <5256858E.9050005@zacarias.com.ar> (raw)
In-Reply-To: <5256543B.6090005@mind.be>

On 10/10/2013 04:16 AM, Arnout Vandecappelle wrote:

>> --- a/package/mongoose/Config.in
>> +++ b/package/mongoose/Config.in
>> @@ -1,6 +1,7 @@
>>   config BR2_PACKAGE_MONGOOSE
>>       bool "mongoose"
>>       depends on BR2_TOOLCHAIN_HAS_THREADS
>> +    depends on BR2_USE_MMU # fork()
>>       help
>>         Mongoose is a small and easy to use web server
> 
>  Note that fork() is only needed for CGI, so you could instead build
> with -DNO_CGI. It would be a pity to remove mongoose for NOMMU platforms
> since it is ideally suited for them...

Right, but there's still a catch, it's explicitly linking to libdl which
is a big no-no for FLAT nommu.
You seem to be involved with it upstream, care to cook up a patch to fix
the Makefile and maybe bump it bump a notch while at it? :)
Regards.

  reply	other threads:[~2013-10-10 10:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 20:25 [Buildroot] [PATCH 1/7] udpcast: needs mmu Gustavo Zacarias
2013-10-09 20:25 ` [Buildroot] [PATCH 2/7] civetweb: " Gustavo Zacarias
2013-10-09 20:25 ` [Buildroot] [PATCH 3/7] kismet: " Gustavo Zacarias
2013-10-09 20:25 ` [Buildroot] [PATCH 4/7] lighttpd: " Gustavo Zacarias
2013-10-09 20:25 ` [Buildroot] [PATCH 5/7] mongoose: " Gustavo Zacarias
2013-10-10  7:16   ` Arnout Vandecappelle
2013-10-10 10:46     ` Gustavo Zacarias [this message]
2013-10-09 20:25 ` [Buildroot] [PATCH 6/7] mrouted: " Gustavo Zacarias
2013-10-09 20:25 ` [Buildroot] [PATCH 7/7] ngircd: " Gustavo Zacarias
2013-10-09 20:36 ` [Buildroot] [PATCH 1/7] udpcast: " Peter Korsgaard

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=5256858E.9050005@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox