Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 14:33:25 -0300	[thread overview]
Message-ID: <4D0112E5.301@zacarias.com.ar> (raw)
In-Reply-To: <AANLkTi=T0idFP0k6fFXP3ex6dsupLxMGPgJwz+V4DCkM@mail.gmail.com>

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.

  reply	other threads:[~2010-12-09 17:33 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 [this message]
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
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=4D0112E5.301@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