From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4736] New: lmbench build failure
Date: Thu, 2 Feb 2012 08:24:50 +0000 (UTC) [thread overview]
Message-ID: <bug-4736-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4736
Summary: lmbench build failure
Product: buildroot
Version: 2011.11
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: s.neumann at raumfeld.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Build of lmbench failed:
lat_rpc.c:(.text+0x87): undefined reference to `svcudp_create'
lat_rpc.c:(.text+0xb8): undefined reference to `svctcp_create'
lat_rpc.c:(.text+0x16a): undefined reference to `svc_run'
/tmp/ccV4OkdU.o: In function `main':
lat_rpc.c:(.text+0x277): undefined reference to `clnt_create'
/tmp/ccV4OkdU.o: In function `initialize':
lat_rpc.c:(.text+0x484): undefined reference to `clnt_create'
collect2: ld returned 1 exit status
make[2]: *** [../bin/i586/lat_rpc] Error 1
Looks like lmbench does not only need basic RPC support in the toolchain, it
needs full RPC support.
Compilation fails with this uclibc config:
UCLIBC_HAS_RPC=y
# UCLIBC_HAS_FULL_RPC is not set
# UCLIBC_HAS_REENTRANT_RPC is not set
It succeeds with:
UCLIBC_HAS_RPC=y
UCLIBC_HAS_FULL_RPC=y
UCLIBC_HAS_REENTRANT_RPC=y
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-02-02 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 8:24 bugzilla at busybox.net [this message]
2013-05-04 18:00 ` [Buildroot] [Bug 4736] lmbench build failure bugzilla at busybox.net
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=bug-4736-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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