From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] iproute2 failing for x86_64 with ext. toolchain
Date: Thu, 09 Dec 2010 15:48:20 -0300 [thread overview]
Message-ID: <4D012474.8050902@zacarias.com.ar> (raw)
In-Reply-To: <AANLkTi=X+CZ9+=yRjcvzfxUecteEGzTgm_6eB+OCGMbG@mail.gmail.com>
On 12/09/10 15:36, Pkun wrote:
> There is a good variable TARGET_CONFIGURE_OPTS within buildroot. It
> contain all possible AR="$(TARGET_AR) CC="$(TARGET_CC) etc. But it's
> long and complex. Probably it will be right to use it for similar cases.
>
> Now I'm making a big patch for iproute2. It has terrible build system
> that don't support cross build. And iproute2's configure script is
> hand-made and use 'gcc' instead $(CC) for example. It can't be build
> without IPv6. I wrote about TARGET_CONFIGURE_OPTS but it can't be used
> for the current iproute2 because it will break the internal CFLAGS
> definitions.
>
> The xtables.h belong to iptables package. But buildroot's iptables don't
> install anything to the staging. The iproute2 uses libxtables.so also.
Keep in mind that doing huge patches that modify upstream source should
be submitted for upstream inclusion, otherwise when there is a new
version for inclusion it might break everything up again.
With regards to IPv6 support i think (and it's a completely personal
opinion) that it's no big deal with the iproute2 case, adding IPv6
support won't make things much bigger than say using real iproute2
versus small busybox iproute2-compatible utils.
Granted, you loose some functionality, but if you want the advanced
stuff you might as well throw IPv6 in.
Regards.
next prev parent reply other threads:[~2010-12-09 18:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 22:21 [Buildroot] iproute2 failing for x86_64 with ext. toolchain Heiko Zuerker
2010-12-09 13:55 ` Gustavo Zacarias
2010-12-09 16:55 ` Heiko Zuerker
2010-12-09 17:28 ` Pkun
2010-12-09 17:33 ` Gustavo Zacarias
2010-12-09 18:26 ` Heiko Zuerker
2010-12-09 18:42 ` Yann E. MORIN
2010-12-09 18:43 ` Heiko Zuerker
2010-12-09 18:46 ` Yann E. MORIN
2010-12-09 19:03 ` Heiko Zuerker
2010-12-09 20:58 ` Heiko Zuerker
2010-12-09 18:36 ` Pkun
2010-12-09 18:48 ` Gustavo Zacarias [this message]
2010-12-09 18:56 ` Pkun
2010-12-11 9:06 ` Pkun
2010-12-11 10:25 ` Thomas Petazzoni
2010-12-11 10:30 ` Gustavo Zacarias
[not found] ` <AANLkTiknNqEPs+cNAnzu-c+wdg=vab2zFuZ+HM-vU8+n@mail.gmail.com>
2010-12-09 17:33 ` Heiko Zuerker
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=4D012474.8050902@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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