From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] prosody: needs MMU
Date: Tue, 03 Apr 2018 15:51:30 +0200 [thread overview]
Message-ID: <87sh8cpfdp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <e7d3af9b986c98c2e11b0a60789401b7e49687c6.1522730725.git.baruch@tkos.co.il> (Baruch Siach's message of "Tue, 3 Apr 2018 07:45:25 +0300")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> prosody POSIX support code calls fork() unconditionally.
> prosody also uses the mallinfo() API, but uClibc does not provide that
> for no-MMU targets.
> Fixes:
> http://autobuild.buildroot.net/results/2d0/2d0f97e41cc1d4c9c7a0eacd4eec8bad6f00bcff/
> http://autobuild.buildroot.net/results/f69/f69dfb1a7d1163b402b1f9bef045891c229539e5/
> Cc: Dushara Jayasinghe <nidujay@gmail.com>
> Cc: Francois Perrad <francois.perrad@gadz.org>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-04-03 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 4:45 [Buildroot] [PATCH 1/2] prosody: fix build with musl libc Baruch Siach
2018-04-03 4:45 ` [Buildroot] [PATCH 2/2] prosody: needs MMU Baruch Siach
2018-04-03 13:51 ` Peter Korsgaard [this message]
2018-04-03 13:50 ` [Buildroot] [PATCH 1/2] prosody: fix build with musl libc 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=87sh8cpfdp.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox