Ever notice most of the *-icon-theme builds take *forever* to build?
Even though they're just copying data, with no compiling happening?
The culprit is makepkg's symlink detection and doinst.sh generation.
To anyone who maintains a build that contains thousands of
symlinks... please consider
On 4/7/20, Tim Dickson via SlackBuilds-users
wrote:
> trying to build the updated qt5 5.12.7 (using sbopkg) is failing for me.
> with the error message.
>
> ninja: build stopped: subcommand failed.
> Makefile.gn_run:1237: recipe for target 'run_ninja' failed
You didn't include enough of the
trying to build the updated qt5 5.12.7 (using sbopkg) is failing for me.
with the error message.
ninja: build stopped: subcommand failed.
Makefile.gn_run:1237: recipe for target 'run_ninja' failed
make[4]: *** [run_ninja] Error 1
make[4]: Leaving directory
Re: Dave Woodfall 08.04.2020 <20200407210510.gb26...@blackswan.r0t.uk>
>On 2020-04-07 14:54,
>MyRequiem put forth the proposition:
>> Packages qt5-legace and qt5 not compatible for simultaneous
>> installation. I understand correctly? I need to remove qt5 and install
>> qt5-legacy in order to use
On 2020-04-07 14:54,
MyRequiem put forth the proposition:
> Packages qt5-legace and qt5 not compatible for simultaneous
> installation. I understand correctly? I need to remove qt5 and install
> qt5-legacy in order to use the package qt5-styleplugins?
That's correct. You can only have one or
> in a previous post, I suggested a different workaround for this problem,
> based in some findings at Google. The starting point was the same
> problem with the unit test, and the solution I chose doesn't disable it.
>
> If you'd like to make an experiment, try the patch mentioned in this
>
On Tue, 7 Apr 2020, Dave Woodfall wrote:
qt5-webkit was listed as required to build both PyQt5 and python3-PyQt5
when I took them over, and I left the dependency lists as they were. I've
just tested building them both without it and didn't see any problems, so
I've now moved qt5-webkit to
On 2020-04-06 16:45,
Rich Shepard put forth the proposition:
> Dave,
>
> I'm curious, and perhaps you know, why qt5-webkit is required for PyQt5
> since Qt5 itself can be built with WEBENGINE=no? (Both Qt5 and PyQT5 take >
> 2 hours to build on my 8-core/16-thread Ryzen 7 2700 desktop with 32G
Hello,
in a previous post, I suggested a different workaround for this problem,
based in some findings at Google. The starting point was the same
problem with the unit test, and the solution I chose doesn't disable it.
If you'd like to make an experiment, try the patch mentioned in this
email:
Re: Dave Woodfall 07.04.2020 <20200407102959.gg30...@blackswan.r0t.uk>
>On 2020-04-07 09:36,
>MyRequiem put forth the proposition:
>> Hi All
>>
>> System: Slackware64 14.2
>>
>> After qt5 package upgrade to version 5.12.7 (I build this without
>> support webengine: WEBENGINE=${WEBENGINE:-no}),
On 2020-04-07 09:36,
MyRequiem put forth the proposition:
> Hi All
>
> System: Slackware64 14.2
>
> After qt5 package upgrade to version 5.12.7 (I build this without
> support webengine: WEBENGINE=${WEBENGINE:-no}), I'm trying to build
> qt5-styleplugins package, but build fails with errors:
>
>
11 matches
Mail list logo
