From: Stephen Hemminger <stephen@networkplumber.org>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: netdev@vger.kernel.org
Subject: Re: Crosscompiling iproute2
Date: Sun, 16 May 2021 14:17:45 -0700 [thread overview]
Message-ID: <20210516141745.009403b7@hermes.local> (raw)
In-Reply-To: <trinity-a96735e9-a95a-45be-9386-6e0aa9955a86-1621176719037@3c-app-gmx-bap46>
On Sun, 16 May 2021 16:51:59 +0200
Frank Wunderlich <frank-w@public-files.de> wrote:
> Hi,
>
> i want to crosscompile (a modified version of) iproute2 (git://git.kernel.org/pub/scm/network/iproute2/iproute2.git) for armhf
>
> do you any idea how?
> configure-script seems to ignore "--host=arm-linux-gnueabihf" like i'm using for nftables
>
> i modified Makefile
>
> -CC := gcc
> +CC := arm-linux-gnueabihf-gcc
>
> -SUBDIRS=lib ip tc bridge misc netem genl tipc devlink rdma dcb man vdpa
> +#SUBDIRS=lib ip tc bridge misc netem genl tipc devlink rdma dcb man vdpa
> +SUBDIRS=ip
>
> and run make like this to use static linking:
>
> make LDFLAGS=-static
>
> but it seems ip always needs libutil
>
> make[1]: *** No rule to make target '../lib/libutil.a', needed by 'ip'. Stop.
>
> if i include lib in SUBDIRS i get many errors about missing libs like selinux and mnl
>
> regards Frank
It is possible to mostly do a cross build if you do:
$ make CC="$CC" LD="$LD"
There are issues with netem local table generation
next prev parent reply other threads:[~2021-05-16 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 14:51 Crosscompiling iproute2 Frank Wunderlich
2021-05-16 21:17 ` Stephen Hemminger [this message]
2021-05-17 7:44 ` Aw: " Frank Wunderlich
2021-05-17 19:36 ` Stephen Hemminger
2021-05-18 14:19 ` Aw: " Frank Wunderlich
2021-05-24 19:06 ` Frank Wunderlich
2021-05-24 21:36 ` Stephen Hemminger
2021-05-25 15:56 ` Frank Wunderlich
2021-05-25 16:08 ` Stephen Hemminger
2021-05-25 18:18 ` Aw: " Frank Wunderlich
2021-05-25 21:37 ` Stephen Hemminger
2021-05-26 7:28 ` Aw: " Frank Wunderlich
2021-05-25 13:30 ` Frank Wunderlich
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=20210516141745.009403b7@hermes.local \
--to=stephen@networkplumber.org \
--cc=frank-w@public-files.de \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).