[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Heiko Zuerker]

Hey,

the iproute2 compile fails with:
-------------------
/data/devil-linux/../x-tools/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc --sysroot=/data/devil-linux/output/staging -Wl,-export-dynamic  ip.o ipaddress.o ipaddrlabel.o iproute.o iprule.o rtm_map.o iptunnel.o ip6tunnel.o tunnel.o ipneigh.o ipntable.o iplink.o ipmaddr.o ipmonitor.o ipmroute.o ipprefix.o iptuntap.o ipxfrm.o xfrm_state.o xfrm_policy.o xfrm_monitor.o iplink_vlan.o link_veth.o link_gre.o iplink_can.o iplink_macvlan.o ../lib/libnetlink.a ../lib/libutil.a  -lresolv -L../lib -lnetlink -lutil -ldl -o  
ip
../lib/libnetlink.a: could not read symbols: Archive has no index; run  
ranlib to add one
collect2: ld returned 1 exit status
------------------------

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Gustavo Zacarias]

On 12/07/10 19:21, Heiko Zuerker wrote:

> Hey,
> 
> the iproute2 compile fails with:
> -------------------
> /data/devil-linux/../x-tools/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc
> --sysroot=/data/devil-linux/output/staging -Wl,-export-dynamic  ip.o
> ipaddress.o ipaddrlabel.o iproute.o iprule.o rtm_map.o iptunnel.o
> ip6tunnel.o tunnel.o ipneigh.o ipntable.o iplink.o ipmaddr.o ipmonitor.o
> ipmroute.o ipprefix.o iptuntap.o ipxfrm.o xfrm_state.o xfrm_policy.o
> xfrm_monitor.o iplink_vlan.o link_veth.o link_gre.o iplink_can.o
> iplink_macvlan.o ../lib/libnetlink.a ../lib/libutil.a  -lresolv -L../lib
> -lnetlink -lutil -ldl -o ip
> ../lib/libnetlink.a: could not read symbols: Archive has no index; run
> ranlib to add one
> collect2: ld returned 1 exit status
> ------------------------

Can you upload a full build log of the relevant (iproute2) part somewhere?
Thanks.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Heiko Zuerker]

Quoting Gustavo Zacarias <gustavo@zacarias.com.ar>:

> On 12/07/10 19:21, Heiko Zuerker wrote:
>
>> Hey,
>>
>> the iproute2 compile fails with:
>> -------------------
>> /data/devil-linux/../x-tools/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc
>> --sysroot=/data/devil-linux/output/staging -Wl,-export-dynamic  ip.o
>> ipaddress.o ipaddrlabel.o iproute.o iprule.o rtm_map.o iptunnel.o
>> ip6tunnel.o tunnel.o ipneigh.o ipntable.o iplink.o ipmaddr.o ipmonitor.o
>> ipmroute.o ipprefix.o iptuntap.o ipxfrm.o xfrm_state.o xfrm_policy.o
>> xfrm_monitor.o iplink_vlan.o link_veth.o link_gre.o iplink_can.o
>> iplink_macvlan.o ../lib/libnetlink.a ../lib/libutil.a  -lresolv -L../lib
>> -lnetlink -lutil -ldl -o ip
>> ../lib/libnetlink.a: could not read symbols: Archive has no index; run
>> ranlib to add one
>> collect2: ld returned 1 exit status
>> ------------------------
>
> Can you upload a full build log of the relevant (iproute2) part somewhere?
> Thanks.

It's on pastebin: http://pastebin.com/hRhJKpkN

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Pkun]

2010/12/9 Heiko Zuerker <heiko@zuerker.org>

