From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3271] New: netperf-2.4.5 fails to compile
Date: Fri, 18 Feb 2011 03:08:06 +0000 (UTC) [thread overview]
Message-ID: <bug-3271-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3271
Summary: netperf-2.4.5 fails to compile
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: keguang.zhang at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
if
/home/kelvin/buildroot/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc
--sysroot=/home/kelvin/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot
-DHAVE_CONFIG_H -I. -I. -I.. -pipe -Os -mtune=arm926ej-s -march=armv5te
-mabi=aapcs-linux -msoft-float -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -MT netslot_linux.o -MD -MP -MF
".deps/netslot_linux.Tpo" \
-c -o netslot_linux.o `test -f 'netslot_linux.c' || echo
'./'`netslot_linux.c; \
then mv -f ".deps/netslot_linux.Tpo" ".deps/netslot_linux.Po"; \
else rm -f ".deps/netslot_linux.Tpo"; exit 1; \
fi
netslot_linux.c:2:17: error: ftw.h: No such file or directory
netslot_linux.c:13: warning: 'struct FTW' declared inside parameter list
netslot_linux.c:13: warning: its scope is only this definition or declaration,
which is probably not what you want
netslot_linux.c:13: warning: 'struct stat' declared inside parameter list
netslot_linux.c: In function 'find_slot':
netslot_linux.c:24: error: dereferencing pointer to incomplete type
netslot_linux.c: At top level:
netslot_linux.c:68: warning: 'struct FTW' declared inside parameter list
netslot_linux.c:68: warning: 'struct stat' declared inside parameter list
netslot_linux.c: In function 'find_interface':
netslot_linux.c:73: error: dereferencing pointer to incomplete type
netslot_linux.c: In function 'find_interface_slot':
netslot_linux.c:100: error: 'FTW_PHYS' undeclared (first use in this function)
netslot_linux.c:100: error: (Each undeclared identifier is reported only once
netslot_linux.c:100: error: for each function it appears in.)
make[4]: *** [netslot_linux.o] ?? 1
make[4]: *** ??????????....
make[4]:?????? `/home/kelvin/buildroot/output/build/netperf-2.4.5/src'
make[3]: *** [all-recursive] ?? 1
make[3]:?????? `/home/kelvin/buildroot/output/build/netperf-2.4.5/src'
make[2]: *** [all-recursive] ?? 1
make[2]:?????? `/home/kelvin/buildroot/output/build/netperf-2.4.5'
make[1]: *** [all] ?? 2
make[1]:?????? `/home/kelvin/buildroot/output/build/netperf-2.4.5'
make: *** [/home/kelvin/buildroot/output/build/netperf-2.4.5/.stamp_built] ?? 2
--
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:[~2011-02-18 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 3:08 bugzilla at busybox.net [this message]
2011-02-18 3:12 ` [Buildroot] [Bug 3271] netperf-2.4.5 fails to compile bugzilla at busybox.net
2011-09-02 3:53 ` bugzilla at busybox.net
2011-09-02 4:19 ` bugzilla at busybox.net
2011-09-02 4:24 ` bugzilla at busybox.net
2011-09-02 4:32 ` bugzilla at busybox.net
2011-09-18 10:22 ` 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-3271-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