From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Pkun <serj.kalichev@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] Fix build system and configure script to use for cross build. Optional IPv6.
Date: Fri, 10 Dec 2010 10:55:31 -0800 [thread overview]
Message-ID: <20101210105531.47e9884a@nehalam> (raw)
In-Reply-To: <AANLkTikFHoMWybK8LWoSKzPhWjVEk1TUSypVsNxEq7nd@mail.gmail.com>
On Fri, 10 Dec 2010 21:13:28 +0300
Pkun <serj.kalichev@gmail.com> wrote:
> 2010/12/10 Stephen Hemminger <shemminger@linux-foundation.org>:
> > On Fri, 10 Dec 2010 18:34:31 +0300
> > Serj Kalichev <serj.kalichev@gmail.com> wrote:
> >
> >> The Makefiles and configure script understand the external variables like
> >> CC, CFLAGS, LDFLAGS etc. So it can be used for cross build easily. The
> >> configure script use CC instead hardcoded gcc and search for the xtables
> >> within specified SYSROOT but not on the host. Two checks were added. The
> >> check for the IPv6 support and check for the Berkeley DB availability.
> >> The iproute2 can be build without IPv6 now.
> >>
> >> Signed-off-by: Serj Kalichev <serj.kalichev@gmail.com>
> >
> > IPv6 support should not be optional.
> >
> >
> > --
> >
>
> Why? I don't need an IPv6. Who need it - will switch it on. No problem
>
Because I want iproute to be a complete tool, not a user configurable
nightmare. Just look at busybox to see what over configuration is.
prev parent reply other threads:[~2010-12-10 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291995271-9912-1-git-send-email-serj.kalichev@gmail.com>
2010-12-10 16:14 ` [PATCH] Fix build system and configure script to use for cross build. Optional IPv6 Stephen Hemminger
2010-12-10 18:13 ` Pkun
2010-12-10 18:55 ` Stephen Hemminger [this message]
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=20101210105531.47e9884a@nehalam \
--to=shemminger@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=serj.kalichev@gmail.com \
/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.