> Quoting Gustavo Zacarias <gustavo@zacarias.com.ar>:
>
>  On 12/07/10 19:21, Heiko Zuerker wrote:
>>
>>  Hey,
>>>
>>> the iproute2 compile fails with:
>>> -------------------
>>>
>>> /data/devil-linux/../x-tools/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc
>>> --sysroot=/data/devil-linux/output/staging -Wl,-export-dynamic  ip.o
>>> ipaddress.o ipaddrlabel.o iproute.o iprule.o rtm_map.o iptunnel.o
>>> ip6tunnel.o tunnel.o ipneigh.o ipntable.o iplink.o ipmaddr.o ipmonitor.o
>>> ipmroute.o ipprefix.o iptuntap.o ipxfrm.o xfrm_state.o xfrm_policy.o
>>> xfrm_monitor.o iplink_vlan.o link_veth.o link_gre.o iplink_can.o
>>> iplink_macvlan.o ../lib/libnetlink.a ../lib/libutil.a  -lresolv -L../lib
>>> -lnetlink -lutil -ldl -o ip
>>> ../lib/libnetlink.a: could not read symbols: Archive has no index; run
>>> ranlib to add one
>>> collect2: ld returned 1 exit status
>>> ------------------------
>>>
>>
>> Can you upload a full build log of the relevant (iproute2) part somewhere?
>> Thanks.
>>
>
> It's on pastebin: http://pastebin.com/hRhJKpkN
>
>
> --
>
> Regards
>  Heiko Zuerker
>  http://www.devil-linux.org
>
>
I think that 'ar' is used from the host but not your
x86_64-unknown-linux-gnu-ar. It can be uncompatible I suppose.

 _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101209/691ef714/attachment-0001.html>

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Gustavo Zacarias]

On 12/09/10 14:28, Pkun wrote:

> 2010/12/9 Heiko Zuerker <heiko at zuerker.org <mailto:heiko@zuerker.org>>
> 
>     Quoting Gustavo Zacarias <gustavo@zacarias.com.ar
>     <mailto:gustavo@zacarias.com.ar>>:
> 
>         On 12/07/10 19:21, Heiko Zuerker wrote:
> 
>             Hey,
> 
>             the iproute2 compile fails with:
>             -------------------
>             /data/devil-linux/../x-tools/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc
>             --sysroot=/data/devil-linux/output/staging
>             -Wl,-export-dynamic  ip.o
>             ipaddress.o ipaddrlabel.o iproute.o iprule.o rtm_map.o
>             iptunnel.o
>             ip6tunnel.o tunnel.o ipneigh.o ipntable.o iplink.o ipmaddr.o
>             ipmonitor.o
>             ipmroute.o ipprefix.o iptuntap.o ipxfrm.o xfrm_state.o
>             xfrm_policy.o
>             xfrm_monitor.o iplink_vlan.o link_veth.o link_gre.o iplink_can.o
>             iplink_macvlan.o ../lib/libnetlink.a ../lib/libutil.a
>              -lresolv -L../lib
>             -lnetlink -lutil -ldl -o ip
>             ../lib/libnetlink.a: could not read symbols: Archive has no
>             index; run
>             ranlib to add one
>             collect2: ld returned 1 exit status
>             ------------------------
> 
> 
>         Can you upload a full build log of the relevant (iproute2) part
>         somewhere?
>         Thanks.
> 
> 
>     It's on pastebin: http://pastebin.com/hRhJKpkN
> 
> 
>     -- 
> 
>     Regards
>      Heiko Zuerker
>      http://www.devil-linux.org
> 
>  
> I think that 'ar' is used from the host but not your
> x86_64-unknown-linux-gnu-ar. It can be uncompatible I suppose.

Yes, that's the problem, even if they were similar it shouldn't be used.
Try changing...
$(MAKE) CC="$(TARGET_CC)" -C $(@D)
to
$(MAKE) CC="$(TARGET_CC)" AR="$(TARGET_AR)" -C $(@D)
in package/iproute/iproute2.mk

Regards.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Heiko Zuerker]

Quoting Gustavo Zacarias <gustavo@zacarias.com.ar>:

> On 12/09/10 14:28, Pkun wrote:
>
>> 2010/12/9 Heiko Zuerker <heiko at zuerker.org <mailto:heiko@zuerker.org>>
>>
>>     Quoting Gustavo Zacarias <gustavo@zacarias.com.ar
>
> Yes, that's the problem, even if they were similar it shouldn't be used.
> Try changing...
> $(MAKE) CC="$(TARGET_CC)" -C $(@D)
> to
> $(MAKE) CC="$(TARGET_CC)" AR="$(TARGET_AR)" -C $(@D)
> in package/iproute/iproute2.mk

Yes that was the issue, now it's going further.
I'll send in a patch for it.

Thanks for the help!

It now blows up because it can't find xtables.h. Seems like the  
external toolchain (ct-ng 1.9.0) didn't include that from the kernel.
I'll do some more testing on it.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Yann E. MORIN]

