From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 269] New: iptables fails to compile
Date: Sun, 12 Apr 2009 16:52:52 +0000 (UTC) [thread overview]
Message-ID: <bug-269-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=269
Host: Linux 2.6.28-ARCH #1 SMP PREEMPT Sun Feb 8 10:13:45 UTC
2009 i686 Intel(R) Xeon(R) CPU X3350 @ 2.66GHz
GenuineIntel GNU/Linux
Target: x86_64
Build: Buildroot snapshot 20090412
Summary: iptables fails to compile
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: info at je-eigen-domein.nl
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Building a x86_64 target with iptables and ipv6 fails.
==
/home/max/buildroot/build_x86_64/staging_dir/usr/bin/x86_64-linux-uclibc-gcc
-Os -pipe -Os -I/home/max/buildroot/build_x86_64/staging_dir/usr/include
-I/home/max/buildroot/build_x86_64/staging_dir/include
--sysroot=/home/max/buildroot/build_x86_64/staging_dir/ -isysroot
/home/max/buildroot/build_x86_64/staging_dir -mtune=generic -fPIC -DPIC
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE=1 -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT -Wall
-Waggregate-return -Wmissing-declarations -Wmissing-prototypes
-Wredundant-decls -Wshadow -Wstrict-prototypes -Winline -pipe
-DXTABLES_LIBDIR=\"/usr/lib/xtables\" -DXTABLES_INTERNAL -I./include
-I./include -I /home/max/buildroot/toolchain_build_x86_64/linux/include -I
/home/max/buildroot/toolchain_build_x86_64/linux/include -DENABLE_IPV6=1 -Os
-pipe -Os -I/home/max/buildroot/build_x86_64/staging_dir/usr/include
-I/home/max/buildroot/build_x86_64/staging_dir/include
--sysroot=/home/max/buildroot/build_x86_64/staging_dir/ -isysroot
/home/max/buildroot/build_x86_64/staging_dir -mtune=generic -fPIC -DPIC
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -rdynamic
--sysroot=/home/max/buildroot/build_x86_64/staging_dir/ -o iptables
iptables-standalone.o iptables.o
-L/home/max/buildroot/build_x86_64/staging_dir/lib
-L/home/max/buildroot/build_x86_64/staging_dir/usr/lib -ldl -lm
libiptc/libiptc.a extensions/libext4.a ./.libs/libxtables.so -Wl,--rpath
-Wl,/home/max/buildroot/build_x86_64/iptables-1.4.2/.libs
extensions/libext4.a: could not read symbols: Archive has no index; run ranlib
to add one
collect2: ld returned 1 exit status
make[3]: *** [iptables] Error 1
make[3]: Leaving directory `/home/max/buildroot/build_x86_64/iptables-1.4.2'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/max/buildroot/build_x86_64/iptables-1.4.2'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/max/buildroot/build_x86_64/iptables-1.4.2'
make: *** [/home/max/buildroot/build_x86_64/iptables-1.4.2/.stamp_built] Error
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:[~2009-04-12 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 16:52 bugzilla at busybox.net [this message]
2009-04-27 7:41 ` [Buildroot] [Bug 269] iptables fails to compile bugzilla at busybox.net
2009-04-27 12:42 ` bugzilla at busybox.net
2009-04-27 12:45 ` bugzilla at busybox.net
2009-04-27 14:10 ` bugzilla at busybox.net
2009-08-07 20:19 ` 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-269-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 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.