the md5 sum seems to be different for qt5-webkit. I'm getting
22e442063e7d0362439934442e269ed2
but am expecting cd77f90cbf312f88d23699a65cd76ee4
have downloaded a couple of times just in case, but still different.
(I got qt5 built ok (8gb ram is enough).)
On 19/04/2020 22:09, Dave Woodfall wr
With the provisos mentioned in my previous communication, I was able to
build ffmpeg4.
On Mon, Apr 20, 2020 at 11:36 AM Luveh Keraph <1.41...@gmail.com> wrote:
> It is building all right, in that it did not choke on opencv as I reported
> here before. However, I could not get opencv-legacy to bui
It is building all right, in that it did not choke on opencv as I reported
here before. However, I could not get opencv-legacy to build with tesseract
already installed. I had to remove tesseract, build and install
opencv-legacy, build and install tesseract, and then launch the build of
ffmpeg4. T
On Sun, 19 Apr 2020, B Watson wrote:
More patience. And/or more RAM, if you can.
I set up ccache and let Qt5 build. It took 4h 55min on my Ryzen7 2700
desktop with 32G RAM. That's a lot of time for a UI widget library, but it
tries to do everything, everywhere, for everybody.
Reading the ccac
Hi,
I have not tried the latest version but can you confirm if the legacy
opencv is needed instead.
On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41...@gmail.com> wrote:
> I am using the following ffmpeg4.sqf file in a freshly installed (and
> up-to-date) 14.2 system:
>
> libass
> chromaprint
>
‐‐‐ Original Message ‐‐‐
On Monday, April 20, 2020 12:58 PM, flinchx via SlackBuilds-users
wrote:
> I will try the patch for retroshare now and will report back.
Retroshare works too now.
Since all issues addresed in this thread seem fixed, I will provide a brief
summary so it gets ar
‐‐‐ Original Message ‐‐‐
On Monday, April 20, 2020 12:48 PM, Dave Woodfall wrote:
> This is what I've found is a good order to upgrade Qt5 for large
> version jumps, like 5.7 to 5.9, or 5.9 to 5.12:
>
> 1 Uninstall the old Qt5 package
> 2 Log out of root
> 3 Log back in as root
> 4 Build
On 2020-04-20 09:04,
Slackbuilds Users put forth the proposition:
> ‐‐‐ Original Message ‐‐‐
> On Monday, April 20, 2020 8:59 AM, Dave Woodfall wrote:
>
> > I have some results.
> >
> > qt5-styleplugins
> >
> > This is now relegated to qt5-legacy I'm afraid. They only made one
> > release
-‐‐ Original Message ‐‐‐
On Monday, April 20, 2020 12:19 PM, flinchx wrote:
> I have also tried to run qt5ct like this:
>
> $ QT_DEBUG_PLUGINS=1 qt5ct
>
> the runtime log is attached
I think I'm getting some progress. I went and removed both qt5ct and
qt5-styleplugins. Rebuilt qbittorre
can you please post the output of this command?
ls -1 /var/log/packages/qt*
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pip
‐‐‐ Original Message ‐‐‐
On Monday, April 20, 2020 12:04 PM, flinchx via SlackBuilds-users
wrote:
> ‐‐‐ Original Message ‐‐‐
> On Monday, April 20, 2020 8:59 AM, Dave Woodfall d...@slackbuilds.org wrote:
>
> > I have some results.
> > qt5-styleplugins
> > This is now relegated to
‐‐‐ Original Message ‐‐‐
On Monday, April 20, 2020 8:59 AM, Dave Woodfall wrote:
> I have some results.
>
> qt5-styleplugins
>
> This is now relegated to qt5-legacy I'm afraid. They only made one
> release in 2014, plus one commit since then in 2017.
I saw the other email, but I'll reply
On 2020-04-20 08:50,
Dave Woodfall put forth the proposition:
> On 2020-04-20 07:17,
> Dave Woodfall put forth the proposition:
> > On 2020-04-20 06:59,
> > Dave Woodfall put forth the proposition:
> > > On 2020-04-20 00:00,
> > > Slackbuilds Users put forth the
> > > proposition:
> > > > I ha
On 2020-04-20 07:17,
Dave Woodfall put forth the proposition:
> On 2020-04-20 06:59,
> Dave Woodfall put forth the proposition:
> > On 2020-04-20 00:00,
> > Slackbuilds Users put forth the
> > proposition:
> > > I have attached the required build logs. I have also included the build
> > > log
14 matches
Mail list logo