Heiko, All,

On Thursday 09 December 2010 19:26:57 Heiko Zuerker wrote:
> It now blows up because it can't find xtables.h. Seems like the  
> external toolchain (ct-ng 1.9.0) didn't include that from the kernel.
> I'll do some more testing on it.

xtables.h does not exist in linux-2.6.36, so it can not be installed. ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Heiko Zuerker]

Quoting "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>:

> Heiko, All,
>
> On Thursday 09 December 2010 19:26:57 Heiko Zuerker wrote:
>> It now blows up because it can't find xtables.h. Seems like the
>> external toolchain (ct-ng 1.9.0) didn't include that from the kernel.
>> I'll do some more testing on it.
>
> xtables.h does not exist in linux-2.6.36, so it can not be installed. ;-)

CT_KERNEL_VERSION="2.6.32.25" :D

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Yann E. MORIN]

Heiko, All,

On Thursday 09 December 2010 19:26:57 Heiko Zuerker wrote:
> It now blows up because it can't find xtables.h. Seems like the  
> external toolchain (ct-ng 1.9.0) didn't include that from the kernel.
> I'll do some more testing on it.

As an addendum to my previous mail: xtables.h does no exist. indeed, but
x_tables.h does, and is correctly is installed in my toolchains, here.

It should be included as though:
  #include <linux/netfilter/x_tables.h>

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Heiko Zuerker]

Quoting "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>:

> Heiko, All,
>
> On Thursday 09 December 2010 19:26:57 Heiko Zuerker wrote:
>> It now blows up because it can't find xtables.h. Seems like the
>> external toolchain (ct-ng 1.9.0) didn't include that from the kernel.
>> I'll do some more testing on it.
>
> As an addendum to my previous mail: xtables.h does no exist. indeed, but
> x_tables.h does, and is correctly is installed in my toolchains, here.
>
> It should be included as though:
>   #include <linux/netfilter/x_tables.h>

I tried that and then it choked on some other stuff.

Since I messed around a lot, I recompiled the toolchain (had kernel  
2.6.32 and switched to .25) and did a buildroot "make clean" to make  
sure I have a clean compile.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Heiko Zuerker]

Quoting "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>:

> Heiko, All,
>
> On Thursday 09 December 2010 19:26:57 Heiko Zuerker wrote:
>> It now blows up because it can't find xtables.h. Seems like the
>> external toolchain (ct-ng 1.9.0) didn't include that from the kernel.
>> I'll do some more testing on it.
>
> As an addendum to my previous mail: xtables.h does no exist. indeed, but
> x_tables.h does, and is correctly is installed in my toolchains, here.
>
> It should be included as though:
>   #include <linux/netfilter/x_tables.h>

Mistery solved!
xtables.h comes from iptables, so there's a dependency between  
iproute2 and iptables. In addition to that, iptables needs the AR= fix  
also.

I'll send in a patch later today.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Pkun]

2010/12/9 Gustavo Zacarias <gustavo@zacarias.com.ar>

