From: Axel Lin <axel.lin@ingics.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] logrotate: nees mmu
Date: Tue, 01 Oct 2013 10:31:42 +0800 [thread overview]
Message-ID: <1380594702.9353.1.camel@phoenix> (raw)
Signed-off-by: Axel Lin <axel.lin@ingics.com>
---
Fix below build error:
logrotate.o: In function `switch_user_permanently':
/opt/test/buildroot/buildroot/output/build/logrotate-3.8.4/logrotate.c:129: undefined reference to `fork'
logrotate.o: In function `removeLogFile':
/opt/test/buildroot/buildroot/output/build/logrotate-3.8.4/logrotate.c:431: undefined reference to `fork'
logrotate.o: In function `mailLog':
/opt/test/buildroot/buildroot/output/build/logrotate-3.8.4/logrotate.c:597: undefined reference to `fork'
/opt/test/buildroot/buildroot/output/build/logrotate-3.8.4/logrotate.c:615: undefined reference to `fork'
logrotate.o: In function `compressLogFile':
/opt/test/buildroot/buildroot/output/build/logrotate-3.8.4/logrotate.c:533: undefined reference to `fork'
collect2: ld returned 1 exit status
make[1]: *** [logrotate] Error 1
package/logrotate/Config.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/logrotate/Config.in b/package/logrotate/Config.in
index 0d0ec61..bc7b295 100644
--- a/package/logrotate/Config.in
+++ b/package/logrotate/Config.in
@@ -2,6 +2,7 @@ config BR2_PACKAGE_LOGROTATE
bool "logrotate"
select BR2_PACKAGE_POPT
depends on BR2_USE_WCHAR
+ depends on BR2_USE_MMU # fork()
help
A simple program to rotate logs.
--
1.8.1.2
next reply other threads:[~2013-10-01 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 2:31 Axel Lin [this message]
2013-10-01 2:32 ` [Buildroot] [PATCH 2/2] logrotate: bump to version 3.8.6 Axel Lin
2013-10-01 19:33 ` Peter Korsgaard
2013-10-01 7:32 ` [Buildroot] [PATCH 1/2] logrotate: nees mmu Thomas Petazzoni
2013-10-01 8:08 ` Axel Lin
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=1380594702.9353.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.