From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] mtools: Does not compile on bfin
Date: Sun, 30 Mar 2014 12:25:05 +0300 [thread overview]
Message-ID: <20140330092505.GE4579@tarshish> (raw)
In-Reply-To: <1396171235-18112-1-git-send-email-bernd.kuhls@t-online.de>
Hi Bernd,
On Sun, Mar 30, 2014 at 11:20:35AM +0200, Bernd Kuhls wrote:
> Fixes http://autobuild.buildroot.net/results/c0f/c0ff79569690b5799c25c09bde581cee6acb9910/
>
> expand.o: In function `_safePopenOut':
> expand.c:(.text+0x1e): undefined reference to `_fork'
> precmd.o: In function `_precmd':
> precmd.c:(.text+0x16): undefined reference to `_fork'
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/mtools/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/mtools/Config.in b/package/mtools/Config.in
> index 5865223..1c83b9e 100644
> --- a/package/mtools/Config.in
> +++ b/package/mtools/Config.in
> @@ -1,6 +1,7 @@
> config BR2_PACKAGE_MTOOLS
> bool "mtools"
> depends on BR2_USE_WCHAR
> + depends on !BR2_bfin # fork()
> depends on BR2_USE_MMU # fork()
Blackfin and a non-MMU architecture, so this dependency is redundant. The
build failure at
http://autobuild.buildroot.net/results/c0f/c0ff79569690b5799c25c09bde581cee6acb9910/
predates commit 56e404bb883b0 (mtools: needs mmu) that added the MMU
dependency.
baurch
> help
> Mtools is a collection of utilities to access MS-DOS disks from
> --
> 1.7.10.4
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-03-30 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 9:20 [Buildroot] [PATCH 1/1] mtools: Does not compile on bfin Bernd Kuhls
2014-03-30 9:25 ` Baruch Siach [this message]
2014-03-30 9:52 ` Bernd Kuhls
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=20140330092505.GE4579@tarshish \
--to=baruch@tkos.co.il \
--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