From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] raspberrypi3_qt5we_defconfig fails to build qt5webengine
Date: Mon, 10 Dec 2018 08:52:47 +0100 [thread overview]
Message-ID: <20181210085247.50b55d95@windsurf> (raw)
In-Reply-To: <20181209231707.103f56f9@gmx.net>
Hello,
On Sun, 9 Dec 2018 23:17:07 +0100, Peter Seiderer wrote:
> But QMAKE_COMPILER should already be set in mkspecs/common/g++-base.conf, but
> is changed by buildroot package/qt5/qt5base/qt5base.mk from 'gcc' to
> '/usr/bin/gcc' by
>
> # This allows to use ccache when available
> define QT5BASE_CONFIGURE_HOSTCC
> $(SED) 's,^QMAKE_COMPILER\s*=.*,QMAKE_COMPILER = $(HOSTCC),' $(@D)/mkspecs/common/g++-base.conf
> $(SED) 's,^QMAKE_CC\s*=.*,QMAKE_CC = $(HOSTCC),' $(@D)/mkspecs/common/g++-base.conf
> $(SED) 's,^QMAKE_CXX\s*=.*,QMAKE_CXX = $(HOSTCXX),' $(@D)/mkspecs/common/g++-base.conf
> endef
>
> The rigth fix should be removing the first sed line, QMAKE_COMPILER is the
> compiler flavour and not a compiler path (see e.g. [1])...
Ah, ok. Thanks for looking into this.
> Will send a proper patch (after some testing) soon...
Thanks a lot, and sorry for this breakage, I caused it when adding the
ccache stuff for HOSTCC in qt5base.mk.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-10 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 15:53 [Buildroot] raspberrypi3_qt5we_defconfig fails to build qt5webengine Thomas Petazzoni
2018-12-09 22:17 ` Peter Seiderer
2018-12-10 7:52 ` Thomas Petazzoni [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=20181210085247.50b55d95@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.