Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: specify llvm-prefix
Date: Tue, 31 Mar 2015 13:55:20 +0200	[thread overview]
Message-ID: <20150331135520.1e5d2744@free-electrons.com> (raw)
In-Reply-To: <551A7CE6.2070701@zacarias.com.ar>

Dear Gustavo Zacarias,

On Tue, 31 Mar 2015 07:54:30 -0300, Gustavo Zacarias wrote:
> On 03/31/2015 06:25 AM, Thomas Petazzoni wrote:
> >> +# Avoid automatic search of llvm-config
> >> +MESA3D_CONF_OPTS += --with-llvm-prefix=$(STAGING_DIR)/usr/bin
> > 
> > Shouldn't we instead test if LLVM is available, explicitly disable LLVM
> > support if not, and enable it if LLVM is available?
> 
> We don't have a llvm package in BR, so testing is a non-option.

Well what I meant is that since we don't have a LLVM option right now,
we should display LLVM support completely.

And we do have patches in patchwork to add LLVM.

> There's no explicit option to disable llvm support, hence this is as
> close as it gets without patching.
> (--without-gallium-drivers comes close, but it takes down a whole bunch
> of other stuff as well).

Ok. Applied then, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-03-31 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 23:16 [Buildroot] [PATCH] mesa3d: specify llvm-prefix Gustavo Zacarias
2015-03-31  9:25 ` Thomas Petazzoni
2015-03-31 10:54   ` Gustavo Zacarias
2015-03-31 11:55     ` Thomas Petazzoni [this message]
2015-03-31 11:56       ` Gustavo Zacarias

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=20150331135520.1e5d2744@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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