All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Lin <axel.lin@ingics.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xinetd: needs mmu
Date: Fri, 27 Sep 2013 16:19:19 +0800	[thread overview]
Message-ID: <1380269959.32472.1.camel@phoenix> (raw)

Signed-off-by: Axel Lin <axel.lin@ingics.com>
---
Fixes below build error:

/opt/test/buildroot/buildroot/output/host/usr/bin/arm-buildroot-uclinux-uclibcgnueabi-gcc -pipe -Os   -Wl,-elf2flt -DNO_RPC  -I../libs/include  -o xinetd access.o addr.o builtins.o child.o conf.o confparse.o connection.o env.o ident.o init.o int.o intcommon.o internals.o log.o logctl.o main.o msg.o nvlists.o parse.o parsesup.o parsers.o reconfig.o retry.o sconf.o sensor.o server.o service.o signals.o special.o tcpint.o time.o udpint.o util.o redirect.o xgetloadavg.o options.o includedir.o xtimer.o inet.o xmdns.o -L../libs/lib -lsio -lmisc -lxlog -lportable -lstr -lpset -lm -lcrypt  || rm -f xinetd
init.o: In function `init_daemon':
init.c:(.text+0x318): undefined reference to `fork'
int.o: In function `intercept':
int.c:(.text+0x3a4): undefined reference to `fork'
server.o: In function `server_start':
server.c:(.text+0x1b8): undefined reference to `fork'
collect2: ld returned 1 exit status

 package/xinetd/Config.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/xinetd/Config.in b/package/xinetd/Config.in
index 76fe603..7f3575c 100644
--- a/package/xinetd/Config.in
+++ b/package/xinetd/Config.in
@@ -1,5 +1,6 @@
 config BR2_PACKAGE_XINETD
 	bool "xinetd"
+	depends on BR2_USE_MMU # fork()
 	help
 	  xinetd is a secure replacement for inetd. It was originally written by
 	  panos at cs.colorado.edu.
-- 
1.8.1.2

             reply	other threads:[~2013-09-27  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  8:19 Axel Lin [this message]
2013-09-27  9:35 ` [Buildroot] [PATCH] xinetd: needs mmu 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=1380269959.32472.1.camel@phoenix \
    --to=axel.lin@ingics.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.