From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] mtd: integck needs MMU support
Date: Thu, 11 Aug 2016 15:01:46 +0200 [thread overview]
Message-ID: <20160811150146.1813651d@free-electrons.com> (raw)
In-Reply-To: <1470847117-14956-2-git-send-email-rahul.bedarkar@imgtec.com>
Hello,
On Wed, 10 Aug 2016 22:08:37 +0530, Rahul Bedarkar wrote:
> After fixing build issue related to MS_DIRSYNC and MS_RELATIME, we get
> following build error with blackfin external toolchain.
>
> fstest_monitor.c: In function 'main':
> fstest_monitor.c:237: warning: implicit declaration of function 'fork'
> /tmp/ccCzZIuW.o: In function 'main':
> /home/rahul.bedarkar/buildroot/output/build/mtd-1.5.2/tests/fs-tests/utils/fstest_monitor.c:237: undefined reference to '_fork'
> collect2: ld returned 1 exit status
> make[2]: *** [fstest_monitor] Error 1
>
> Since it uses fork(), add dependency on MMU support for integck.
>
> Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
> ---
> package/mtd/Config.in | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-11 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 16:38 [Buildroot] [PATCH 1/2] mtd: fix build failure with blackfin external toolchain Rahul Bedarkar
2016-08-10 16:38 ` [Buildroot] [PATCH 2/2] mtd: integck needs MMU support Rahul Bedarkar
2016-08-10 20:37 ` Thomas Petazzoni
2016-08-11 5:36 ` Rahul Bedarkar
2016-08-11 13:01 ` Thomas Petazzoni [this message]
2016-08-11 13:03 ` [Buildroot] [PATCH 1/2] mtd: fix build failure with blackfin external toolchain Thomas Petazzoni
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=20160811150146.1813651d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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