All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Wunderlich <frank-w@public-files.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Aw: Re: Crosscompiling iproute2
Date: Tue, 18 May 2021 16:19:29 +0200	[thread overview]
Message-ID: <trinity-ebe68814-ee65-4efc-b059-e59e7fea5200-1621347569206@3c-app-gmx-bs02> (raw)
In-Reply-To: <20210517123628.13624eeb@hermes.local>


> Gesendet: Montag, 17. Mai 2021 um 21:36 Uhr
> Von: "Stephen Hemminger" <stephen@networkplumber.org>
> An: "Frank Wunderlich" <frank-w@public-files.de>
> Cc: netdev@vger.kernel.org
> Betreff: Re: Crosscompiling iproute2
> Cross compile needs to know the compiler for building non-cross tools as well.
> This works for me:
>
> make CC="$CC" LD="$LD" HOSTCC=gcc

Thanks, works for me too, also with dynamic linking (without "LDFLAGS=-static")

CROSS_COMPILE=arm-linux-gnueabihf-
make -j8 CC="${CROSS_COMPILE}gcc" LD="${CROSS_COMPILE}-ld" HOSTCC=gcc

only see warning

libnetlink.c:154:2: warning: #warning "libmnl required for error support" [-Wcpp]

but i guess i can ignore it

regards Frank

  reply	other threads:[~2021-05-18 14:19 UTC|newest]

Thread overview: 14+ 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
2021-05-17  7:44   ` Aw: " Frank Wunderlich
2021-05-17 19:36     ` Stephen Hemminger
2021-05-18 14:19       ` Frank Wunderlich [this message]
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
2021-05-25 14:35 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=trinity-ebe68814-ee65-4efc-b059-e59e7fea5200-1621347569206@3c-app-gmx-bs02 \
    --to=frank-w@public-files.de \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 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.