All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-06
Date: Sat, 9 Nov 2019 14:30:00 +0100	[thread overview]
Message-ID: <20191109143000.37b5a746@windsurf> (raw)
In-Reply-To: <569eeff2-f02f-3506-5cdc-1f02a8e3c325@gmail.com>

On Sat, 9 Nov 2019 14:09:50 +0100
Romain Naour <romain.naour@gmail.com> wrote:

> Well, It's the same problem as for using llvm/clang on the host to build some
> host tools. For your case you have to build hos-llvm with your host variant
> (x86_64 for example) (LLVM_TARGETS_TO_BUILD).
> 
> But since we use the same LLVM_TARGET_ARCH for the host-llvm and llvm, we need
> to use -target x86_64-linux-gnu when using clang.

Wouldn't it be more "natural" for clang to by default produce binaries
for the host, and when you want to cross-compile, have to explicitly
pass -target arm-something-something ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-11-09 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5dc3c4b8.1c69fb81.ff4f2.2a4cSMTPIN_ADDED_MISSING@mx.google.com>
2019-11-09 10:40 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-06 Romain Naour
2019-11-09 12:01   ` Yann E. MORIN
2019-11-09 13:09     ` Romain Naour
2019-11-09 13:30       ` Thomas Petazzoni [this message]
2019-11-09 13:42         ` Romain Naour
2019-11-09 21:33       ` Yann E. MORIN
2019-11-17 19:22         ` Arnout Vandecappelle
2019-11-09 22:29   ` Peter Seiderer

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=20191109143000.37b5a746@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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 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.