Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/llvm: set the path to llvm-config
Date: Mon, 28 Jan 2019 18:04:54 +0100	[thread overview]
Message-ID: <87fttcemrt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190116213921.2280-1-romain.naour@smile.fr> (Romain Naour's message of "Wed, 16 Jan 2019 22:39:21 +0100")

>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:

 > While building llvm for the target (x86_64), the build failded due to
 > path poisoning (-I/usr/include/libxml2) while building NATIVE tools
 > (i.e for the host). The llvm package try to build a tool for the host
 > with the cross-compiler which doesn't work when the paranoid toolchain
 > wrapper (BR2_COMPILER_PARANOID_UNSAFE_PATH) is enabled.

 > We know that llvm (target) needs llvm-tablegen and llvm-config build by
 > host-llvm, but only LLVM_TABLEGEN is provided by llvm.mk. Adding
 > LLVM_CONFIG_PATH=$(HOST_DIR)/bin/llvm-config for llvm (target)
 > fixes the path poisoining issue since llvm doesn't build the NATIVE
 > variant.

 > Signed-off-by: Romain Naour <romain.naour@smile.fr>
 > Cc: Valentin Korenblit <valentinkorenblit@gmail.com>
 > Cc: Matthew Weber <matthew.weber@rockwellcollins.com>
 > ---
 > Valentin, I'm not sure why we don't set LLVM_CONFIG_PATH in llvm.mk for
 > the target variant? We provide it for clang and libclc, why not for
 > llvm ?

Committed to 2018.11.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2019-01-28 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 21:39 [Buildroot] [PATCH] package/llvm: set the path to llvm-config Romain Naour
2019-01-16 23:54 ` Matthew Weber
2019-01-17  8:55 ` Peter Korsgaard
2019-01-17 20:53 ` Valentin Korenblit
2019-01-28 17:04 ` Peter Korsgaard [this message]

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=87fttcemrt.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox