${BUILD_CC} for host's CC
On Thu, Jun 1, 2017 at 6:30 PM, Khem Raj wrote:
> Export cc=${CC} or some such in recipe
>
> On Thu, Jun 1, 2017 at 6:17 AM Samuli Piippo
> wrote:
>
> > On 01.06.2017 15:57, Daniel Mack wrote:
> > > On 06/01/2017 02:35 PM,
Export cc=${CC} or some such in recipe
On Thu, Jun 1, 2017 at 6:17 AM Samuli Piippo
wrote:
> On 01.06.2017 15:57, Daniel Mack wrote:
> > On 06/01/2017 02:35 PM, Samuli Piippo wrote:
> >> Parts of the chromium is built for the host and requires gcc-multilib to
> >> be
On 06/01/2017 03:16 PM, Samuli Piippo wrote:
> On 01.06.2017 15:57, Daniel Mack wrote:
>> On 06/01/2017 02:35 PM, Samuli Piippo wrote:
>>> Parts of the chromium is built for the host and requires gcc-multilib to
>>> be installed when building on a x64 host. I should have noted that in
>>> commit
On 01.06.2017 15:57, Daniel Mack wrote:
On 06/01/2017 02:35 PM, Samuli Piippo wrote:
Parts of the chromium is built for the host and requires gcc-multilib to
be installed when building on a x64 host. I should have noted that in
commit message.
My /usr/bin/cc is a symlink to gcc
Hmm, same
On 06/01/2017 02:35 PM, Samuli Piippo wrote:
> Parts of the chromium is built for the host and requires gcc-multilib to
> be installed when building on a x64 host. I should have noted that in
> commit message.
>
> My /usr/bin/cc is a symlink to gcc
Hmm, same here, but that's not the case when
On 01.06.2017 10:30, Daniel Mack wrote:
On 05/31/2017 08:40 AM, Samuli Piippo wrote:
* adapt QtWebEngine recipe to use GN instead of GYP
* add QtRemoteObjects as a new Qt module
* update available QtBase configure arguments
* remove obsolete patches
* patch all .pc files to remove build paths
*
On 05/31/2017 08:40 AM, Samuli Piippo wrote:
> * adapt QtWebEngine recipe to use GN instead of GYP
> * add QtRemoteObjects as a new Qt module
> * update available QtBase configure arguments
> * remove obsolete patches
> * patch all .pc files to remove build paths
> * include generated QML cache