> On 12/09/10 14:28, Pkun wrote:
>
> > 2010/12/9 Heiko Zuerker <heiko at zuerker.org <mailto:heiko@zuerker.org>>
> >
> >     Quoting Gustavo Zacarias <gustavo@zacarias.com.ar
> >     <mailto:gustavo@zacarias.com.ar>>:
> >
> >         On 12/07/10 19:21, Heiko Zuerker wrote:
> >
> >             Hey,
> >
> >             the iproute2 compile fails with:
> >             -------------------
> >
> /data/devil-linux/../x-tools/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc
> >             --sysroot=/data/devil-linux/output/staging
> >             -Wl,-export-dynamic  ip.o
> >             ipaddress.o ipaddrlabel.o iproute.o iprule.o rtm_map.o
> >             iptunnel.o
> >             ip6tunnel.o tunnel.o ipneigh.o ipntable.o iplink.o ipmaddr.o
> >             ipmonitor.o
> >             ipmroute.o ipprefix.o iptuntap.o ipxfrm.o xfrm_state.o
> >             xfrm_policy.o
> >             xfrm_monitor.o iplink_vlan.o link_veth.o link_gre.o
> iplink_can.o
> >             iplink_macvlan.o ../lib/libnetlink.a ../lib/libutil.a
> >              -lresolv -L../lib
> >             -lnetlink -lutil -ldl -o ip
> >             ../lib/libnetlink.a: could not read symbols: Archive has no
> >             index; run
> >             ranlib to add one
> >             collect2: ld returned 1 exit status
> >             ------------------------
> >
> >
> >         Can you upload a full build log of the relevant (iproute2) part
> >         somewhere?
> >         Thanks.
> >
> >
> >     It's on pastebin: http://pastebin.com/hRhJKpkN
> >
> >
> >     --
> >
> >     Regards
> >      Heiko Zuerker
> >      http://www.devil-linux.org
> >
> >
> > I think that 'ar' is used from the host but not your
> > x86_64-unknown-linux-gnu-ar. It can be uncompatible I suppose.
>
> Yes, that's the problem, even if they were similar it shouldn't be used.
> Try changing...
> $(MAKE) CC="$(TARGET_CC)" -C $(@D)
> to
> $(MAKE) CC="$(TARGET_CC)" AR="$(TARGET_AR)" -C $(@D)
> in package/iproute/iproute2.mk
>
> Regards.
>
>
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101209/3235326a/attachment.html>

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Gustavo Zacarias]

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.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Pkun]

2010/12/9 Gustavo Zacarias <gustavo@zacarias.com.ar>

> 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.
>

Yes, I'll try to send it to the upstream. Anyway I need this patch for my
project that uses buildroot. May be the IPv6 is not huge but it's not good
that project can't be build without it. I already did it so there is no
additional work to do now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101209/7d6f8e9d/attachment.html>

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Pkun]

2010/12/9 Gustavo Zacarias <gustavo@zacarias.com.ar>:
> 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.
>

The author of iproute2 did't accept my patch. Moreover the problem is
not with a bad patch. The author don't want to make IPv6 support
optional and don't want to make iproute2 configurable. From netdev
mailing list: to my question about optional IPv6 he wrote: "Because I
want iproute to be a complete tool, not a user configurable nightmare.
Just look at busybox to see what over configuration is." It's strange
for me. So the upstream problems with iproute2 build system will
continue.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Thomas Petazzoni]

On Sat, 11 Dec 2010 12:06:54 +0300
Pkun <serj.kalichev@gmail.com> wrote:

> The author of iproute2 did't accept my patch. Moreover the problem is
> not with a bad patch. The author don't want to make IPv6 support
> optional and don't want to make iproute2 configurable. From netdev
> mailing list: to my question about optional IPv6 he wrote: "Because I
> want iproute to be a complete tool, not a user configurable nightmare.
> Just look at busybox to see what over configuration is." It's strange
> for me. So the upstream problems with iproute2 build system will
> continue.

So, just make iproute2 depends on BR2_INET_IPV6. iproute2 is a fairly
advanced networking utility, so it doesn't sound unreasonable to have
it depend on IPv6 support.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Gustavo Zacarias]

On 12/11/2010 06:06 AM, Pkun wrote:

> The author of iproute2 did't accept my patch. Moreover the problem is
> not with a bad patch. The author don't want to make IPv6 support
> optional and don't want to make iproute2 configurable. From netdev
> mailing list: to my question about optional IPv6 he wrote: "Because I
> want iproute to be a complete tool, not a user configurable nightmare.
> Just look at busybox to see what over configuration is." It's strange
> for me. So the upstream problems with iproute2 build system will
> continue.

That's bad, sometimes people have different priorities than we do. It
doesn't mean that we can't include your no-ipv6 patch (my opinion
regarding that is merely personal). If it becomes cumbersome in the
future to keep supporting it for whatever reason we can just drop it.
Just don't try to fix things that don't want fixing, like the configure
script as Mike said, better to just do all the configuring in the
package makefile. If the patch to fix it is bigger and doesn't do
anything different and upstream probably won't take it then we shouldn't
bother with it.
Regards.

[Buildroot] iproute2 failing for x86_64 with ext. toolchain

[Heiko Zuerker]

Quoting Lionel Landwerlin <llandwerlin@gmail.com>:

> Just an idea...
> Could you change the BR2_JLEVEL to 1 in your .config file, remove the
> iproute2 build directory and retry ?

same result

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.