From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] iproute2 build errors when updating to 4.6
Date: Tue, 24 May 2016 15:01:43 +0200 [thread overview]
Message-ID: <20160524130143.GA3162@archie.localdomain> (raw)
In-Reply-To: <74398021-6cef-6626-2a22-eff21cae84bb@pengutronix.de>
Hi Alex, Hi Michael,
On Tue, May 24, 2016 at 09:30:41AM +0200, Alexander Aring wrote:
> Maybe to add KERNEL_INCLUDE=${KERNEL_HEADERS_DIR) in IPROUTE2_MAKE_OPT is
> enough here, or leave it empty to use maybe the fallback?
>
> I think to updating to use KERNEL_INCLUDE=${KERNEL_HEADERS_DIR) would be
> nice in ptxdist, if this solves your issue.
>
Thank you for your help!
I tried adding KERNEL_INCLUDE=$(KERNEL_HEADERS_DIR) to the MAKE_OPTS but
that alone did not fix the problem. It still used the toolchain headers.
Including net/if.h before linux/if.h fixes the redefinition errors, but now I
get: fatal error: xtables-version.h: No such file or directory
Although the iptables dependency should be optional.
Is this a bug in the hand-crafted configure script of iproute2 and can
you reproduce this on your machines?
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-05-24 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 23:55 Clemens Gruber
2016-05-24 7:20 ` Alexander Aring
2016-05-24 7:30 ` Alexander Aring
2016-05-24 13:01 ` Clemens Gruber [this message]
2016-05-24 15:24 ` Alexander Aring
2016-05-24 18:08 ` Alexander Aring
2016-05-25 17:42 ` Clemens Gruber
2016-05-29 18:31 ` Alexander Aring
2016-05-30 19:59 ` Clemens Gruber
2016-06-15 18:37 ` Alexander Aring
2016-06-16 16:19 ` Clemens Gruber
2016-05-24 10:04 ` Michael Olbrich
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=20160524130143.GA3162@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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