From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] iproute2 build error
Date: Thu, 10 Oct 2013 07:37:19 +0300 [thread overview]
Message-ID: <20131010043719.GU4875@tarshish> (raw)
In-Reply-To: <CALoHCLPE6SOyJM58kDXFyTxhKoCiJs4qQ1Gzk2Fsa_0-1ubViA@mail.gmail.com>
Hi Eric,
On Wed, Oct 09, 2013 at 03:49:45PM -0700, Eric Seifert wrote:
> Hello, I was on buildroot-2012.08 and am trying to get up to date, so I am
> using the git repo directly now with the latest changes. Previously
> iproute2 was building successfully (v3.4.0), now I am getting this iproute2
> build error (v3.11.0). I am building for PowerPC 8548/e500v2 (SPE). I am
> using an external toolchain gcc4.3.2 that uses eglibc. Any help would be
> great.
[...]
> libnetlink.c: In function 'rtnl_open_byproto':
> libnetlink.c:46: error: 'SOCK_CLOEXEC' undeclared (first use in this
> function)
> libnetlink.c:46: error: (Each undeclared identifier is reported only once
> libnetlink.c:46: error: for each function it appears in.)
> make[2]: *** [libnetlink.o] Error 1
It seems that you toolchain is missing the definition of SOCK_CLOEXEC. What
version of eglibc are you using?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2013-10-10 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 22:49 [Buildroot] iproute2 build error Eric Seifert
2013-10-10 4:37 ` Baruch Siach [this message]
2013-10-10 7:10 ` Thomas Petazzoni
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=20131010043719.GU4875@tarshish \
--to=baruch@tkos.co.il \
--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.