[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210524143620.465dd25d@hermes.local>
Date: Mon, 24 May 2021 14:36:20 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Frank Wunderlich <frank-w@...lic-files.de>
Cc: netdev@...r.kernel.org
Subject: Re: Crosscompiling iproute2
On Mon, 24 May 2021 21:06:02 +0200
Frank Wunderlich <frank-w@...lic-files.de> wrote:
> Am 17. Mai 2021 21:36:28 MESZ schrieb Stephen Hemminger <stephen@...workplumber.org>:
> >On Mon, 17 May 2021 09:44:21 +0200
> >This works for me:
> >
> >make CC="$CC" LD="$LD" HOSTCC=gcc
>
> Hi,
>
> Currently have an issue i guess from install. After compile i install into local directory,pack it and unpack on target system (/usr/local/sbin).tried
>
> https://github.com/frank-w/iproute2/blob/main/crosscompile.sh#L17
>
> Basic ip commands work,but if i try e.g. this
>
> ip link add name lanbr0 type bridge vlan_filtering 1 vlan_default_pvid 500
>
> I get this:
>
> Garbage instead of arguments "vlan_filtering ...". Try "ip link help".
>
> I guess ip tries to call bridge binary from wrong path (tried $PRFX/usr/local/bin).
>
> regards Frank
No ip command does not call bridge.
More likely either your kernel is out of date with the ip command (ie new ip command is asking for
something kernel doesn't understand); or the iplink_bridge.c was not compiled as part of your compile;
or simple PATH issue
or your system is not handling dlopen(NULL) correctly.
What happens is that the "type" field in ip link triggers the code
to use dlopen as form of introspection (see get_link_kind)
Powered by blists - more mailing lists