From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] nano: needs mmu
Date: Thu, 03 Oct 2013 12:12:41 +0200 [thread overview]
Message-ID: <87hacyoe7a.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1380766412.29754.0.camel@phoenix> (Axel Lin's message of "Thu, 03 Oct 2013 10:13:32 +0800")
>>>>> "Axel" == Axel Lin <axel.lin@ingics.com> writes:
Axel> Fix below build error if !BR2_USE_MMU:
Axel> text.o: In function `execute_command':
Axel> text.c:(.text+0x7f8): undefined reference to `fork'
Axel> text.o: In function `do_int_speller':
Axel> text.c:(.text+0x3480): undefined reference to `fork'
Axel> text.c:(.text+0x34f4): undefined reference to `fork'
Axel> text.c:(.text+0x3568): undefined reference to `fork'
Axel> text.o: In function `do_alt_speller':
Axel> text.c:(.text+0x3914): undefined reference to `fork'
Axel> collect2: ld returned 1 exit status
Axel> make[3]: *** [nano] Error 1
Axel> Signed-off-by: Axel Lin <axel.lin@ingics.com>
Axel> ---
Axel> package/nano/Config.in | 1 +
Axel> 1 file changed, 1 insertion(+)
Axel> diff --git a/package/nano/Config.in b/package/nano/Config.in
Axel> index ef7f69d..036313f 100644
Axel> --- a/package/nano/Config.in
Axel> +++ b/package/nano/Config.in
Axel> @@ -1,5 +1,6 @@
Axel> config BR2_PACKAGE_NANO
Axel> bool "nano"
Axel> + depends on BR2_USE_MMU # fork()
The part using fork() is actually only built if the full blown nano
version is used, so I changed this to simply be:
# full version uses fork()
select BR2_PACKAGE_NANO_TINY if !BR2_USE_MMU
And committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-10-03 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 2:13 [Buildroot] [PATCH] nano: needs mmu Axel Lin
2013-10-03 10:12 ` Peter Korsgaard [this message]
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=87hacyoe7a.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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