From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libclc: disable ccache
Date: Mon, 6 Apr 2020 22:13:59 +0200 [thread overview]
Message-ID: <20200406201359.GS22325@scaer> (raw)
In-Reply-To: <20200406165045.2607140-1-aduskett@gmail.com>
Adam, Romain, All,
On 2020-04-06 09:50 -0700, aduskett at gmail.com spake thusly:
> 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.
This is very unfortunate. :-(
But I can see that libclc does have a CMakeList.txt. Can't we make it a
cmake paclage? Presumably, that is supposed to work better than this
hand-crafted atrocity of configure.py... Care to have a look?
In the meantime, I've applied to master, thanks.
Regards,
Yann E. MORIN.
> 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)
>
> define LIBCLC_CONFIGURE_CMDS
> (cd $(@D); $(TARGET_CONFIGURE_OPTS) ./configure.py $(LIBCLC_CONF_OPTS))
> --
> 2.25.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-04-06 20:13 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
2020-04-06 20:13 ` Yann E. MORIN [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=20200406201359.GS22325@scaer \
--to=yann.morin.1998@free.fr \
--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