All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libclc: disable ccache
Date: Mon, 6 Apr 2020 19:11:47 +0200	[thread overview]
Message-ID: <8e448ddf-c8f8-5209-bfab-a5c813b90ff9@gmail.com> (raw)
In-Reply-To: <20200406165045.2607140-1-aduskett@gmail.com>

Hi Adam, All,

Le 06/04/2020 ? 18:50, aduskett at gmail.com a ?crit?:
> From: Adam Duskett <Aduskett@gmail.com>
> 
> Configure.py extracts arch, vendor, and os from the passed
> toolchain string on line 180. When using ccache, the passed path string is
> "/usr/lib64/ccache/g++" which breaks the logic, causing the following error:
> 
> Traceback (most recent call last):
>   File "./configure.py", line 180, in <module>
>     (t_arch, t_vendor, t_os) = target.split('-')
> ValueError: not enough values to unpack (expected 3, got 1)
> 
> Use --with-cxx-compiler=$(HOSTCXX_NOCCACHE) instead of $(HOSTCXX) to fix the
> above error.
> 
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>
> ---
>  package/libclc/libclc.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/libclc/libclc.mk b/package/libclc/libclc.mk
> index 52249a7087..630616905c 100644
> --- a/package/libclc/libclc.mk
> +++ b/package/libclc/libclc.mk
> @@ -25,7 +25,7 @@ LIBCLC_CONF_OPTS = \
>  	--prefix=/usr \
>  	--includedir=/usr/share \
>  	--pkgconfigdir=/usr/lib/pkgconfig \
> -	--with-cxx-compiler=$(HOSTCXX)
> +	--with-cxx-compiler=$(HOSTCXX_NOCCACHE)

I don't use ccache while testing...

Reviewed-by: Romain Naour <romain.naour@gmail.com>

Best regards,
Romain

>  
>  define LIBCLC_CONFIGURE_CMDS
>  	(cd $(@D); $(TARGET_CONFIGURE_OPTS) ./configure.py $(LIBCLC_CONF_OPTS))
> 

  reply	other threads:[~2020-04-06 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 16:50 [Buildroot] [PATCH 1/1] package/libclc: disable ccache aduskett at gmail.com
2020-04-06 17:11 ` Romain Naour [this message]
2020-04-06 20:13 ` Yann E. MORIN

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=8e448ddf-c8f8-5209-bfab-a5c813b90ff9@gmail.com \
    --to=romain.naour@gmail.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.