From rshepard at appl-ecosys.com Fri Feb 1 16:18:39 2019 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Feb 2019 08:18:39 -0800 (PST) Subject: [Slackbuilds-users] SBo: Upgrading python3 Message-ID: I sent this message to Audrius but it was returned as undeliverable. The SBo repository has python3-3.6.7 while the current release is -3.7.2. I tried building the new version changing the version number in the current script with this result: Python-3.7.2/Objects/typeslots.inc patching file Modules/readline.c Hunk #1 succeeded at 11 (offset -1 lines). patching file Makefile.pre.in Hunk #1 FAILED at 533. Hunk #2 FAILED at 578. Hunk #3 FAILED at 679. Hunk #4 FAILED at 1391. 4 out of 4 hunks FAILED -- saving rejects to file Makefile.pre.in.rej The referenced Makefile.pre.in.rej is attached. I would appreciate your upgrading the SBo repo so version 3.7.2 builds. Thanks in advance, Rich -------------- next part -------------- --- Makefile.pre.in 2017-07-08 06:33:27.000000000 +0300 +++ Makefile.pre.in 2017-08-20 15:03:55.591112188 +0300 @@ -533,7 +533,7 @@ $(RUNSHARED) $(PYTHON_FOR_BUILD) ./Tools/clinic/clinic.py --make # Build the interpreter -$(BUILDPYTHON): Programs/python.o $(LIBRARY) $(LDLIBRARY) $(PY3LIBRARY) +$(BUILDPYTHON): Programs/python.o $(LDLIBRARY) $(PY3LIBRARY) $(LINKCC) $(PY_LDFLAGS) $(LINKFORSHARED) -o $@ Programs/python.o $(BLDLIBRARY) $(LIBS) $(MODLIBS) $(SYSLIBS) $(LDLAST) platform: $(BUILDPYTHON) pybuilddir.txt @@ -578,18 +578,6 @@ $(PYTHON_FOR_BUILD) $(srcdir)/setup.py $$quiet build -# Build static library -# avoid long command lines, same as LIBRARY_OBJS -$(LIBRARY): $(LIBRARY_OBJS) - -rm -f $@ - $(AR) $(ARFLAGS) $@ Modules/getbuildinfo.o - $(AR) $(ARFLAGS) $@ $(PARSER_OBJS) - $(AR) $(ARFLAGS) $@ $(OBJECT_OBJS) - $(AR) $(ARFLAGS) $@ $(PYTHON_OBJS) Python/frozen.o - $(AR) $(ARFLAGS) $@ $(MODULE_OBJS) - $(AR) $(ARFLAGS) $@ $(MODOBJS) - $(RANLIB) $@ - libpython$(LDVERSION).so: $(LIBRARY_OBJS) if test $(INSTSONAME) != $(LDLIBRARY); then \ $(BLDSHARED) -Wl,-h$(INSTSONAME) -o $(INSTSONAME) $(LIBRARY_OBJS) $(MODLIBS) $(SHLIBS) $(LIBC) $(LIBM) $(LDLAST); \ @@ -679,7 +667,7 @@ echo "-----------------------------------------------"; \ fi -Programs/_testembed: Programs/_testembed.o $(LIBRARY) $(LDLIBRARY) $(PY3LIBRARY) +Programs/_testembed: Programs/_testembed.o $(LDLIBRARY) $(PY3LIBRARY) $(LINKCC) $(PY_LDFLAGS) $(LINKFORSHARED) -o $@ Programs/_testembed.o $(BLDLIBRARY) $(LIBS) $(MODLIBS) $(SYSLIBS) $(LDLAST) ############################################################################ @@ -1391,18 +1379,6 @@ else true; \ fi; \ done - @if test -d $(LIBRARY); then :; else \ - if test "$(PYTHONFRAMEWORKDIR)" = no-framework; then \ - if test "$(SHLIB_SUFFIX)" = .dll; then \ - $(INSTALL_DATA) $(LDLIBRARY) $(DESTDIR)$(LIBPL) ; \ - else \ - $(INSTALL_DATA) $(LIBRARY) $(DESTDIR)$(LIBPL)/$(LIBRARY) ; \ - $(RANLIB) $(DESTDIR)$(LIBPL)/$(LIBRARY) ; \ - fi; \ - else \ - echo Skip install of $(LIBRARY) - use make frameworkinstall; \ - fi; \ - fi $(INSTALL_DATA) Modules/config.c $(DESTDIR)$(LIBPL)/config.c $(INSTALL_DATA) Programs/python.o $(DESTDIR)$(LIBPL)/python.o $(INSTALL_DATA) $(srcdir)/Modules/config.c.in $(DESTDIR)$(LIBPL)/config.c.in From willysr at slackbuilds.org Fri Feb 1 16:25:19 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 1 Feb 2019 23:25:19 +0700 Subject: [Slackbuilds-users] SBo: Upgrading python3 In-Reply-To: References: Message-ID: <9e0a87a9-a638-b158-1767-4fe98b4cad70@slackbuilds.org> > I sent this message to Audrius but it was returned as undeliverable. > > The SBo repository has python3-3.6.7 while the current release is -3.7.2. I > tried building the new version changing the version number in the current > script with this result: > > Python-3.7.2/Objects/typeslots.inc > patching file Modules/readline.c > Hunk #1 succeeded at 11 (offset -1 lines). > patching file Makefile.pre.in > Hunk #1 FAILED at 533. > Hunk #2 FAILED at 578. > Hunk #3 FAILED at 679. > Hunk #4 FAILED at 1391. > 4 out of 4 hunks FAILED -- saving rejects to file Makefile.pre.in.rej Try removing all the patches since it's only meant for 3.6. It's probably fixed (or changed) during 3.7 development, thus it will fail to apply -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Fri Feb 1 17:02:04 2019 From: didier at slint.fr (Didier Spaier) Date: Fri, 1 Feb 2019 18:02:04 +0100 Subject: [Slackbuilds-users] SBo: Upgrading python3 In-Reply-To: References: Message-ID: Hello, On 01/02/2019 17:18, Rich Shepard wrote: > I sent this message to Audrius but it was returned as undeliverable. > > The SBo repository has python3-3.6.7 while the current release is -3.7.2. I > tried building the new version changing the version number in the current > script with this result: If you suggest to upgrade Python 3 to 3.7.2 in SBo, I disagree. There are a few backward incompatible changes that need to be handled by existing programs written in Pyton 3.6.x mentioned in this document: https://docs.python.org/3/whatsnew/3.7.html, that's why. But if you just want to upgrade locally, that's fine of course ;) Best, Didier From willysr at slackbuilds.org Fri Feb 1 17:08:57 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 2 Feb 2019 00:08:57 +0700 Subject: [Slackbuilds-users] SBo: Upgrading python3 In-Reply-To: References: Message-ID: <66d0f673-3e8a-736a-1439-be5a877260f2@slackbuilds.org> >> The SBo repository has python3-3.6.7 while the current release is -3.7.2. I >> tried building the new version changing the version number in the current >> script with this result: > > If you suggest to upgrade Python 3 to 3.7.2 in SBo, I disagree. > > There are a few backward incompatible changes that need to be handled > by existing programs written in Pyton 3.6.x mentioned in this document: > https://docs.python.org/3/whatsnew/3.7.html, that's why. > > But if you just want to upgrade locally, that's fine of course ;) I agree. There are a lot of scripts that depends on python3 and unless you can validate that all scripts works with new Python 3.7, it's not going to happen soon. Slackware-Current is also staying at 3.6.x for now. It's better to sync with -current so it ease our job when validating scripts for next Slackware 15.0 repository during development cycle. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Fri Feb 1 17:42:23 2019 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Feb 2019 09:42:23 -0800 (PST) Subject: [Slackbuilds-users] SBo: Upgrading python3 [DONE] In-Reply-To: <9e0a87a9-a638-b158-1767-4fe98b4cad70@slackbuilds.org> References: <9e0a87a9-a638-b158-1767-4fe98b4cad70@slackbuilds.org> Message-ID: On Fri, 1 Feb 2019, Willy Sudiarto Raharjo wrote: > Try removing all the patches since it's only meant for 3.6. It's probably > fixed (or changed) during 3.7 development, thus it will fail to apply Willy, I am appropriately chagrined. I saw the patches/ directory, wondered if they still applied, and ignored them. Shame on me! Removing the patches/ directory and commenting out the few lines referring to patches in the SlackBuild script fixed the problem. Thanks for pointing out the obvious to me. Carpe weekend, Rich From rshepard at appl-ecosys.com Fri Feb 1 17:44:40 2019 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Feb 2019 09:44:40 -0800 (PST) Subject: [Slackbuilds-users] SBo: Upgrading python3 In-Reply-To: References: Message-ID: On Fri, 1 Feb 2019, Didier Spaier wrote: > There are a few backward incompatible changes that need to be handled by > existing programs written in Pyton 3.6.x mentioned in this document: > https://docs.python.org/3/whatsnew/3.7.html, that's why. Didier, I'm working on building an application to use for my business; it's the first full use of Python3 here, and no earlier programs will be upgraded. So, ... > But if you just want to upgrade locally, that's fine of course ;) Glad you agree. :-) Carpe weekend, Rich From rshepard at appl-ecosys.com Fri Feb 1 17:45:50 2019 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Feb 2019 09:45:50 -0800 (PST) Subject: [Slackbuilds-users] SBo: Upgrading python3 In-Reply-To: <66d0f673-3e8a-736a-1439-be5a877260f2@slackbuilds.org> References: <66d0f673-3e8a-736a-1439-be5a877260f2@slackbuilds.org> Message-ID: On Sat, 2 Feb 2019, Willy Sudiarto Raharjo wrote: > I agree. There are a lot of scripts that depends on python3 and unless you > can validate that all scripts works with new Python 3.7, it's not going to > happen soon. I'll watch and see if any SBo package I use now stops working. If so, I'll downgrade to 3.6.2. Regards, Rich From dominik.drobek at o2.pl Fri Feb 1 23:33:53 2019 From: dominik.drobek at o2.pl (Dominik Drobek) Date: Sat, 2 Feb 2019 00:33:53 +0100 Subject: [Slackbuilds-users] Can't build nvidia-kernel-410.78 with kernel 4.4.172 Message-ID: <5332929f-da50-49a5-266c-e274c18efa94@o2.pl> Hi, Has anyone tried to build the NVIDIA proprietary kernel module for the most recent kernel (4.4.172) on Slackware-14.2? I'm getting the following error: CC [M] /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.o In file included from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:21:0, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c: In function 'os_lock_user_pages': /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:120:48: warning: passing argument 6 of 'get_user_pages' makes pointer from integer without a cast [-Wint-conversion] page_count, write, force, user_pages, NULL); ^ /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-mm.h:44:70: note: in definition of macro 'NV_GET_USER_PAGES' get_user_pages(current, current->mm, start, nr_pages, write, force, pages, vmas) ^ In file included from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-pgprot.h:17:0, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:20, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: include/linux/mm.h:1200:6: note: expected 'struct page **' but argument is of type 'NvBool {aka unsigned char}' long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ In file included from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:21:0, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:120:55: warning: passing argument 7 of 'get_user_pages' from incompatible pointer type [-Wincompatible-pointer-types] page_count, write, force, user_pages, NULL); ^ /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-mm.h:44:77: note: in definition of macro 'NV_GET_USER_PAGES' get_user_pages(current, current->mm, start, nr_pages, write, force, pages, vmas) ^ In file included from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-pgprot.h:17:0, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:20, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: include/linux/mm.h:1200:6: note: expected 'struct vm_area_struct **' but argument is of type 'struct page **' long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ In file included from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:21:0, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-mm.h:44:9: error: too many arguments to function 'get_user_pages' get_user_pages(current, current->mm, start, nr_pages, write, force, pages, vmas) ^ /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:119:11: note: in expansion of macro 'NV_GET_USER_PAGES' ret = NV_GET_USER_PAGES((unsigned long)address, ^ In file included from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-pgprot.h:17:0, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:20, from /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: include/linux/mm.h:1200:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ scripts/Makefile.build:277: recipe for target '/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.o' failed make[2]: *** [/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.o] Error 1 Makefile:1436: recipe for target '_module_/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel' failed make[1]: *** [_module_/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel] Error 2 make[1]: Leaving directory '/usr/src/linux-4.4.172' Makefile:79: recipe for target 'modules' failed make: *** [modules] Error 2 (I was using sbopkg only to build the package - not to upgrade it.) Regards, Dominik Drobek From thedoogster at gmail.com Sat Feb 2 00:13:13 2019 From: thedoogster at gmail.com (Doogster) Date: Fri, 1 Feb 2019 16:13:13 -0800 Subject: [Slackbuilds-users] Can't build nvidia-kernel-410.78 with kernel 4.4.172 In-Reply-To: <5332929f-da50-49a5-266c-e274c18efa94@o2.pl> References: <5332929f-da50-49a5-266c-e274c18efa94@o2.pl> Message-ID: There?s, like, 3 threads on LQ about this. On Fri, Feb 1, 2019 at 3:40 PM Dominik Drobek wrote: > Hi, > > Has anyone tried to build the NVIDIA proprietary kernel module for the > most recent kernel (4.4.172) on Slackware-14.2? I'm getting the > following error: > > CC [M] > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.o > In file included from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:21:0, > from > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c: > In function 'os_lock_user_pages': > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:120:48: > > warning: passing argument 6 of 'get_user_pages' makes pointer from > integer without a cast [-Wint-conversion] > page_count, write, force, user_pages, NULL); > ^ > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-mm.h:44:70: > > note: in definition of macro 'NV_GET_USER_PAGES' > get_user_pages(current, current->mm, start, nr_pages, write, > force, pages, vmas) > ^ > In file included from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-pgprot.h:17:0, > from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:20, > from > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: > include/linux/mm.h:1200:6: note: expected 'struct page **' but argument > is of type 'NvBool {aka unsigned char}' > long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, > ^ > In file included from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:21:0, > from > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:120:55: > > warning: passing argument 7 of 'get_user_pages' from incompatible > pointer type [-Wincompatible-pointer-types] > page_count, write, force, user_pages, NULL); > ^ > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-mm.h:44:77: > > note: in definition of macro 'NV_GET_USER_PAGES' > get_user_pages(current, current->mm, start, nr_pages, write, > force, pages, vmas) > > ^ > In file included from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-pgprot.h:17:0, > from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:20, > from > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: > include/linux/mm.h:1200:6: note: expected 'struct vm_area_struct **' but > argument is of type 'struct page **' > long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, > ^ > In file included from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:21:0, > from > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-mm.h:44:9: > > error: too many arguments to function 'get_user_pages' > get_user_pages(current, current->mm, start, nr_pages, write, > force, pages, vmas) > ^ > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:119:11: > > note: in expansion of macro 'NV_GET_USER_PAGES' > ret = NV_GET_USER_PAGES((unsigned long)address, > ^ > In file included from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-pgprot.h:17:0, > from > > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/common/inc/nv-linux.h:20, > from > /tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.c:15: > include/linux/mm.h:1200:6: note: declared here > long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, > ^ > scripts/Makefile.build:277: recipe for target > '/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.o' > failed > make[2]: *** > [/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel/nvidia/os-mlock.o] > Error 1 > Makefile:1436: recipe for target > '_module_/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel' failed > make[1]: *** > [_module_/tmp/sbopkg.eaeOsa/NVIDIA-Linux-x86_64-410.78/kernel] Error 2 > make[1]: Leaving directory '/usr/src/linux-4.4.172' > Makefile:79: recipe for target 'modules' failed > make: *** [modules] Error 2 > > (I was using sbopkg only to build the package - not to upgrade it.) > > > Regards, > Dominik Drobek > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Feb 2 00:40:33 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 2 Feb 2019 07:40:33 +0700 Subject: [Slackbuilds-users] Can't build nvidia-kernel-410.78 with kernel 4.4.172 In-Reply-To: References: <5332929f-da50-49a5-266c-e274c18efa94@o2.pl> Message-ID: <11803edd-66fb-012c-c77a-cd8c1897520f@slackbuilds.org> > Has anyone tried to build the NVIDIA proprietary kernel module for the > most recent kernel (4.4.172) on Slackware-14.2? I'm getting the > following error: The maintainer is aware of this issue and will soon fix it. Meanwhile, you can try to look over this thread on LQ https://www.linuxquestions.org/questions/slackware-14/virtualbox-fails-to-build-drivers-for-kernel-4-4-172-a-4175647407/ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dominik.drobek at o2.pl Sat Feb 2 00:45:51 2019 From: dominik.drobek at o2.pl (Dominik Drobek) Date: Sat, 2 Feb 2019 01:45:51 +0100 Subject: [Slackbuilds-users] Can't build nvidia-kernel-410.78 with kernel 4.4.172 In-Reply-To: <11803edd-66fb-012c-c77a-cd8c1897520f@slackbuilds.org> References: <5332929f-da50-49a5-266c-e274c18efa94@o2.pl> <11803edd-66fb-012c-c77a-cd8c1897520f@slackbuilds.org> Message-ID: <0e67a9b8-a710-be72-3f9f-85eed0297856@o2.pl> > The maintainer is aware of this issue and will soon fix it. > Meanwhile, you can try to look over this thread on LQ > > https://www.linuxquestions.org/questions/slackware-14/virtualbox-fails-to-build-drivers-for-kernel-4-4-172-a-4175647407/ Thank you. It seemed to me that it's appropriate to report the problem here, especially that it hasn't been mentioned in the list yet. Next time I'll look at LQ forums first. Regards, Dominik From willysr at slackbuilds.org Sat Feb 2 01:24:23 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 2 Feb 2019 08:24:23 +0700 Subject: [Slackbuilds-users] Updates - 20190202.1 Message-ID: <6c855cdd-8bc2-fe18-a935-b2e146887125@slackbuilds.org> Hi everyone As you may have noticed, Patrick has released a new kernels on -stable, but it has one API changes which breaks some packages (namely nvidia and virtualbox). Some people in LQ have managed to find a fix for them and the maintainer of virtualbox (Heinz) is aware of this issue and he will have a proper fix in the next public update. Sat Feb 2 01:13:00 UTC 2019 academic/STAR: Updated for version 2.7.0a. academic/lapacke: Build the deprecated routines. academic/ngspice: Add shared library. academic/xflr5: Updated for version 6.43. audio/abcde: Updated for version 2.9.2. audio/flacon: Updated for version 5.1.0. audio/mp4tools: Update DOWNLOAD. desktop/Zafiro-icons: Updated for version 0.8.5. desktop/awesome-extra: Updated for version 2019012501. desktop/fbmenugen: Updated for version 0.83. desktop/gnome-menus: Updated for version 3.31.4. desktop/gtkhash: Correct thunar params. desktop/jgmenu: Updated for version 2.0. desktop/lxmenu-data: Various cleanups. desktop/simplenote: Updated for version 1.4.0. development/beautysh: Updated for version 4.1. development/dpkg: Updated for version 1.19.4. development/eclim: Add patch for building against eclipse 201812. development/eclipse-cpp: Updated for version 201812. development/eclipse-java: Updated for version 201812. development/eclipse-jee: Updated for version 201812. development/hub: Updated for version 2.8.3. development/ninja: Updated for version 1.9.0. development/openjdk8: Updated for version 8u191. development/openjdk: Updated for version 7u201. development/perf: Updated for version 4.4.172. development/postman: Updated for version 6.7.2. development/radare2: Update script. gis/gpxsee: Updated for version 7.2. gis/mapnik: Updated for version 3.0.22. gis/rasterio: Updated for version 1.0.15. graphics/exact-image: Updated for version 1.0.2. graphics/inkscape: Updated for version 0.92.4. graphics/wayland-protocols: Updated for version 1.7. libraries/lapack: Build the deprecated routines. libraries/libdbusmenu: Updated for version 18.10.20180917~bzr490. libraries/libfm-extra: Updated for version 1.3.1, cleanups. libraries/libfm: Updated for version 1.3.1, cleanups. libraries/libinput: Updated for version 1.12.6. libraries/menu-cache: Apply a patch from upstream, cleanups. libraries/zeromq: Updated for version 4.3.1. misc/discount: Updated for version 2.2.5. multimedia/x265: Updated for version 3.0. network/clipgrab: Updated for version 3.8.0. network/filezilla: Updated for version 3.40.0. network/krb5: Updated for version 1.17. network/opera-developer: Updated for version 59.0.3209.0. network/opera: Updated for version 58.0.3135.47. network/phpmyadmin: Updated for version 4.8.5. network/tor-browser: Updated for version 8.0.5. network/waterfox: Updated for version 56.2.7. office/MasterPDFEditor: Updated for version 5.3.02. office/ReText: add a dependency. office/onlyoffice-desktopeditors: Updated for version 5.2.8_3. office/turtl: Added (A secure, collaborative notebook). perl/perl-Math-MPFR: Updated for version 4.08. perl/perl-Module-ScanDeps: Updated for version 1.27. perl/perl-Net-XMPP: Change maintainer info. perl/perl-Term-ReadLine-Gnu: Updated for version 1.36. perl/perl-XML-Stream: Change maintainer info. python/mypy: Updated for version 0.660. python/plaso: Update DEP. python/python-fonttools: Updated for version 3.37.0. python/python-markdown-math: Added (extension for Python-Markdown). python/python3-prompt_toolkit: 2.0.8. python/thonny: Updated for version 3.1.0. python/typed_ast: Updated for version 1.3.0. ruby/ruby-build: Updated for version 20190130. system/dar: Updated for version 2.6.1. system/dget: Updated for version 2.19.2. system/dosbox-dev: Updated for version 0.74.r4184. system/epson-inkjet-printer-escpr2: Updated for version 1.0.30. system/fdupes: Update to version 1.6.1 system/firetools: Updated for version 0.9.58. system/i2c-tools: Updated for version 4.1. system/letsencrypt: Updated for version 0.30.2. system/lynis: Updated for version 2.7.1. system/pcmanfm: Updated for version 1.3.1, cleanups. system/sboui: Update DEP. system/st: Update script. system/winetricks: Updated for version 20181203. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jorge.giner at hotmail.com Sat Feb 2 16:43:58 2019 From: jorge.giner at hotmail.com (Jorge Giner Cordero) Date: Sat, 2 Feb 2019 16:43:58 +0000 Subject: [Slackbuilds-users] Package name change: how to proceed Message-ID: Hello, I maintain two packages one named obnc and the other obnc-libstd. The first is an Oberon compiler and basic library and the second is a library for it with extra functionality. The author of the compiler has decided to rename second from obnc-libstd to obnc-libext. How should I proceed? Should I make a new SlackBuild named obnc-libext and request the removal of obnc-libstd? Additionally, I wanted to ask which is the correct way to proceed when using the mirror of Slackbuilds on github (https://github.com/willysr/slackbuilds). Is the correct way fork that repository, make changes and then do a pull request? Is this better (easier) for the team maintaing Slackbuilds.org than submitting the tar.gz? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Feb 2 16:46:36 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 2 Feb 2019 23:46:36 +0700 Subject: [Slackbuilds-users] Package name change: how to proceed In-Reply-To: References: Message-ID: > I maintain two packages one named obnc and the other obnc-libstd. The > first is an Oberon compiler and basic library and the second is a > library for it with extra functionality. The author of the compiler has > decided to rename second from obnc-libstd to obnc-libext. > > How should I proceed? Should I make a new SlackBuild named obnc-libext > and request the removal of obnc-libstd? You can keep the same name if you like or submit a new name and leave a comment section to remove the old name. > Additionally, I wanted to ask which is the correct way to proceed when > using the mirror of Slackbuilds on github > (https://github.com/willysr/slackbuilds). Is the correct way fork that > repository, make changes and then do a pull request? Is this better > (easier) for the team maintaing Slackbuilds.org than submitting the tar.gz? It's better to send PR/MR through this repositories: https://github.com/SlackBuildsOrg/slackbuilds/ https://gitlab.com/SlackBuilds.org/slackbuilds/ Both submission and PR/MR works fine with us -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From z.coldplayer at gmail.com Sat Feb 2 17:35:49 2019 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sat, 2 Feb 2019 21:35:49 +0400 Subject: [Slackbuilds-users] Package name change: how to proceed In-Reply-To: References: Message-ID: On Sat, 2 Feb 2019, 20:46 Willy Sudiarto Raharjo > I maintain two packages one named obnc and the other obnc-libstd. The > > first is an Oberon compiler and basic library and the second is a > > library for it with extra functionality. The author of the compiler has > > decided to rename second from obnc-libstd to obnc-libext. > > > > How should I proceed? Should I make a new SlackBuild named obnc-libext > > and request the removal of obnc-libstd? > > You can keep the same name if you like or submit a new name and leave a > comment section to remove the old name. > > > Additionally, I wanted to ask which is the correct way to proceed when > > using the mirror of Slackbuilds on github > > (https://github.com/willysr/slackbuilds). Is the correct way fork that > > repository, make changes and then do a pull request? Is this better > > (easier) for the team maintaing Slackbuilds.org than submitting the > tar.gz? > > It's better to send PR/MR through this repositories: > > https://github.com/SlackBuildsOrg/slackbuilds/ > https://gitlab.com/SlackBuilds.org/slackbuilds/ > > Both submission and PR/MR works fine with us > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ Thanks so much for the update Cheers Pritvi > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchmelik at gmail.com Sun Feb 3 09:08:42 2019 From: dchmelik at gmail.com (David Melik) Date: Sun, 3 Feb 2019 01:08:42 -0800 Subject: [Slackbuilds-users] Can't build nvidia-kernel-* with kernel 4.4.172 Message-ID: <941e33b1-0e5a-da4e-0370-a0771db3ca30@gmail.com> Someone couldn't build nvidia-kernel-410.78 with with kernel 4.4.172.? I couldn't build nvidia-driver390, getting what looked like the exact same error.? I'd guess it's a problem with all the nvidia SlackBuilds. From willysr at slackbuilds.org Sun Feb 3 14:36:34 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 Feb 2019 21:36:34 +0700 Subject: [Slackbuilds-users] Can't build nvidia-kernel-* with kernel 4.4.172 In-Reply-To: <941e33b1-0e5a-da4e-0370-a0771db3ca30@gmail.com> References: <941e33b1-0e5a-da4e-0370-a0771db3ca30@gmail.com> Message-ID: <9acdc27a-2bec-8156-ae3f-61912274739f@slackbuilds.org> > Someone couldn't build nvidia-kernel-410.78 with with kernel 4.4.172.? I > couldn't build nvidia-driver390, getting what looked like the exact same > error.? I'd guess it's a problem with all the nvidia SlackBuilds. Since the changes applied to kernels, everything that build kernel modules using the API will be affected -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Feb 3 17:18:04 2019 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 3 Feb 2019 09:18:04 -0800 Subject: [Slackbuilds-users] Can't build nvidia-kernel-410.78 with kernel 4.4.172 In-Reply-To: <11803edd-66fb-012c-c77a-cd8c1897520f@slackbuilds.org> References: <5332929f-da50-49a5-266c-e274c18efa94@o2.pl> <11803edd-66fb-012c-c77a-cd8c1897520f@slackbuilds.org> Message-ID: On 2/1/19 4:40 PM, Willy Sudiarto Raharjo wrote: >> Has anyone tried to build the NVIDIA proprietary kernel module for the >> most recent kernel (4.4.172) on Slackware-14.2? I'm getting the >> following error: > > The maintainer is aware of this issue and will soon fix it. > Meanwhile, you can try to look over this thread on LQ > > https://www.linuxquestions.org/questions/slackware-14/virtualbox-fails-to-build-drivers-for-kernel-4-4-172-a-4175647407/ > > I'm playing catch-up after a week in the UK for my corporate overlord. As soon as I recover from jet lag (getting too damn old for 10+ hr flights), I'll update my VMs and have a look. Nvidia also has a newer version as well that fixes kernel compile issues: Version: 410.93 Release Date: 2019.1.3 This long-lived-branch now includes a number of kernel compile fixes from the short-lived-branch. The legacy versions my be another issue. I have older NVidia GPUs, but nothing to stick them into to test. At this point, if you need nvidia-legacy you must NOT upgrade your kernel. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: From geno.bob at gmail.com Sun Feb 3 06:41:29 2019 From: geno.bob at gmail.com (Geno Bob) Date: Sat, 2 Feb 2019 22:41:29 -0800 Subject: [Slackbuilds-users] ZoneMinder build fails if ffmpeg is not installed In-Reply-To: References: <74b5c2e4-94be-8047-1c44-0dad1c5e3af6@slackbuilds.org> Message-ID: Wow, I don't check my email for a few days, and everything falls apart. Daniel, thank you very much for taking the time to create all of these patches, as well as actually investigate the cause of your issue! There are definitely a lot of changes moving up to the latest version. In my test environment, everything seemed to be functioning properly, but obviously my environment must be slightly different from yours. I will build a fresh slackware install and verify everything on my end. Again, thank you for everything! On Mon, Jan 28, 2019 at 6:45 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Here are three patches. The first one you should be able to apply to > > ZoneMinder in the SBo git. The second two are patches executed by the > > SlackBuild. fix_video_file_format.patch is the one I mentioned > > previously that was needed on my system for ZoneMinder to encode mp4 > > videos for events. fix_zone_area_calc.patch applies upstream commits > > 4937a686 and 4da95369. I also added ffmpeg, libmp4v2, and x264 as > > dependencies and noted php-apcu as an optional dependency. Hopefully > > the maintainer will also weigh in on these changes. > > I think you cover all of those changes in the first patch :) > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sun Feb 3 22:07:05 2019 From: 1.41421 at gmail.com (JCA) Date: Sun, 3 Feb 2019 15:07:05 -0700 Subject: [Slackbuilds-users] ReText still broken? Message-ID: It would seem that the missing python-markdown-math dependency has been sorted out, as ReText now launches without a problem. However, when trying to do a live preview of a document, it complains: Could not parse file contents, check if you have the necessary module installed! That "necessary module" link takes one to https://github.com/Python-Markdown/markdown. This would seem to correspond to the Slackbuilds Markdown package - which is installed in my system. -------------- next part -------------- An HTML attachment was scrubbed... URL: From psychi2009 at gmail.com Tue Feb 5 13:17:26 2019 From: psychi2009 at gmail.com (psychi) Date: Tue, 5 Feb 2019 21:17:26 +0800 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: Message-ID: Hi JCA, When it comes to 'module' in Python-Markdown it may mean the extensions inside it. e.g. https://python-markdown.github.io/extensions/ I have no problems on 'live preview'. My extensions installed are: toc, meta, codehilite. BTW, what's the type of your document is? By default it supports markdown, while it needs other python modules ( python-docutils ) if you want it to support reStructuredText language. Details is on their Github repo: https://github.com/retext-project/retext Cheers, happy hacking. MDrights On Mon, 4 Feb 2019 at 22:32, JCA <1.41421 at gmail.com> wrote: > It would seem that the missing python-markdown-math dependency has been > sorted out, as ReText now launches without a problem. However, when trying > to do a live preview of a document, it complains: > > Could not parse file contents, check if you have the necessary module > installed! > > That "necessary module" link takes one to > https://github.com/Python-Markdown/markdown. This would seem to > correspond to the Slackbuilds Markdown package - which is installed in my > system. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- -- *[PGP key]* 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 - If I did not reply to you, please find another email address of mine. Cheers. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Tue Feb 5 15:22:05 2019 From: didier at slint.fr (Didier Spaier) Date: Tue, 5 Feb 2019 16:22:05 +0100 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: Message-ID: Hello, On 05/02/2019 14:17, psychi wrote: > Hi JCA, > > When it comes to 'module' in Python-Markdown > > it may mean the extensions inside it. e.g. > https://python-markdown.github.io/extensions/ > > I have no problems on 'live preview'. My extensions installed are: toc, > meta, codehilite. > > BTW, what's the type of your document is? By default it supports markdown, > while it needs other python modules ( python-docutils > ) if you want it to support > reStructuredText language. Details is on their Github repo: > https://github.com/retext-project/retext > > Cheers, happy hacking. > MDrights > > On Mon, 4 Feb 2019 at 22:32, JCA <1.41421 at gmail.com> wrote: > >> It would seem that the missing python-markdown-math dependency has been >> sorted out, as ReText now launches without a problem. However, when trying >> to do a live preview of a document, it complains: >> >> Could not parse file contents, check if you have the necessary module >> installed! >> >> That "necessary module" link takes one to >> https://github.com/Python-Markdown/markdown. This would seem to >> correspond to the Slackbuilds Markdown package - which is installed in my >> system. FWIW, geany does syntax highlighting for both Markdown and reStruturesText, as well as many others document types. Best, Didier From 1.41421 at gmail.com Tue Feb 5 16:06:53 2019 From: 1.41421 at gmail.com (JCA) Date: Tue, 5 Feb 2019 09:06:53 -0700 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: Message-ID: I just installed ReText as instructed in Slackbuilds, by means of sbopkg - which implies, I believe, that all the required software is built and installed as a consequence. I don't know what Python-Markdown extensions I have, if any. As for the document, I have tried with number of different *.md files from several different sources. The result, however, is always the same, as I described. In fact, it is the same thing for the following, very simple .md file: ## Some Title ### Prerequisites We are currently building Go executables using Golang version 1.11. 1. install the Go package for your distro 1. configure your go environment * GOBIN * GOPATH 1. run 'go get github.com/tools/godep' The 'godep' tool manages Go library build dependencies. The dependencies are documented elsewhere. I am obviously missing something here, but I am at a loss as to what that may be. On Tue, Feb 5, 2019 at 6:17 AM psychi wrote: > Hi JCA, > > When it comes to 'module' in Python-Markdown > > it may mean the extensions inside it. e.g. > https://python-markdown.github.io/extensions/ > > I have no problems on 'live preview'. My extensions installed are: toc, > meta, codehilite. > > BTW, what's the type of your document is? By default it supports markdown, > while it needs other python modules ( python-docutils > ) if you want it to support > reStructuredText language. Details is on their Github repo: > https://github.com/retext-project/retext > > Cheers, happy hacking. > MDrights > > On Mon, 4 Feb 2019 at 22:32, JCA <1.41421 at gmail.com> wrote: > >> It would seem that the missing python-markdown-math dependency has been >> sorted out, as ReText now launches without a problem. However, when trying >> to do a live preview of a document, it complains: >> >> Could not parse file contents, check if you have the necessary module >> installed! >> >> That "necessary module" link takes one to >> https://github.com/Python-Markdown/markdown. This would seem to >> correspond to the Slackbuilds Markdown package - which is installed in my >> system. >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > > -- > -- > *[PGP key]* > 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 > > - If I did not reply to you, please find another email address of mine. > > Cheers. > -- > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at tty1.uk Tue Feb 5 18:36:21 2019 From: dave at tty1.uk (Dave Woodfall) Date: Tue, 5 Feb 2019 18:36:21 +0000 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: Message-ID: <20190205183621.GH14372@blackholeuniverse.ru> On Tuesday 5 February 2019 09:06, JCA <1.41421 at gmail.com> put forth the proposition: > I just installed ReText as instructed in Slackbuilds, by means of sbopkg - > which implies, I believe, that all the required software is built and > installed as a consequence. Only if you make a queue (sqf) file first with sqg. Sbopkg doesn't build deps automatically. I don't know what Python-Markdown extensions I > have, if any. As for the document, I have tried with number of different > *.md files from several different sources. The result, however, is always > the same, as I described. In fact, it is the same thing for the following, > very simple .md file: > > ## Some Title > ### Prerequisites > > We are currently building Go executables using Golang version 1.11. > > 1. install the Go package for your distro > 1. configure your go environment > * GOBIN > * GOPATH > 1. run 'go get github.com/tools/godep' > > The 'godep' tool manages Go library build dependencies. The dependencies > are documented elsewhere. > > I am obviously missing something here, but I am at a loss as to what that > may be. > > > On Tue, Feb 5, 2019 at 6:17 AM psychi wrote: > > > Hi JCA, > > > > When it comes to 'module' in Python-Markdown > > > > it may mean the extensions inside it. e.g. > > https://python-markdown.github.io/extensions/ > > > > I have no problems on 'live preview'. My extensions installed are: toc, > > meta, codehilite. > > > > BTW, what's the type of your document is? By default it supports markdown, > > while it needs other python modules ( python-docutils > > ) if you want it to support > > reStructuredText language. Details is on their Github repo: > > https://github.com/retext-project/retext > > > > Cheers, happy hacking. > > MDrights > > > > On Mon, 4 Feb 2019 at 22:32, JCA <1.41421 at gmail.com> wrote: > > > >> It would seem that the missing python-markdown-math dependency has been > >> sorted out, as ReText now launches without a problem. However, when trying > >> to do a live preview of a document, it complains: > >> > >> Could not parse file contents, check if you have the necessary module > >> installed! > >> > >> That "necessary module" link takes one to > >> https://github.com/Python-Markdown/markdown. This would seem to > >> correspond to the Slackbuilds Markdown package - which is installed in my > >> system. > >> > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > >> FAQ - https://slackbuilds.org/faq/ > >> > >> > > > > -- > > -- > > *[PGP key]* > > 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 > > > > - If I did not reply to you, please find another email address of mine. > > > > Cheers. > > -- -- Documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing. -- Dick Brandon -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From willysr at slackbuilds.org Tue Feb 5 18:42:33 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 6 Feb 2019 01:42:33 +0700 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: <20190205183621.GH14372@blackholeuniverse.ru> References: <20190205183621.GH14372@blackholeuniverse.ru> Message-ID: > Only if you make a queue (sqf) file first with sqg. Sbopkg doesn't > build deps automatically. You can use sqg -a to generate all queues or sqg -p for specific package (a lot faster too) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Wed Feb 6 15:46:56 2019 From: dpross1100 at msn.com (Daniel Prosser) Date: Wed, 6 Feb 2019 15:46:56 +0000 Subject: [Slackbuilds-users] MD5sum wrong for kodi Message-ID: Hi, I'm not sure if the upstream source has changed, but this is the md5sum I get for kodi: # md5sum xbmc-17.6-Krypton.tar.gz 17a0aaf77d641a2cd52c8728bddaf898 xbmc-17.6-Krypton.tar.gz The .info file has a64c2fc56ddc41b9b0dded55eaabf170 Dan From dpross1100 at msn.com Wed Feb 6 15:53:39 2019 From: dpross1100 at msn.com (Daniel Prosser) Date: Wed, 6 Feb 2019 15:53:39 +0000 Subject: [Slackbuilds-users] MD5sum wrong for kodi In-Reply-To: References: Message-ID: Actually, you can ignore that last email. Seems I just had a bad download. Sorry for the noise. Dan On Wed, Feb 06, 2019 at 03:46:56PM +0000, Daniel Prosser wrote: > Hi, > > I'm not sure if the upstream source has changed, but this is the md5sum > I get for kodi: > > # md5sum xbmc-17.6-Krypton.tar.gz > 17a0aaf77d641a2cd52c8728bddaf898 xbmc-17.6-Krypton.tar.gz > > The .info file has > a64c2fc56ddc41b9b0dded55eaabf170 > > Dan > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From 1.41421 at gmail.com Tue Feb 5 19:39:10 2019 From: 1.41421 at gmail.com (JCA) Date: Tue, 5 Feb 2019 12:39:10 -0700 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: <20190205183621.GH14372@blackholeuniverse.ru> References: <20190205183621.GH14372@blackholeuniverse.ru> Message-ID: Right. That's exactly what I did. The contents of the ReText queue file are: python3 python-markdown-math Markdown pyudev python-evdev graphviz ninja meson libwacom libinput libxkbcommon qt5 qt5-webkit python3-sip python3-PyQt5 Markups ReText On Tue, Feb 5, 2019 at 11:36 AM Dave Woodfall wrote: > On Tuesday 5 February 2019 09:06, > JCA <1.41421 at gmail.com> put forth the proposition: > > I just installed ReText as instructed in Slackbuilds, by means of sbopkg > - > > which implies, I believe, that all the required software is built and > > installed as a consequence. > > Only if you make a queue (sqf) file first with sqg. Sbopkg doesn't > build deps automatically. > > I don't know what Python-Markdown extensions I > > have, if any. As for the document, I have tried with number of different > > *.md files from several different sources. The result, however, is always > > the same, as I described. In fact, it is the same thing for the > following, > > very simple .md file: > > > > ## Some Title > > ### Prerequisites > > > > We are currently building Go executables using Golang version 1.11. > > > > 1. install the Go package for your distro > > 1. configure your go environment > > * GOBIN > > * GOPATH > > 1. run 'go get github.com/tools/godep' > > > > The 'godep' tool manages Go library build dependencies. The > dependencies > > are documented elsewhere. > > > > I am obviously missing something here, but I am at a loss as to what that > > may be. > > > > > > On Tue, Feb 5, 2019 at 6:17 AM psychi wrote: > > > > > Hi JCA, > > > > > > When it comes to 'module' in Python-Markdown > > > > > > it may mean the extensions inside it. e.g. > > > https://python-markdown.github.io/extensions/ > > > > > > I have no problems on 'live preview'. My extensions installed are: toc, > > > meta, codehilite. > > > > > > BTW, what's the type of your document is? By default it supports > markdown, > > > while it needs other python modules ( python-docutils > > > ) if you want it to support > > > reStructuredText language. Details is on their Github repo: > > > https://github.com/retext-project/retext > > > > > > Cheers, happy hacking. > > > MDrights > > > > > > On Mon, 4 Feb 2019 at 22:32, JCA <1.41421 at gmail.com> wrote: > > > > > >> It would seem that the missing python-markdown-math dependency has > been > > >> sorted out, as ReText now launches without a problem. However, when > trying > > >> to do a live preview of a document, it complains: > > >> > > >> Could not parse file contents, check if you have the necessary module > > >> installed! > > >> > > >> That "necessary module" link takes one to > > >> https://github.com/Python-Markdown/markdown. This would seem to > > >> correspond to the Slackbuilds Markdown package - which is installed > in my > > >> system. > > >> > > >> _______________________________________________ > > >> SlackBuilds-users mailing list > > >> SlackBuilds-users at slackbuilds.org > > >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > >> FAQ - https://slackbuilds.org/faq/ > > >> > > >> > > > > > > -- > > > -- > > > *[PGP key]* > > > 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 > > > > > > - If I did not reply to you, please find another email address of mine. > > > > > > Cheers. > > > -- > > -- > > Documentation is like sex: when it is good, it is very, very good; and > when it is bad, it is better than nothing. > -- Dick Brandon > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Wed Feb 6 19:38:13 2019 From: 1.41421 at gmail.com (JCA) Date: Wed, 6 Feb 2019 12:38:13 -0700 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: <20190205183621.GH14372@blackholeuniverse.ru> Message-ID: I decided to try this in an all-fresh 14.2 installation. I therefore created a VM with 14.2, I upgraded every package contained in the most recent (as of yesterday) official patches for 14.2, and then proceeded to build ReText with sbopkg using the most recent queue file for ReText. This took quite a while, for both qt5 and qt5-webkit take a very long time to build. Anyway, the resulting ReText still behaves the way I have described - the live preview feature does not work. On Tue, Feb 5, 2019 at 12:39 PM JCA <1.41421 at gmail.com> wrote: > Right. That's exactly what I did. The contents of the ReText queue file > are: > > python3 > python-markdown-math > Markdown > pyudev > python-evdev > graphviz > ninja > meson > libwacom > libinput > libxkbcommon > qt5 > qt5-webkit > python3-sip > python3-PyQt5 > Markups > ReText > > > On Tue, Feb 5, 2019 at 11:36 AM Dave Woodfall wrote: > >> On Tuesday 5 February 2019 09:06, >> JCA <1.41421 at gmail.com> put forth the proposition: >> > I just installed ReText as instructed in Slackbuilds, by means of >> sbopkg - >> > which implies, I believe, that all the required software is built and >> > installed as a consequence. >> >> Only if you make a queue (sqf) file first with sqg. Sbopkg doesn't >> build deps automatically. >> >> I don't know what Python-Markdown extensions I >> > have, if any. As for the document, I have tried with number of different >> > *.md files from several different sources. The result, however, is >> always >> > the same, as I described. In fact, it is the same thing for the >> following, >> > very simple .md file: >> > >> > ## Some Title >> > ### Prerequisites >> > >> > We are currently building Go executables using Golang version 1.11. >> > >> > 1. install the Go package for your distro >> > 1. configure your go environment >> > * GOBIN >> > * GOPATH >> > 1. run 'go get github.com/tools/godep' >> > >> > The 'godep' tool manages Go library build dependencies. The >> dependencies >> > are documented elsewhere. >> > >> > I am obviously missing something here, but I am at a loss as to what >> that >> > may be. >> > >> > >> > On Tue, Feb 5, 2019 at 6:17 AM psychi wrote: >> > >> > > Hi JCA, >> > > >> > > When it comes to 'module' in Python-Markdown >> > > >> > > it may mean the extensions inside it. e.g. >> > > https://python-markdown.github.io/extensions/ >> > > >> > > I have no problems on 'live preview'. My extensions installed are: >> toc, >> > > meta, codehilite. >> > > >> > > BTW, what's the type of your document is? By default it supports >> markdown, >> > > while it needs other python modules ( python-docutils >> > > ) if you want it to support >> > > reStructuredText language. Details is on their Github repo: >> > > https://github.com/retext-project/retext >> > > >> > > Cheers, happy hacking. >> > > MDrights >> > > >> > > On Mon, 4 Feb 2019 at 22:32, JCA <1.41421 at gmail.com> wrote: >> > > >> > >> It would seem that the missing python-markdown-math dependency has >> been >> > >> sorted out, as ReText now launches without a problem. However, when >> trying >> > >> to do a live preview of a document, it complains: >> > >> >> > >> Could not parse file contents, check if you have the necessary module >> > >> installed! >> > >> >> > >> That "necessary module" link takes one to >> > >> https://github.com/Python-Markdown/markdown. This would seem to >> > >> correspond to the Slackbuilds Markdown package - which is installed >> in my >> > >> system. >> > >> >> > >> _______________________________________________ >> > >> SlackBuilds-users mailing list >> > >> SlackBuilds-users at slackbuilds.org >> > >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> > >> Archives - >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> > >> FAQ - https://slackbuilds.org/faq/ >> > >> >> > >> >> > > >> > > -- >> > > -- >> > > *[PGP key]* >> > > 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 >> > > >> > > - If I did not reply to you, please find another email address of >> mine. >> > > >> > > Cheers. >> > > -- >> >> -- >> >> Documentation is like sex: when it is good, it is very, very good; and >> when it is bad, it is better than nothing. >> -- Dick Brandon >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Wed Feb 6 22:46:59 2019 From: chris.willing at linux.com (Christoph Willing) Date: Thu, 7 Feb 2019 08:46:59 +1000 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: <20190205183621.GH14372@blackholeuniverse.ru> Message-ID: <2a40cdcc-c4e0-0885-3820-2c8cbe3c78c9@linux.com> On 7/2/19 5:38 am, JCA wrote: > I decided to try this in an all-fresh 14.2 installation. I therefore > created a VM with 14.2, I upgraded every package contained in the most > recent (as of yesterday) official patches for 14.2, and then proceeded > to build ReText with sbopkg using the most recent queue file for ReText. > This took quite a while, for both qt5 and qt5-webkit take a very long > time to build. Anyway, the resulting ReText still behaves the way I have > described - the live preview feature does not work. > I saw the same problem. It is due to python/Markdown not having python3 support. I fixed the problem locally by adding (just after the existing setup.py command): # Python 3 support. if $(python3 -c 'import sys' 2>/dev/null); then python3 setup.py install --root=$PKG fi (as copied from python/Markups/Markups.SlackBuild) Rebuilding & reinstalling the new Markdown with python3 support enabled the Preview functionality to work as expected. chris From 1.41421 at gmail.com Wed Feb 6 23:12:38 2019 From: 1.41421 at gmail.com (JCA) Date: Wed, 6 Feb 2019 16:12:38 -0700 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: <2a40cdcc-c4e0-0885-3820-2c8cbe3c78c9@linux.com> References: <20190205183621.GH14372@blackholeuniverse.ru> <2a40cdcc-c4e0-0885-3820-2c8cbe3c78c9@linux.com> Message-ID: I have just tested that, and it works all right. Thanks for fixing this - it was driving me up the wall. On Wed, Feb 6, 2019 at 3:47 PM Christoph Willing wrote: > On 7/2/19 5:38 am, JCA wrote: > > I decided to try this in an all-fresh 14.2 installation. I therefore > > created a VM with 14.2, I upgraded every package contained in the most > > recent (as of yesterday) official patches for 14.2, and then proceeded > > to build ReText with sbopkg using the most recent queue file for ReText. > > This took quite a while, for both qt5 and qt5-webkit take a very long > > time to build. Anyway, the resulting ReText still behaves the way I have > > described - the live preview feature does not work. > > > > I saw the same problem. It is due to python/Markdown not having python3 > support. I fixed the problem locally by adding (just after the existing > setup.py command): > > # Python 3 support. > if $(python3 -c 'import sys' 2>/dev/null); then > python3 setup.py install --root=$PKG > fi > > (as copied from python/Markups/Markups.SlackBuild) > > Rebuilding & reinstalling the new Markdown with python3 support enabled > the Preview functionality to work as expected. > > chris > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From psychi2009 at gmail.com Thu Feb 7 14:31:29 2019 From: psychi2009 at gmail.com (psychi) Date: Thu, 7 Feb 2019 22:31:29 +0800 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: <20190205183621.GH14372@blackholeuniverse.ru> <2a40cdcc-c4e0-0885-3820-2c8cbe3c78c9@linux.com> Message-ID: Thanks Chris. So we'd like to ping slackbuilds at mareichelt.de who is the maintainer of the Markdown SlackBuild. :) Cheers On Thu, 7 Feb 2019 at 12:56, JCA <1.41421 at gmail.com> wrote: > I have just tested that, and it works all right. Thanks for fixing this - > it was driving me up the wall. > > On Wed, Feb 6, 2019 at 3:47 PM Christoph Willing > wrote: > >> On 7/2/19 5:38 am, JCA wrote: >> > I decided to try this in an all-fresh 14.2 installation. I therefore >> > created a VM with 14.2, I upgraded every package contained in the most >> > recent (as of yesterday) official patches for 14.2, and then proceeded >> > to build ReText with sbopkg using the most recent queue file for ReText. >> > This took quite a while, for both qt5 and qt5-webkit take a very long >> > time to build. Anyway, the resulting ReText still behaves the way I have >> > described - the live preview feature does not work. >> > >> >> I saw the same problem. It is due to python/Markdown not having python3 >> support. I fixed the problem locally by adding (just after the existing >> setup.py command): >> >> # Python 3 support. >> if $(python3 -c 'import sys' 2>/dev/null); then >> python3 setup.py install --root=$PKG >> fi >> >> (as copied from python/Markups/Markups.SlackBuild) >> >> Rebuilding & reinstalling the new Markdown with python3 support enabled >> the Preview functionality to work as expected. >> >> chris >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- -- *[PGP key]* 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 - If I did not reply to you, please find another email address of mine. Cheers. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Thu Feb 7 21:11:29 2019 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 8 Feb 2019 07:11:29 +1000 Subject: [Slackbuilds-users] ReText still broken? In-Reply-To: References: <20190205183621.GH14372@blackholeuniverse.ru> <2a40cdcc-c4e0-0885-3820-2c8cbe3c78c9@linux.com> Message-ID: On 8/2/19 12:31 am, psychi wrote: > Thanks Chris. > > So we'd like to ping slackbuilds at mareichelt.de > who is the maintainer of the Markdown > SlackBuild. :) > I noticed Willy already added the python3 stuff in his branch for next SBo release this weekend. chris From willysr at slackbuilds.org Sat Feb 9 03:44:38 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Feb 2019 10:44:38 +0700 Subject: [Slackbuilds-users] Updates - 20190209.1 Message-ID: <454ae8d9-93ab-1e27-aaa1-a2f34af87b5c@slackbuilds.org> Hi all as promised, we deliver the fixes for nvidia and virtualbox issue on this batch of updates along with other changes that comes during this week. We also updated libreoffice (both source and binary) scripts to 6.2.0, the latest major version. Have a nice weekend :) Sat Feb 9 03:30:52 UTC 2019 academic/Mnemosyne: Updated for version 2.6.1. academic/ngspice: Update script. academic/scipy3: Updated for version 1.1.0. academic/scipy: Update script. academic/sympy: Updated for version 1.3. audio/gusersoundfont: Added (A sound font). development/Sphinx: Updated for version 1.8.4. development/composer: Updated for version 1.8.3 development/cutter: Added (GUI for radare2). development/dwarf: Updated for version 20190110 development/git-cola: Updated for version 3.3. development/hhvm: Updated for version 3.30.3 development/hub: Updated for version 2.8.4. development/hugo: Updated for version 0.54.0. development/obnc-libext: Added (Extended Library for OBNC). development/obnc: Updated for version 0.14.2. development/pycharm: Updated for version 2018.3.4. development/python3-matplotlib: Updated for version 2.2.3. development/pyvim: Updated for version 2.0.24. development/tanya: Updated for version 0.15.0 development/universal-ctags: Updated for version 28a8c70 games/RetroArch: Updated for version 1.7.6. games/crrcsim: Added (model airplane flight simulator). gis/rasterio: Updated for version 1.0.18. graphics/abcm2ps: Added (converter). graphics/advancecomp: Updated for version 2.1. graphics/pygraphviz: Updated for version 1.5. graphicss/sxiv: Updated for version 25. ham/cqrlog: Updated for version 2.3.0. libraries/SOPE: Updated for version 4.0.5. libraries/libcdr: Updated for version 0.1.5. libraries/libcmis: Updated for version 0.5.2. libraries/libcpuid: Updated for version 0.4.1. libraries/libetonyek: Updated for version 0.1.9. libraries/libqxp: Updated for version 0.0.2. libraries/live555: Updated for version 2019.02.03 libraries/obnc-libstd: Removed (Replaced with obnc-libext). misc/mosquitto: Updated for version 1.5.6 misc/with-readline: Added (run non readline apps in readline). multimedia/abcMIDI: Added (MIDI Converter). multimedia/devedeng: Updated for version 4.13.0. multimedia/ffmpeg: Update README. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 71.0. network/brave-browser: Updated for version 0.59.34. network/libnfsidmap: Added (NFS idmapping library). network/nbd: Updated for version 3.19 network/signal-desktop: Updated for version 1.21.0. network/telegram: Updated for version 1.5.11. network/vivaldi: Updated for version 2.3.1440.41. network/waterfox: Updated for version 56.2.7.1. network/yle-dl: Updated for version 20190203. network/you-get: Updated for version 0.4.1205. network/youtube-dl: Updated for version 2019.01.30.1. office/LibreOffice: Updated for version 6.2.0.3 office/SOGo: Updated for version 4.0.5. office/libreoffice-helppack: Updated for version 6.2.0. office/libreoffice-langpack: Updated for version 6.2.0. office/libreoffice: Updated for version 6.2.0. office/pdfstudio2018: Updated for version 18.3.0. python/Markdown: Enable Python3 support. python/parso: Updated for version 0.3.3. python/pycodestyle: Updated for version 2.5.0. python/pytest: Downgraded to version 3.8.2. python/python-distro: Updated for version 1.4.0. python/python-fonttools: Updated for version 3.37.3. python/python3-parso: Updated for version 0.3.3. python/typed_ast: Updated for version 1.3.1. ruby/rubygem-jaro_winkler: Updated for version 1.5.2. system/Iosevka: Updated for version 2.1.0. system/ZoneMinder: Update script. system/duplicity: Updated for version 0.7.18.2 + new maintainer. system/firejail: Updated for version 0.9.58. system/fwupd: Updated for version 1.2.4. system/kitchen-sync: Updated for version 1.11. system/ksh-openbsd: Updated for version 20190127 + new maintainer. system/loksh: Added doinst.sh. system/nvidia-driver: Updated for version 418.30. system/nvidia-kernel: Updated for version 418.30. system/phoronix-test-suite: Updated for version 8.6.0. system/posh: Added doinst.sh. system/qtfm: Updated for version 6.1.6. system/virtualbox-kernel-addons: Fix building against newer kernels. system/virtualbox-kernel: Fix building against kernel >= 4.4.168. system/worker: Updated for version 3.15.4. system/yash: Added doinst.sh. system/zfs-auto-snapshot: Added (ZFS Snapshot). +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From sbolokanov at abv.bg Sat Feb 9 12:07:43 2019 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGK4oCT0KHQtdCy0LDRgA==?= =?utf-8?B?0Yog0JHQvtC70L7QutCw0L3QvtCy0Yo=?=) Date: Sat, 9 Feb 2019 14:07:43 +0200 (EET) Subject: [Slackbuilds-users] rhash update Message-ID: <1001526670.440393.1549714063435@nm51.abv.bg> Update for rhash attached. -- ?. ?. ?????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-system-rhash-Updated-for-version-1.3.8.patch Type: application/octet-stream Size: 1520 bytes Desc: not available URL: From alleytrotter at gmail.com Sat Feb 9 15:54:24 2019 From: alleytrotter at gmail.com (John Yost) Date: Sat, 9 Feb 2019 10:54:24 -0500 Subject: [Slackbuilds-users] LibreOffice Fails Message-ID: -- tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done] Error 1 make[1]: *** Waiting for unfinished jobs.... /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done] Error 1 /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done] Error 1 /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done] Error 1 Makefile:286: recipe for target 'build' failed make: *** [build] Error 2 ./libreoffice.SlackBuild and / or JAVA=no ./libreoffice.SlackBuild John David Yost AlleyTrotter pub 2048D/F3BDEB55 2014-05-23 [expires: Never] -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x2C7AF6BEF3BDEB55.asc Type: application/pgp-keys Size: 2294 bytes Desc: not available URL: From mickski56 at hotmail.com Sat Feb 9 15:59:07 2019 From: mickski56 at hotmail.com (mickski 56) Date: Sat, 9 Feb 2019 15:59:07 +0000 Subject: [Slackbuilds-users] LibreOffice Fails In-Reply-To: References: Message-ID: I Saw this error too. Solved by removing previous libreoffice package hth > -- tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done' > failed make[1]: *** > [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done] Error 1 > make[1]: *** Waiting for unfinished jobs.... > /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done' > failed > make[1]: *** > [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done] Error > 1 /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done' > failed make[1]: *** > [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done] Error 1 > /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done' > failed make[1]: *** > [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done] Error 1 > Makefile:286: recipe for target 'build' failed > make: *** [build] Error 2 > > ./libreoffice.SlackBuild > and / or > JAVA=no ./libreoffice.SlackBuild > > > John David Yost > AlleyTrotter > pub 2048D/F3BDEB55 2014-05-23 [expires: Never] > From fernando.lopezjr at gmail.com Sat Feb 9 17:13:19 2019 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 9 Feb 2019 10:13:19 -0700 Subject: [Slackbuilds-users] libpyspatialite freexl needed? Message-ID: is freexl needed dep for libpyspatialite? -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at jaxartes.net Sat Feb 9 17:28:32 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 09 Feb 2019 09:28:32 -0800 Subject: [Slackbuilds-users] libpyspatialite freexl needed? In-Reply-To: References: Message-ID: <1902047.cBl9bSMxv1@wintermute.sprawl.net> On Saturday, 9 February 2019 09:13:19 PST Fernando Lopez wrote: > is freexl needed dep for libpyspatialite? Indirectly, yes. pyspatialite <- libspatialite <- freexl. Ben From alleytrotter at gmail.com Sat Feb 9 18:10:28 2019 From: alleytrotter at gmail.com (John Yost) Date: Sat, 9 Feb 2019 13:10:28 -0500 Subject: [Slackbuilds-users] LibreOffice Fails In-Reply-To: References: Message-ID: On 2/9/19 10:59 AM, mickski 56 wrote: > I Saw this error too. Solved by removing previous libreoffice package > hth > >> -- tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done' >> failed make[1]: *** >> [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done] Error 1 >> make[1]: *** Waiting for unfinished jobs.... >> /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done' >> failed >> make[1]: *** >> [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done] Error >> 1 /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done' >> failed make[1]: *** >> [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done] Error 1 >> /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done' >> failed make[1]: *** >> [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done] Error 1 >> Makefile:286: recipe for target 'build' failed >> make: *** [build] Error 2 >> >> ./libreoffice.SlackBuild >> and / or >> JAVA=no ./libreoffice.SlackBuild >> >> > removepkg libreoffice ./LibreOffice.SlackBuild returns the following: """Bootstrap exception 'component context fails to supply service com.sun.star.ucb.UniversalContentBroker of type com.sun.star.ucb.XUniversalContentBroker' /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done] Error 1 make[1]: *** Waiting for unfinished jobs.... Bootstrap exception 'component context fails to supply service com.sun.star.ucb.UniversalContentBroker of type com.sun.star.ucb.XUniversalContentBroker' /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done] Error 1 Bootstrap exception 'component context fails to supply service com.sun.star.ucb.UniversalContentBroker of type com.sun.star.ucb.XUniversalContentBroker' /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done] Error 1 Bootstrap exception 'component context fails to supply service com.sun.star.ucb.UniversalContentBroker of type com.sun.star.ucb.XUniversalContentBroker' /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done' failed make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done] Error 1 Makefile:286: recipe for target 'build' failed make: *** [build] Error 2 """ John David Yost AlleyTrotter pub 2048D/F3BDEB55 2014-05-23 [expires: Never] -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x2C7AF6BEF3BDEB55.asc Type: application/pgp-keys Size: 2294 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Feb 9 18:12:39 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 10 Feb 2019 01:12:39 +0700 Subject: [Slackbuilds-users] LibreOffice Fails In-Reply-To: References: Message-ID: <449496fe-9650-4998-68a9-e8a8136e7b59@slackbuilds.org> > removepkg libreoffice > > ./LibreOffice.SlackBuild > returns the following: > """Bootstrap exception 'component context fails to supply service > com.sun.star.ucb.UniversalContentBroker of type > com.sun.star.ucb.XUniversalContentBroker' > /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done' failed > make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done] > Error 1 > make[1]: *** Waiting for unfinished jobs.... > Bootstrap exception 'component context fails to supply service > com.sun.star.ucb.UniversalContentBroker of type > com.sun.star.ucb.XUniversalContentBroker' > /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done' failed > make[1]: *** > [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done] Error 1 > Bootstrap exception 'component context fails to supply service > com.sun.star.ucb.UniversalContentBroker of type > com.sun.star.ucb.XUniversalContentBroker' > /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done' > failed > make[1]: *** > [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done] Error 1 > Bootstrap exception 'component context fails to supply service > com.sun.star.ucb.UniversalContentBroker of type > com.sun.star.ucb.XUniversalContentBroker' > /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for > target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done' failed > make[1]: *** > [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done] Error 1 > Makefile:286: recipe for target 'build' failed > make: *** [build] Error 2 > """ Have you tried building with "su -" instead of just "su" ? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From alleytrotter at gmail.com Sat Feb 9 22:25:27 2019 From: alleytrotter at gmail.com (John Yost) Date: Sat, 9 Feb 2019 17:25:27 -0500 Subject: [Slackbuilds-users] LibreOffice Fails In-Reply-To: <449496fe-9650-4998-68a9-e8a8136e7b59@slackbuilds.org> References: <449496fe-9650-4998-68a9-e8a8136e7b59@slackbuilds.org> Message-ID: On 2/9/19 1:12 PM, Willy Sudiarto Raharjo wrote: >> removepkg libreoffice >> >> ./LibreOffice.SlackBuild >> returns the following: >> """Bootstrap exception 'component context fails to supply service >> com.sun.star.ucb.UniversalContentBroker of type >> com.sun.star.ucb.XUniversalContentBroker' >> /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done' failed >> make[1]: *** [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/arrows.done] >> Error 1 >> make[1]: *** Waiting for unfinished jobs.... >> Bootstrap exception 'component context fails to supply service >> com.sun.star.ucb.UniversalContentBroker of type >> com.sun.star.ucb.XUniversalContentBroker' >> /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done' failed >> make[1]: *** >> [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/computers.done] Error 1 >> Bootstrap exception 'component context fails to supply service >> com.sun.star.ucb.UniversalContentBroker of type >> com.sun.star.ucb.XUniversalContentBroker' >> /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done' >> failed >> make[1]: *** >> [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/backgrounds.done] Error 1 >> Bootstrap exception 'component context fails to supply service >> com.sun.star.ucb.UniversalContentBroker of type >> com.sun.star.ucb.XUniversalContentBroker' >> /tmp/SBo/libreoffice-6.2.0.3/solenv/gbuild/Gallery.mk:58: recipe for >> target '/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done' failed >> make[1]: *** >> [/tmp/SBo/libreoffice-6.2.0.3/workdir/Gallery/diagrams.done] Error 1 >> Makefile:286: recipe for target 'build' failed >> make: *** [build] Error 2 >> """ problem was local I did upgrade package reinstall on the $REQUIRES reboot LibreOffice built fine thanks All john From yth at ythogtha.org Sun Feb 10 18:56:07 2019 From: yth at ythogtha.org (Arnaud) Date: Sun, 10 Feb 2019 19:56:07 +0100 Subject: [Slackbuilds-users] LibreOffice Fails In-Reply-To: References: <449496fe-9650-4998-68a9-e8a8136e7b59@slackbuilds.org> Message-ID: <20190210195607.493a2febef95d5a9a4a3e4a4@ythogtha.org> > On 2/9/19 1:12 PM, Willy Sudiarto Raharjo wrote: > > problem was local > I did upgrade package reinstall on the $REQUIRES > reboot > LibreOffice built fine > > thanks All > john Oh, well, you're lucky... Up until the last update I had to make sure previous LibreOffice was actually installed for the new one to build. But today I'm at a loss, it always fails. I've rebuilt all dependencies on a clean and up-to-date VM. I used to not install optional dependencies, all the one that could use internal LibreOffice versions instead, but today I tried building them all. And it always fails at the same place. So, well... I'm still trying ! -- Arnaud From chris.willing at linux.com Sun Feb 10 21:24:48 2019 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 11 Feb 2019 07:24:48 +1000 Subject: [Slackbuilds-users] LibreOffice Fails In-Reply-To: <20190210195607.493a2febef95d5a9a4a3e4a4@ythogtha.org> References: <449496fe-9650-4998-68a9-e8a8136e7b59@slackbuilds.org> <20190210195607.493a2febef95d5a9a4a3e4a4@ythogtha.org> Message-ID: <317cdbe2-c802-8626-798c-8aed6ae8535a@linux.com> On 11/2/19 4:56 am, Arnaud wrote: >> On 2/9/19 1:12 PM, Willy Sudiarto Raharjo wrote: >> >> problem was local >> I did upgrade package reinstall on the $REQUIRES >> reboot >> LibreOffice built fine >> >> thanks All >> john > > Oh, well, you're lucky... > Up until the last update I had to make sure previous LibreOffice was actually > installed for the new one to build. > But today I'm at a loss, it always fails. > I've rebuilt all dependencies on a clean and up-to-date VM. > > I used to not install optional dependencies, all the one that could use internal > LibreOffice versions instead, but today I tried building them all. > > And it always fails at the same place. > I sometimes see this when checking 32bit builds before submission of a new version update. It's reasonably unusual these days after lots of fiddling with (increasing) swap size & memory allocation to the VM. Nevertheless I had a freeze when test building the latest update in a 32bit VM. I just ran the build again and it completed without issue. I've had no problems with 64bit builds for many version updates now (after similar fiddling with swap size and memory allocation). chris From alleytrotter at gmail.com Sun Feb 10 21:58:51 2019 From: alleytrotter at gmail.com (John Yost) Date: Sun, 10 Feb 2019 16:58:51 -0500 Subject: [Slackbuilds-users] LibreOffice Fails In-Reply-To: <20190210195607.493a2febef95d5a9a4a3e4a4@ythogtha.org> References: <449496fe-9650-4998-68a9-e8a8136e7b59@slackbuilds.org> <20190210195607.493a2febef95d5a9a4a3e4a4@ythogtha.org> Message-ID: <65f47515-2539-0974-4f07-f22f7389d84b@gmail.com> On 2/10/19 1:56 PM, Arnaud wrote: >> On 2/9/19 1:12 PM, Willy Sudiarto Raharjo wrote: >> >> problem was local >> I did upgrade package reinstall on the $REQUIRES >> reboot >> LibreOffice built fine >> >> thanks All >> john > > Oh, well, you're lucky... > Up until the last update I had to make sure previous LibreOffice was actually > installed for the new one to build. > But today I'm at a loss, it always fails. > I've rebuilt all dependencies on a clean and up-to-date VM. > > I used to not install optional dependencies, all the one that could use internal > LibreOffice versions instead, but today I tried building them all. > > And it always fails at the same place. > > So, well... > I'm still trying ! > I once had to use a VM fresh and new, but without any updates installed to make it build Might Help? john From duncan_roe at optusnet.com.au Tue Feb 12 00:08:24 2019 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Tue, 12 Feb 2019 11:08:24 +1100 Subject: [Slackbuilds-users] libreoffice 6.2 (RPM's) runtime failure Message-ID: <20190212000824.GA16110@dimstar.local.net> Hi all, I am getting the following error: > 11:01:56$ libreoffice6.2 ~/calendar.ods > /opt/libreoffice6.2/program/soffice.bin: symbol lookup error: /opt/libreoffice6.2/program/libvclplug_gtk3lo.so: undefined symbol: gdk_wayland_display_get_type Fwiw avahi is up to date (avahi-0.6.32) and I'm using Oracle Java(TM) SE Runtime Environment 18.3 (build 10.0.2+13) Cheers ... Duncan. From lists at osh.id.au Tue Feb 12 01:39:38 2019 From: lists at osh.id.au (David O'Shaughnessy) Date: Mon, 11 Feb 2019 20:39:38 -0500 Subject: [Slackbuilds-users] libreoffice 6.2 (RPM's) runtime failure In-Reply-To: <20190212000824.GA16110@dimstar.local.net> References: <20190212000824.GA16110@dimstar.local.net> Message-ID: <4f898514-09d0-42a3-bcbd-c77cfc7156b1@www.fastmail.com> On Mon, 11 Feb 2019, at 4:08 PM, Duncan Roe wrote: > I am getting the following error: > > > 11:01:56$ libreoffice6.2 ~/calendar.ods > > /opt/libreoffice6.2/program/soffice.bin: symbol lookup error: /opt/libreoffice6.2/program/libvclplug_gtk3lo.so: undefined symbol: gdk_wayland_display_get_type > For your environment (~/.bash_profile, etc) you need: export SAL_USE_VCLPLUGIN=gtk Or you can source it from: /etc/profile.d/libreoffice.sh -- Dave From willysr at slackbuilds.org Tue Feb 12 02:21:13 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 12 Feb 2019 09:21:13 +0700 Subject: [Slackbuilds-users] libreoffice 6.2 (RPM's) runtime failure In-Reply-To: <4f898514-09d0-42a3-bcbd-c77cfc7156b1@www.fastmail.com> References: <20190212000824.GA16110@dimstar.local.net> <4f898514-09d0-42a3-bcbd-c77cfc7156b1@www.fastmail.com> Message-ID: <0aee57cc-9e2b-6dba-c57a-c45696460bf4@slackbuilds.org> > For your environment (~/.bash_profile, etc) you need: > export SAL_USE_VCLPLUGIN=gtk > > Or you can source it from: /etc/profile.d/libreoffice.sh or if you reboot, it will be sourced by default, so it should be fine -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Tue Feb 12 16:16:11 2019 From: kingbeowulf at gmail.com (Edward Koenig) Date: Tue, 12 Feb 2019 08:16:11 -0800 Subject: [Slackbuilds-users] Fwd: nvidia-kernel (418.30) slackbuild: wrong link in .info file References: Message-ID: <8C531B6A-6070-4EA8-A459-E014D6B77A2D@gmail.com> Hello admins Looks like a small typo slipped by us in nvidia-kernel.info see below for fix. Thanks. -Ed Begin forwarded message: > From: Joe > Date: February 11, 2019 at 3:23:00 PM PST > To: kingbeowulf at gmail.com > Subject: nvidia-kernel (418.30) slackbuild: wrong link in .info file > > Hello, > an user noticed sbopkg can't download the driver due to wrong link > specified in info file: > https://slackbuilds.org/slackbuilds/14.2/system/nvidia-kernel/nvidia-kernel.info > > The wrong link: > https://download.nvidia.com/XFree86/Linux-x86_64/410.78/NVIDIA-Linux-x86_64-418.30.run > > And the right working one: > https://download.nvidia.com/XFree86/Linux-x86_64/418.30/NVIDIA-Linux-x86_64-418.30.run > > My two cent :) > Thank you for your work Edward! > Good Slack! > Bye! -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Feb 12 16:26:57 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 12 Feb 2019 23:26:57 +0700 Subject: [Slackbuilds-users] Fwd: nvidia-kernel (418.30) slackbuild: wrong link in .info file In-Reply-To: <8C531B6A-6070-4EA8-A459-E014D6B77A2D@gmail.com> References: <8C531B6A-6070-4EA8-A459-E014D6B77A2D@gmail.com> Message-ID: <013f1918-1ba6-e0d8-e6ed-e0fc992f734a@slackbuilds.org> > Looks like a small typo slipped by us in nvidia-kernel.info > see below for fix.? Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From geno.bob at gmail.com Sat Feb 16 23:41:23 2019 From: geno.bob at gmail.com (Geno Bob) Date: Sat, 16 Feb 2019 15:41:23 -0800 Subject: [Slackbuilds-users] ZoneMinder build fails if ffmpeg is not installed In-Reply-To: References: <74b5c2e4-94be-8047-1c44-0dad1c5e3af6@slackbuilds.org> Message-ID: Thank you Willy and Daniel! ffmpeg should have been a required program listing. x264 is not required to build, however I would say that it is a highly recommended "optional" dependency. Thank you Willy for making all the necessary changes/updates, and thank you again Daniel for your time in not only pointing out issues, but also taking the time to troubleshoot, diagnose, and create a solution to the problem! On Mon, Jan 28, 2019 at 6:45 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Here are three patches. The first one you should be able to apply to > > ZoneMinder in the SBo git. The second two are patches executed by the > > SlackBuild. fix_video_file_format.patch is the one I mentioned > > previously that was needed on my system for ZoneMinder to encode mp4 > > videos for events. fix_zone_area_calc.patch applies upstream commits > > 4937a686 and 4da95369. I also added ffmpeg, libmp4v2, and x264 as > > dependencies and noted php-apcu as an optional dependency. Hopefully > > the maintainer will also weigh in on these changes. > > I think you cover all of those changes in the first patch :) > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Feb 17 15:07:12 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Feb 2019 22:07:12 +0700 Subject: [Slackbuilds-users] Updates - 20190217.1 Message-ID: Hi, sorry for the delay for this batch, due to some real life work :) Sun Feb 17 14:57:42 UTC 2019 academic/STAR: Updated for version 2.7.0c. academic/libqalculate: Updated for version 2.9.0 academic/qalculate-gtk: Updated for version 2.9.0 academic/suitesparse: Updated for version 5.4.0 audio/clyrics: Updated for version 0.11. desktop/Zafiro-icons: Updated for version 0.8.7. desktop/awesome-extra: Updated for version 2019021001. desktop/gnome-menus: Updated for version 3.31.90. desktop/py3status: Updated for version 3.16. desktop/simplenote: Updated for version 1.4.1. development/composer: Updated for version 1.8.4 development/d-tools: Updated for version 2.084.1 development/dart: Updated for version 2.1.0. development/dmd: Updated for version 2.084.1 development/idlex: Updated for version 1.18. development/kotlin: Updated for version 1.3.21. development/postman: Updated for version 6.7.3. development/sbcl: Updated for version 1.4.16. development/universal-ctags: Updated for version a4adde1 development/wheel: Updated for version 0.33.0. games/mrboom: Updated for version 4.7. games/stone_soup: Updated for version 0.23.0. gis/pyshp: Updated for version 2.1.0. gis/qmapshack: Updated for version 1.12.3. graphics/CairoSVG: Updated for version 2.3.0. graphics/PyMOL: Updated for version 2.2.0. graphics/pyformex: Updated for version 1.0.5. graphics/tuxpaint: Added tuxpaint-config. libraries/SFML: Updated for version 2.5.1. libraries/VTK: Updated foe version 8.2.0 libraries/cffi: Updated for version 1.11.5. libraries/libbluray: Updated for version 1.1.0 libraries/libpaper: Updated for version 1.1.26. libraries/libpinyin: Added (Chinese input method library). libraries/libuv: Updated for version 1.26.0. libraries/libversion: Updated for version 2.8.2. libraries/libxkbcommon: Updated for version 0.8.3. libraries/pcl: Updated for version 1.9.1 + new maintainer libraries/pycparser: Updated for version 2.19. libraries/wxSQLite3: Updated for version 4.4.1. misc/KeePass: Updated for version 2.41. misc/fcitx-libpinyin: Added (wrapper for libpinyin). misc/mosquitto: Updated for version 1.5.7 multimedia/gpodder: Updated for version 3.10.7. network/brave-browser: Updated for version 0.59.35. network/dropbox: Updated for version 66.4.84. network/exim: Updated for version 4.92. network/hiawatha: Updated for version 10.8.4. network/ipfs-pack: Adde (FS and packing tool for IPFS). network/ncrack: Updated for version 0.6. network/newsboat: Updated for version 2.14.1. network/opera-developer: Updated for version 59.0.3218.0. network/opera: Updated for version 58.0.3135.65. network/shorewall-core: Updated for version 5.2.3. network/shorewall6: Updated for version 5.2.3. network/shorewall: Updated for version 5.2.3. network/signal-desktop: Updated for version 1.21.2. network/telegram: Updated for version 1.5.15. network/twitter: Updated for version 1.18.0. network/vivaldi: Updated for version 2.3.1440.48. network/yandex-browser-beta: Updated for version 19.1.0.2494. network/you-get: Updated for version 0.4.1210. network/youtube-dl: Updated for version 2019.02.08. office/kmymoney: Updated for version 4.8.3. office/pyspread: Updated for version 1.1.3. office/smoffice2018: Updated for version 2018_946. perl/perl-Glib-Object-Introspection: Updated for version 0.047. perl/perl-Math-MPFR: Updated for version 4.09. perl/perl-glib: Updated for version 1.329. python/cairocffi: Updated for version 0.9.0. python/mypy: Updated for version 0.670. python/parso: Updated for version 0.3.4. python/python3-dateutil: Updated for version 2.8.0. python/python3-parso: Updated for version 0.3.4. python/pytzdata: Updated for version 2018.9. python/regex: Updated for version 2019.02.07. python/send2trash: Updated for version 1.5.0. python/stevedore: Updated for version 1.30.0. python/termcolor: Updated HOMEPAGE & DOWNLOAD url. python/thonny: Updated for version 3.1.2. python/tqdm: Updated for version 4.31.0. python/virtualenvwrapper: Updated for version 4.8.4. ruby/rubygem-rubocop: Updated for version 0.64.0. system/TermRecord: Updated for version 1.2.5. system/ansible: Updated for version 2.7.7. system/bleachbit: Updated for version 2.1. system/chronograf: Updated for version 1.7.8. system/containerd: Updated for version 1.2.3. system/ddrescue-gui: Updated for version 2.0.1. system/docker-proxy: Updated for version 20181207_2cfbf9b. system/docker: Updated for version 18.09.2. system/firejail: Updated for version 0.9.58.2. system/fish: Updated for version 3.0.1. system/keybase: Updated for version 3.0.0. system/ksh-openbsd: Updated for version 20180115. system/letsencrypt: Updated for version 0.31.0. system/nvidia-kernel: Fix DOWNLOAD. system/omnidb-app: Updated for version 2.14.0. system/progress: Updated for version 0.14. system/qtfm: Updated for version 6.1.7. system/rhash: Updated for version 1.3.8 system/runc: Updated for version 1.0.0_rc6_6635b4f. system/spman: Updated for version 2.2.1. system/telegraf: Updated for version 1.9.4. system/udiskie: Updated for version 1.7.6. system/xonsh: Updated for version 0.8.10. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Sun Feb 17 19:24:49 2019 From: lists at osh.id.au (David O'Shaughnessy) Date: Sun, 17 Feb 2019 14:24:49 -0500 Subject: [Slackbuilds-users] Updates - 20190217.1 In-Reply-To: References: Message-ID: On Sun, 17 Feb 2019, at 7:07 AM, Willy Sudiarto Raharjo wrote: > sorry for the delay for this batch, due to some real life work :) No need to apologize Willy, thanks for your efforts :) -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From kjhambrick at gmail.com Sun Feb 17 20:31:58 2019 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 17 Feb 2019 14:31:58 -0600 Subject: [Slackbuilds-users] Updates - 20190217.1 In-Reply-To: References: Message-ID: What Dave said. No worries Willy ! Thanks for all you do when you find time to do it :) -- kjh On Sun, Feb 17, 2019 at 1:28 PM David O'Shaughnessy wrote: > On Sun, 17 Feb 2019, at 7:07 AM, Willy Sudiarto Raharjo wrote: > > sorry for the delay for this batch, due to some real life work :) > > > No need to apologize Willy, thanks for your efforts :) > > -- > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sombragris at sombragris.org Sun Feb 17 22:26:23 2019 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sun, 17 Feb 2019 19:26:23 -0300 Subject: [Slackbuilds-users] Progress: MD5SUM fail Message-ID: Hi there, I would like to report that the latest update of progress fails its MD5SUM check: > progress: > Found progress-0.14.tar.gz in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for progress-0.14.tar.gz ... FAILED! > Expected: c7c53dbfd84825a9ac037e81b685fdfb > Found: 37103cc9ac32a6e8a2286c56ec5a10c2 > > Do you want to use the downloaded progress source: Thanks and best regards, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Oficina: https://goo.gl/maps/mccgBNM7Zw32 Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow - Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Feb 17 23:52:25 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 18 Feb 2019 06:52:25 +0700 Subject: [Slackbuilds-users] Progress: MD5SUM fail In-Reply-To: References: Message-ID: <3a08c29c-679c-48ca-3913-f2c43b48a638@slackbuilds.org> > I would like to report that the latest update of progress fails its > MD5SUM check: > >> progress: >> Found progress-0.14.tar.gz in /var/cache/sbopkg. >> Checking MD5SUM: >> MD5SUM check for progress-0.14.tar.gz ... FAILED! >> Expected: c7c53dbfd84825a9ac037e81b685fdfb >> Found: 37103cc9ac32a6e8a2286c56ec5a10c2 >> >> Do you want to use the downloaded progress source: > > Thanks and best regards, Fixed in my branch thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From markand at malikania.fr Tue Feb 19 08:14:13 2019 From: markand at malikania.fr (David Demelier) Date: Tue, 19 Feb 2019 09:14:13 +0100 Subject: [Slackbuilds-users] Merging python / python3 packages Message-ID: Hello there, In Slackware current, python packages are both provided for python 3 and python 2 using the same SlackBuild file. In SlackBuilds repository there are some duplications for the same packages. E.g. python3-Pygments and Pygments. Should we start merging all these python3 packages with their python2 in master branch? Exemple of current: http://ftp.slackware.com/pub/slackware/slackware64-current/source/l/python-packaging/python-packaging.SlackBuild Also, I think we should update the python SlackBuild template. I propose to add templates as part of the git repository, it will be easier to maintain templates per Slackware version and to provide patches. Regards, -- David From matteo.bernardini at gmail.com Tue Feb 19 08:22:18 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 19 Feb 2019 09:22:18 +0100 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: References: Message-ID: Il giorno mar 19 feb 2019 alle ore 09:14 David Demelier ha scritto: > > Hello there, > > In Slackware current, python packages are both provided for python 3 and > python 2 using the same SlackBuild file. > > In SlackBuilds repository there are some duplications for the same > packages. E.g. python3-Pygments and Pygments. > > Should we start merging all these python3 packages with their python2 in > master branch? > > Exemple of current: > http://ftp.slackware.com/pub/slackware/slackware64-current/source/l/python-packaging/python-packaging.SlackBuild > > Also, I think we should update the python SlackBuild template. I propose > to add templates as part of the git repository, it will be easier to > maintain templates per Slackware version and to provide patches. > > Regards, > > -- > David Hi David, there has already been some talk about it and the plan should be merging the eventual two versions of the Slackbuild in a single one for both python-2.x and python3-3.x when the repository will be migrated to the next Slackware version, keeping things untouched in the meantime to avoid confusion and issues with dependencies. regarding templates I think you missed them, but they are already in their own git repository https://git.slackbuilds.org/templates/ Matteo From markand at malikania.fr Tue Feb 19 08:39:30 2019 From: markand at malikania.fr (David Demelier) Date: Tue, 19 Feb 2019 09:39:30 +0100 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: References: Message-ID: Le 19/02/2019 ? 09:22, Matteo Bernardini a ?crit?: > there has already been some talk about it and the plan should be > merging the eventual two versions of the Slackbuild in a single one > for both python-2.x and python3-3.x when the repository will be > migrated to the next Slackware version, keeping things untouched in > the meantime to avoid confusion and issues with dependencies. Do you mean even in master git branch? Because I thought it was used to match the Slackware current version too. Do we need to wait that Slackware 15.0 is released to do the merge then? > regarding templates I think you missed them, but they are already in > their own git repository > > https://git.slackbuilds.org/templates/ Ah yes, I've didn't see this repository. Thanks! From matteo.bernardini at gmail.com Tue Feb 19 08:53:06 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 19 Feb 2019 09:53:06 +0100 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: References: Message-ID: Il giorno mar 19 feb 2019 alle ore 09:39 David Demelier ha scritto: > > Le 19/02/2019 ? 09:22, Matteo Bernardini a ?crit : > > there has already been some talk about it and the plan should be > > merging the eventual two versions of the Slackbuild in a single one > > for both python-2.x and python3-3.x when the repository will be > > migrated to the next Slackware version, keeping things untouched in > > the meantime to avoid confusion and issues with dependencies. > > Do you mean even in master git branch? Because I thought it was used to > match the Slackware current version too. Do we need to wait that > Slackware 15.0 is released to do the merge then? also the master git branch usually tracks the latest Slackware version: for example, ATM, is used to merge things in the 14.2 one. only when a new Slackware version is about to be released (in the past when release candidates version were out), submissions will close and the master branch in our git will be used to merge fixes/adjustments for the upcoming release. when then next Slackware version will be released a new branch will appear in the repository ("15.0" in this case), the http repository will be updated, submission will reopen and maintainers will be able to push their updates/fixes for the new release. Matteo From skaendo at excite.com Tue Feb 19 10:00:09 2019 From: skaendo at excite.com (Ed Ender) Date: Tue, 19 Feb 2019 05:00:09 -0500 Subject: [Slackbuilds-users] Merging python / python3 packages Message-ID: <20190219050009.17734@web006.roc2.bluetie.com> I think that we should be trying to move away from python2 as it will be no longer supported after Jan 2020: https://pythonclock.org/ -----Original Message----- From: "Matteo Bernardini" [matteo.bernardini at gmail.com] Date: 02/19/2019 02:53 AM To: "SlackBuilds.org Users List" Subject: Re: [Slackbuilds-users] Merging python / python3 packages Il giorno mar 19 feb 2019 alle ore 09:39 David Demelier ha scritto: > > Le 19/02/2019 ? 09:22, Matteo Bernardini a ?crit : > > there has already been some talk about it and the plan should be > > merging the eventual two versions of the Slackbuild in a single one > > for both python-2.x and python3-3.x when the repository will be > > migrated to the next Slackware version, keeping things untouched in > > the meantime to avoid confusion and issues with dependencies. > > Do you mean even in master git branch? Because I thought it was used to > match the Slackware current version too. Do we need to wait that > Slackware 15.0 is released to do the merge then? also the master git branch usually tracks the latest Slackware version: for example, ATM, is used to merge things in the 14.2 one. only when a new Slackware version is about to be released (in the past when release candidates version were out), submissions will close and the master branch in our git will be used to merge fixes/adjustments for the upcoming release. when then next Slackware version will be released a new branch will appear in the repository ("15.0" in this case), the http repository will be updated, submission will reopen and maintainers will be able to push their updates/fixes for the new release. Matteo _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ From matteo.bernardini at gmail.com Tue Feb 19 10:15:45 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 19 Feb 2019 11:15:45 +0100 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: <20190219050009.17734@web006.roc2.bluetie.com> References: <20190219050009.17734@web006.roc2.bluetie.com> Message-ID: Il giorno mar 19 feb 2019 alle ore 11:00 Ed Ender ha scritto: > > I think that we should be trying to move away from python2 as it will be no longer supported after Jan 2020: > > https://pythonclock.org/ IMHO, I think unfortunately this won't be possible completely as lots of stuff will still be python-2.x only also in jan 2020, but at least this won't be a distro-specific issue and, who knows, maybe someone interested in the meantime might step in for support... Matteo From skaendo at excite.com Tue Feb 19 10:32:06 2019 From: skaendo at excite.com (Ed Ender) Date: Tue, 19 Feb 2019 05:32:06 -0500 Subject: [Slackbuilds-users] Merging python / python3 packages Message-ID: <20190219053206.20284@web001.roc2.bluetie.com> -----Original Message----- From: "Matteo Bernardini" [matteo.bernardini at gmail.com] Date: 02/19/2019 04:15 AM To: "SlackBuilds.org Users List" Subject: Re: [Slackbuilds-users] Merging python / python3 packages >IMHO, I think unfortunately this won't be possible completely as lots >of stuff will still be python-2.x only also in jan 2020, but at least >this won't be a distro-specific issue and, who knows, maybe someone >interested in the meantime might step in for support... >Matteo I completely agree that it will not be possible to completely move away from python 2 immediately, but I think that what can be built with python 3 should be, and drop any python 2 packages that are no longer needed. I don't think that it is such a good idea to merge python2/3 packages if python2 is not going to be maintained, and the python2 packages are no longer needed. I guess that I'm just trying to look to the future and not make/have a huge clusterfuck to deal with later. Ed From matteo.bernardini at gmail.com Tue Feb 19 12:03:54 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 19 Feb 2019 13:03:54 +0100 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: <20190219053206.20284@web001.roc2.bluetie.com> References: <20190219053206.20284@web001.roc2.bluetie.com> Message-ID: Il giorno mar 19 feb 2019 alle ore 11:32 Ed Ender ha scritto: > From: "Matteo Bernardini" [matteo.bernardini at gmail.com] > Date: 02/19/2019 04:15 AM > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Merging python / python3 packages > > >IMHO, I think unfortunately this won't be possible completely as lots > >of stuff will still be python-2.x only also in jan 2020, but at least > >this won't be a distro-specific issue and, who knows, maybe someone > >interested in the meantime might step in for support... > > >Matteo > > I completely agree that it will not be possible to completely move away from > python 2 immediately, but I think that what can be built with python 3 should > be, and drop any python 2 packages that are no longer needed. > > I don't think that it is such a good idea to merge python2/3 packages if > python2 is not going to be maintained, and the python2 packages are no longer > needed. > > I guess that I'm just trying to look to the future and not make/have a huge > clusterfuck to deal with later. still IMHO, we better follow what upstream, in this case Slackware, decides to do: if Pat will ship the python-2.x interpreter (the one that will supposedly won't be maintained anymore in 2020) in the next Slackware, on SBo we should ship the python modules for that (that, BTW, are maintained by different people with maybe differents agendas). Matteo From belka at caraus.de Tue Feb 19 12:19:39 2019 From: belka at caraus.de (Eugen Wissner) Date: Tue, 19 Feb 2019 13:19:39 +0100 Subject: [Slackbuilds-users] cracklib sources removed Message-ID: <1550578779.1421.6.camel@caraus.de> Hey, cracklib removed all release sources some days or weeks ago: https://github.com/cracklib/cracklib/issues/21 In the meantime you can get the sources for 2.9.6 from my server: DOWNLOAD="https://download.dlackware.com/hosted-sources/cracklib/crackl ib-2.9.6.tar.gz \ ??????????https://download.dlackware.com/hosted-sources/cracklib/crackl ib-words-2.9.6.gz" MD5SUM="c52f463585d85924b28cdc1e373ae06d \ ????????2c6ae019c8460400c14347576c01cd75" Best regards Eugene From willysr at slackbuilds.org Tue Feb 19 13:01:37 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 19 Feb 2019 20:01:37 +0700 Subject: [Slackbuilds-users] cracklib sources removed In-Reply-To: <1550578779.1421.6.camel@caraus.de> References: <1550578779.1421.6.camel@caraus.de> Message-ID: <11c79d7e-056d-3174-685e-52284a7636aa@slackbuilds.org> > cracklib removed all release sources some days or weeks ago: > https://github.com/cracklib/cracklib/issues/21 > > In the meantime you can get the sources for 2.9.6 from my server: > > DOWNLOAD="https://download.dlackware.com/hosted-sources/cracklib/crackl > ib-2.9.6.tar.gz \ > ??????????https://download.dlackware.com/hosted-sources/cracklib/crackl > ib-words-2.9.6.gz" > MD5SUM="c52f463585d85924b28cdc1e373ae06d \ > ????????2c6ae019c8460400c14347576c01cd75" Thanks Eugene i fixed this on my CSB project, but i forgot to update it here as well now it's fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From noryungi at gmail.com Tue Feb 19 13:05:34 2019 From: noryungi at gmail.com (Noryungi) Date: Tue, 19 Feb 2019 14:05:34 +0100 Subject: [Slackbuilds-users] git clone instead of downloading a source tarball In-Reply-To: References: Message-ID: One additional question, then: if a tarball is required, is it acceptable to download a git repo as a zip file and use that in a SlackBuild? Many projects hosted on GitHub offer pre-packaged "releases", but these are almost always zip files, and not ".tar.gz" files. Le jeu. 31 janv. 2019 ? 21:31, Daniel Prosser a ?crit : > To add to what Willy said, SlackBuilds on SBo don't download source > tarballs either. That is up to the user or the tool used. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Feb 19 13:09:04 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 19 Feb 2019 20:09:04 +0700 Subject: [Slackbuilds-users] git clone instead of downloading a source tarball In-Reply-To: References: Message-ID: <6495deaf-7f65-64f9-1c3a-e5fa41db51cf@slackbuilds.org> > One additional question, then: if a tarball is required, is it > acceptable to download a git repo as a zip file and use that in a > SlackBuild? > > Many projects hosted on GitHub offer pre-packaged "releases", but these > are almost always zip files, and not ".tar.gz" files. Sure, but don't use latest master commits archive as it always change use specific commits or released tarballs, either in tar.gz, tar.bz2 or zip files. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jebrhansen+SBo at gmail.com Tue Feb 19 15:15:18 2019 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 19 Feb 2019 08:15:18 -0700 Subject: [Slackbuilds-users] git clone instead of downloading a source tarball In-Reply-To: References: Message-ID: On Tue, Feb 19, 2019, 6:05 AM Noryungi One additional question, then: if a tarball is required, is it acceptable > to download a git repo as a zip file and use that in a SlackBuild? > > Many projects hosted on GitHub offer pre-packaged "releases", but these > are almost always zip files, and not ".tar.gz" files. > I have an example with the picard-plugins package I maintain. They don't provide any releases, so I link to a certain commit on github and that is used as the source. Check out the .info and .SlackBuild for an example. https://slackbuilds.org/repository/14.2/multimedia/picard-plugins/ Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at jaxartes.net Tue Feb 19 23:34:56 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 19 Feb 2019 15:34:56 -0800 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: References: Message-ID: <140b4d06-cb20-8c96-4182-17d81f36e402@jaxartes.net> On 2019-02-19 12:22 a.m., Matteo Bernardini wrote: > Il giorno mar 19 feb 2019 alle ore 09:14 David Demelier > ha scritto: >> >> In Slackware current, python packages are both provided for python 3 and >> python 2 using the same SlackBuild file. >> >> In SlackBuilds repository there are some duplications for the same >> packages. E.g. python3-Pygments and Pygments. > > Hi David, > > there has already been some talk about it and the plan should be > merging the eventual two versions of the Slackbuild in a single one > for both python-2.x and python3-3.x when the repository will be > migrated to the next Slackware version, keeping things untouched in > the meantime to avoid confusion and issues with dependencies. As Matteo mentioned, it's come up a few times on the list if you check the archives. I'm strongly in favour of merging 2/3 into single SlackBuilds and while this will mostly happen during the freeze before 15.0, maintainers can start doing it now if they are comfortable making Python 3 a *mandatory* dependency for their SlackBuilds. I'm doing it for a lot of my Python scripts, e.g. https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=e41084eb60be64574dca5a993bb9ca3ceef6a1ea (Pygments is harder since there are separate maintainers for the 2 and 3 versions) Ben From dickson.tim at googlemail.com Wed Feb 20 10:48:12 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 20 Feb 2019 10:48:12 +0000 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: <140b4d06-cb20-8c96-4182-17d81f36e402@jaxartes.net> References: <140b4d06-cb20-8c96-4182-17d81f36e402@jaxartes.net> Message-ID: On 19/02/2019 23:34, Benjamin Trigona-Harany wrote: > On 2019-02-19 12:22 a.m., Matteo Bernardini wrote: >> Il giorno mar 19 feb 2019 alle ore 09:14 David Demelier >> ha scritto: >>> >>> In Slackware current, python packages are both provided for python 3 >>> and >>> python 2 using the same SlackBuild file. >>> >>> In SlackBuilds repository there are some duplications for the same >>> packages. E.g. python3-Pygments and Pygments. >> >> Hi David, >> >> there has already been some talk about it and the plan should be >> merging the eventual two versions of the Slackbuild in a single one >> for both python-2.x and python3-3.x when the repository will be >> migrated to the next Slackware version, keeping things untouched in >> the meantime to avoid confusion and issues with dependencies. > > As Matteo mentioned, it's come up a few times on the list if you check > the archives. I'm strongly in favour of merging 2/3 into single > SlackBuilds and while this will mostly happen during the freeze before > 15.0, maintainers can start doing it now if they are comfortable > making Python 3 a *mandatory* dependency for their SlackBuilds. I'm > doing it for a lot of my Python scripts, e.g. > https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=e41084eb60be64574dca5a993bb9ca3ceef6a1ea > > (Pygments is harder since there are separate maintainers for the 2 and > 3 versions) > > Ben > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > I look after a few of python3 modules, but I only created them because the python(2) module version available didn't do python3, and the 3 version was needed for a dep. I'm quite happy for the original (python2) build maintainer to add python3 support, (usually just a single line python3 setup.py install --root=$PKG ?added to the build script after the "python setup.py install --root=$PKG" line) then my modules can get ditched. I do have a couple that are python3 only, they don't work on python2 and never will. my slackbuilds that can be merged: python3-docutils? (with docutils) python3-pyserial (with pyserial) ones that only work with python3: mypy mypy_extensions regards, Tim From yalhcru at gmail.com Wed Feb 20 22:37:17 2019 From: yalhcru at gmail.com (B Watson) Date: Wed, 20 Feb 2019 17:37:17 -0500 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: <140b4d06-cb20-8c96-4182-17d81f36e402@jaxartes.net> References: <140b4d06-cb20-8c96-4182-17d81f36e402@jaxartes.net> Message-ID: On 2/19/19, Benjamin Trigona-Harany wrote: > > As Matteo mentioned, it's come up a few times on the list if you check > the archives. I'm strongly in favour of merging 2/3 into single > SlackBuilds and while this will mostly happen during the freeze before > 15.0, maintainers can start doing it now if they are comfortable making > Python 3 a *mandatory* dependency for their SlackBuilds. I'm doing it > for a lot of my Python scripts, e.g. > https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=e41084eb60be64574dca5a993bb9ca3ceef6a1ea Why does it have to be mandatory? Currently we have in the template: python setup.py install --root=$PKG Just after (or just before) this line, add this: python3 -c 0 &>/dev/null && python3 setup.py install --root=$PKG In other words actually check for the existence of python3. I've done this for a few (as yet unsubmitted) python libraries and it works for them at least. From slackbuilds at jaxartes.net Wed Feb 20 22:51:56 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Wed, 20 Feb 2019 14:51:56 -0800 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: References: <140b4d06-cb20-8c96-4182-17d81f36e402@jaxartes.net> Message-ID: On 2019-02-20 2:37 p.m., B Watson wrote: > On 2/19/19, Benjamin Trigona-Harany wrote: >> >> As Matteo mentioned, it's come up a few times on the list if you check >> the archives. I'm strongly in favour of merging 2/3 into single >> SlackBuilds and while this will mostly happen during the freeze before >> 15.0, maintainers can start doing it now if they are comfortable making >> Python 3 a *mandatory* dependency for their SlackBuilds. I'm doing it >> for a lot of my Python scripts, e.g. >> https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=e41084eb60be64574dca5a993bb9ca3ceef6a1ea > > Why does it have to be mandatory? > > Currently we have in the template: > > python setup.py install --root=$PKG > > Just after (or just before) this line, add this: > > python3 -c 0 &>/dev/null && python3 setup.py install --root=$PKG > > In other words actually check for the existence of python3. I've done > this for a few (as yet unsubmitted) python libraries and it works for > them at least. Anyone can put conditional Python 3 builds today (I do so in some of my scripts), but I don't think it's worth deprecating a Python 3 SlackBuild if it's not mandatory since anyone with a dependency will need to update their README files to explain build orders. Myself I maintain a number of python3-xxxx scripts because otherwise my downstream builds wouldn't be able to rely on the REQUIRES line in .info. For example, I will remove python3-Pygments when Pygments makes Python 3 mandatory because I don't want my python3-ipython script to require a specific build order. It's also possible to end up with broken executables when you do conditional Python 3 installs and have no visibility into how dependencies were built. Ben From dpross1100 at msn.com Thu Feb 21 00:32:38 2019 From: dpross1100 at msn.com (Daniel Prosser) Date: Thu, 21 Feb 2019 00:32:38 +0000 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: Message-ID: I like the idea of having a single script for both Python 2 and Python 3 versions of each module (or as many as possible), but I don't think a lot of work should be done to enforce uniformity for 14.2. When Slackware 15 comes out, Python 3 will be included and the issue of dependencies will be moot for most scripts. For now, I can deal with maintainers taking different approaches. -------------- next part -------------- An HTML attachment was scrubbed... URL: From markand at malikania.fr Thu Feb 21 10:20:04 2019 From: markand at malikania.fr (David Demelier) Date: Thu, 21 Feb 2019 11:20:04 +0100 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: References: Message-ID: <407852d2-afcb-01d1-8684-6e5c7f742d0b@malikania.fr> Le 21/02/2019 ? 01:32, Daniel Prosser a ?crit?: > I like the idea of having a single script for both Python 2 and Python 3 > versions of each module (or as many as possible), but I don't think a > lot of work should be done to enforce uniformity for 14.2. When > Slackware 15 comes out, Python 3 will be included and the issue of > dependencies will be moot for most scripts. For now, I can deal with > maintainers taking different approaches. Won't it require lot of a time to do the merge for 15.0? I mean, how long are freeze times before a new Slackware version? That's why I thought the master git branch was used to track slackware-current. Now I feel like once we have a code freeze in Slackware, we need to do as quick as possible the modifications in master to match the new upcoming release. Or perhaps I understood something wrong. -- Regards From yth at ythogtha.org Thu Feb 21 10:36:44 2019 From: yth at ythogtha.org (Arnaud) Date: Thu, 21 Feb 2019 10:36:44 +0000 Subject: [Slackbuilds-users] Merging python / python3 packages In-Reply-To: <407852d2-afcb-01d1-8684-6e5c7f742d0b@malikania.fr> References: <407852d2-afcb-01d1-8684-6e5c7f742d0b@malikania.fr> Message-ID: I think it will be quite fast. I could write a shell script automatically identifying packages with python2 and python3 packages and adding standard python3 handling in the base SlackBuild, in one hour or two. Then we'll have to test them all, but obviously we'll have to test most SlackBuilds at that time. But as I remember the window is not too small, as it starts with first RC, and Pat is never in any rush to ship a new version. Le February 21, 2019 10:20:04 AM UTC, David Demelier a ?crit : >Le 21/02/2019 ? 01:32, Daniel Prosser a ?crit?: >> I like the idea of having a single script for both Python 2 and >Python 3 >> versions of each module (or as many as possible), but I don't think a > >> lot of work should be done to enforce uniformity for 14.2. When >> Slackware 15 comes out, Python 3 will be included and the issue of >> dependencies will be moot for most scripts. For now, I can deal with >> maintainers taking different approaches. > >Won't it require lot of a time to do the merge for 15.0? I mean, how >long are freeze times before a new Slackware version? > >That's why I thought the master git branch was used to track >slackware-current. Now I feel like once we have a code freeze in >Slackware, we need to do as quick as possible the modifications in >master to match the new upcoming release. > >Or perhaps I understood something wrong. > >-- >Regards > >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ -- Envoy? de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma bri?vet?. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Thu Feb 21 15:35:41 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 21 Feb 2019 15:35:41 +0000 Subject: [Slackbuilds-users] vlc slackbuild Message-ID: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> trying to run vlc segfaults. (64bit slackware 14.2 fully patched) vlc package is sbo version, (3.0.6) as is qt5 ( 5.9.7 ) is this just me? or does vlc not work. (I used to use Eric's version of vlc so this is first time just using sbo version) regards, Tim From chris.willing at linux.com Thu Feb 21 21:48:50 2019 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 22 Feb 2019 07:48:50 +1000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> Message-ID: <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> On 22/2/19 1:35 am, Tim Dickson via SlackBuilds-users wrote: > trying to run vlc segfaults. (64bit slackware 14.2 fully patched) > vlc package is sbo version, (3.0.6) as is qt5 ( 5.9.7 ) > is this just me? or does vlc not work. > (I used to use Eric's version of vlc so this is first time just using > sbo version) Try running vlc from the command line to look for messages about why it might be segfaulting. chris From lenardrspencer at gmail.com Thu Feb 21 23:36:57 2019 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Thu, 21 Feb 2019 18:36:57 -0500 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> Message-ID: It's happening with me as well. I'll post a log as soon as I can. On Thu, Feb 21, 2019, 16:49 Christoph Willing On 22/2/19 1:35 am, Tim Dickson via SlackBuilds-users wrote: > > trying to run vlc segfaults. (64bit slackware 14.2 fully patched) > > vlc package is sbo version, (3.0.6) as is qt5 ( 5.9.7 ) > > is this just me? or does vlc not work. > > (I used to use Eric's version of vlc so this is first time just using > > sbo version) > > Try running vlc from the command line to look for messages about why it > might be segfaulting. > > chris > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Fri Feb 22 01:03:32 2019 From: lists at osh.id.au (David O'Shaughnessy) Date: Thu, 21 Feb 2019 20:03:32 -0500 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> Message-ID: <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> On Thu, 21 Feb 2019, at 3:38 PM, Lenard Spencer wrote: > It's happening with me as well. I'll post a log as soon as I can. Odd, I just re-built VLC on 14.2_64 and it runs without problem. Might be something to do with certain build options? -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Fri Feb 22 10:33:25 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 22 Feb 2019 10:33:25 +0000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> Message-ID: I get [0000000001114a10] mail libvlc: Running vlc with the default interface. Use 'clvc' to use vlc without interface. Segmentation fault i did a strace but the output is over 350k long so a bit big for mailing list, and I couldn't see anything obvious at the end. the last page's worth is below ------------------------ open("/usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libfreetype.so.6", O_RDONLY|O_CLOEXEC) = 12 read(12, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\10\1\0\0\0\0\0"..., 832) = 832 fstat(12, {st_mode=S_IFREG|0755, st_size=638928, ...}) = 0 mmap(NULL, 2734136, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 12, 0) = 0x7f50ce3af000 mprotect(0x7f50ce445000, 2093056, PROT_NONE) = 0 mmap(0x7f50ce644000, 28672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 12, 0x95000) = 0x7f50ce644000 close(12)?????????????????????????????? = 0 open("/usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libbz2.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/../lib64/libbz2.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 12 fstat(12, {st_mode=S_IFREG|0644, st_size=298823, ...}) = 0 mmap(NULL, 298823, PROT_READ, MAP_PRIVATE, 12, 0) = 0x7f50ded27000 close(12)?????????????????????????????? = 0 open("/lib64/libbz2.so.1", O_RDONLY|O_CLOEXEC) = 12 read(12, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300\25\0\0\0\0\0\0"..., 832) = 832 fstat(12, {st_mode=S_IFREG|0755, st_size=66560, ...}) = 0 mmap(NULL, 2161840, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 12, 0) = 0x7f50ce19f000 mprotect(0x7f50ce1ae000, 2093056, PROT_NONE) = 0 mmap(0x7f50ce3ad000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 12, 0xe000) = 0x7f50ce3ad000 close(12)?????????????????????????????? = 0 mprotect(0x7f50d3a14000, 4096, PROT_READ) = 0 mprotect(0x7f50d37f7000, 4096, PROT_READ) = 0 mprotect(0x7f50d35c3000, 4096, PROT_READ) = 0 mprotect(0x7f50ce644000, 24576, PROT_READ) = 0 mprotect(0x7f50ce85b000, 4096, PROT_READ) = 0 mprotect(0x7f50cf08b000, 4096, PROT_READ) = 0 mprotect(0x7f50cf4bf000, 16384, PROT_READ) = 0 mprotect(0x7f50d288e000, 8192, PROT_READ) = 0 mprotect(0x7f50d2b0e000, 4096, PROT_READ) = 0 mprotect(0x7f50d10b1000, 4096, PROT_READ) = 0 mprotect(0x7f50dc32c000, 4096, PROT_READ) = 0 mprotect(0x7f50d3feb000, 40960, PROT_READ) = 0 mprotect(0x7f50d2e9c000, 65536, PROT_READ) = 0 mprotect(0x7f50d3330000, 57344, PROT_READ) = 0 mprotect(0x7f50d3c7a000, 12288, PROT_READ) = 0 mprotect(0x7f50dc53b000, 8192, PROT_READ) = 0 mprotect(0x7f50dcc08000, 49152, PROT_READ) = 0 mprotect(0x7f50dd934000, 61440, PROT_READ) = 0 mprotect(0x7f50ddb51000, 4096, PROT_READ) = 0 mprotect(0x7f50de354000, 184320, PROT_READ) = 0 mprotect(0x7f50de5d9000, 8192, PROT_READ) = 0 mprotect(0x7f50deafc000, 106496, PROT_READ) = 0 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1a5c0} --- +++ killed by SIGSEGV +++ ---------------------- vlc was built with the options OPENCV=yes WAYLAND=yes I can provide all the build options chosen for all the deps if it would help. On 22/02/2019 01:03, David O'Shaughnessy wrote: > On Thu, 21 Feb 2019, at 3:38 PM, Lenard Spencer wrote: >> It's happening with me as well.? I'll post a log as soon as I can. > > Odd, I just re-built VLC on 14.2_64 and it runs without problem. Might > be something to do with certain build options? > > -- > Dave > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Fri Feb 22 12:51:53 2019 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 22 Feb 2019 22:51:53 +1000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> Message-ID: On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: > vlc was built with the options OPENCV=yes WAYLAND=yes > I can provide all the build options chosen for all the deps if it would > help. > I admit that I don't test that particular option combination very often. I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick test of the resulting vlc was fine. However the wayland option is quite time consuming to test since it requires qt5 to have been (re)built with wayland, wayland-egl & wayland-protocols already installed. It's now late enough here that it will be an overnight job to rebuild qt5 and then vlc. In the meantime, could you build & test vlc without wayland support? Success there would indicate that wayland support is the problem. Then we'd have to figure out a possible fix or just not support that option any more. chris From dickson.tim at googlemail.com Fri Feb 22 14:59:45 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 22 Feb 2019 14:59:45 +0000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> Message-ID: <03f3658b-8f34-adab-bc58-d2bd689dc415@googlemail.com> On 22/02/2019 12:51, Christoph Willing wrote: > On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: > >> vlc was built with the options OPENCV=yes WAYLAND=yes >> I can provide all the build options chosen for all the deps if it would >> help. >> > I admit that I don't test that particular option combination very often. > I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick > test of the resulting vlc was fine. > > However the wayland option is quite time consuming to test since it > requires qt5 to have been (re)built with wayland, wayland-egl & > wayland-protocols already installed. It's now late enough here that it > will be an overnight job to rebuild qt5 and then vlc. > > In the meantime, could you build & test vlc without wayland support? > Success there would indicate that wayland support is the problem. Then > we'd have to figure out a possible fix or just not support that option > any more. > > chris > unfortunately it is still segfaulting, even when built without the wayland support. From dickson.tim at googlemail.com Fri Feb 22 17:51:36 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 22 Feb 2019 17:51:36 +0000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> Message-ID: <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> On 22/02/2019 12:51, Christoph Willing wrote: > On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: > >> vlc was built with the options OPENCV=yes WAYLAND=yes >> I can provide all the build options chosen for all the deps if it would >> help. >> > I admit that I don't test that particular option combination very often. > I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick > test of the resulting vlc was fine. > > However the wayland option is quite time consuming to test since it > requires qt5 to have been (re)built with wayland, wayland-egl & > wayland-protocols already installed. It's now late enough here that it > will be an overnight job to rebuild qt5 and then vlc. > > In the meantime, could you build & test vlc without wayland support? > Success there would indicate that wayland support is the problem. Then > we'd have to figure out a possible fix or just not support that option > any more. > > chris > > I've now also tried the other way around, enable wayland and disable opencv (legacy) and it now runs without seg-faulting, which is the opposite result of your test!. I'm open to more suggestions, although at least it runs now, Tim From willysr at slackbuilds.org Sat Feb 23 01:47:13 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 Feb 2019 08:47:13 +0700 Subject: [Slackbuilds-users] Updates - 20190223.1 Message-ID: <6ba2a4fe-09fd-cfff-53d4-0beb983f1edb@slackbuilds.org> Hi Here's another batch of updates for this week I made a mistake on one of the package i maintain (hub), in which i forget to put the new MD5SUM, which is 863a44861b281d3296f02378f4b59457. It has been fixed in my branch now, but it will get merged in the next public update next week. Vincent Batts has added some interesting container-related SlackBuild scripts (podman, buildah, skopeo) and there are some security fixes for flashplayer/pepperflash as well. On another note, Python 3.7 has entered -current and Audrius has pushed his changes for Python3 in SBo to 3.7 in a separate branch for testing. We plan to merge this changes to match what's being used in -current so we need your help on testing whether the scripts in our repository is working fine with the latest Python 3.7. Sat Feb 23 01:27:42 UTC 2019 academic/eprover: Added (a first-order theorem prover). accessibility/unclutter-xfixes: Updated for version 1.5. development/editorconfig-core-c: Added (EditorConfig core library). development/git-lfs: Updated for version 2.7.0. development/hhvm: Updated for version 3.30.4 development/hopper: Updated for version 4.5.6. development/hub: Updated for version 2.9.0. games/adom: Updated for version 3.3.3. games/sone_soup: Fix DEP. gis/Shapely: Enable Python 3 by default. gis/gpxsee: Updated for version 7.3. graphics/feh: Updated for version 3.1.2. graphics/white_dune: Added (graphical VRML97/X3D editor). libraries/cracklib: Update DOWNLOAD urls. libraries/dav1d: Added (AV1 decoder). libraries/libtermkey: Updated for version 0.21.1. libraries/libversion: Updated for version 2.9.0. misc/go-md2man: Added (utility to generate man pages). misc/subsurface: Updated for version 4.8.5 multimedia/flashplayer-plugin: Updated for version 32.0.0.142. multimedia/pepperflash-plugin: Updated for version 32.0.0.142. network/modsecurity-apache: Updated for version 2.9.3 and CRS 3.1.0. network/newsbeuter: Removed (Use newsboat). network/palemoon-bin: Updated for version 28.4.0. network/palemoon: Updated for version 28.4.0. network/signal-desktop: Updated for version 1.22.0. network/slirp4netns: Added (non-root networking utility). network/tor-browser: Updated for version 8.0.6. network/weechat: Updated for version 2.4. network/xinetd: Updated for version 2.3.15.4, upstream changed. network/zabbix_agentd: Updated for version 4.0.4. network/zabbix_java_gateway: Updated for version 4.0.4. network/zabbix_proxy: Updated for version 4.0.4. network/zabbix_server: Updated for version 4.0.4. network/zoom-linux: Update script. office/MasterPDFEditor: Updated for version 5.3.16. office/texmacs: Updated for version 1.99.9. python/pelican: Updated for version 4.0.1. python/python-fonttools: Updated for version 3.38.0. python/python-prometheus_client: Updated for version 0.6.0. python/python3-ipython: Updated for version 7.3.0. python/python3-prompt_toolkit: 2.0.9. python/python3-pyzmq: Updated for version 18.0.0 python/pyzmq: Updated for version 18.0.0. python/tqdm: Updated for version 4.31.1. system/ansible: Updated for version 2.7.8. system/buildah: Added (container build utility). system/containerd: Updated for version 1.2.4. system/fuse-overlayfs: Added (non-root overlayfs+shiftfs). system/fuse3: Added (Filesystem in Userspace). system/inxi: Updated for version 3.0.32. system/ioninja: Updated for version 3.10.2. system/ksh-openbsd: Updated for version 20190127. system/netdata: Updated for version 1.12.0. system/phoronix-test-suite: Updated for version 8.6.1. system/podman: Added (utility to run OCI-based containers). system/progress: Fix MD5SUM. system/runc: Updated for version 1.0.0_rc6_8084f76. system/saleae-logic: Added (Logic Analyzer Software). system/setconf: Updated for version 0.7.6. system/skopeo: Added (utility for container images and registries). system/steghide: Added (steganography program). system/tomb: Added several optional deps. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From chris.willing at linux.com Sat Feb 23 03:17:38 2019 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 23 Feb 2019 13:17:38 +1000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> Message-ID: <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: > On 22/02/2019 12:51, Christoph Willing wrote: >> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >> >>> vlc was built with the options OPENCV=yes WAYLAND=yes >>> I can provide all the build options chosen for all the deps if it would >>> help. >>> >> I admit that I don't test that particular option combination very often. >> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick >> test of the resulting vlc was fine. >> >> However the wayland option is quite time consuming to test since it >> requires qt5 to have been (re)built with wayland, wayland-egl & >> wayland-protocols already installed. It's now late enough here that it >> will be an overnight job to rebuild qt5 and then vlc. >> >> In the meantime, could you build & test vlc without wayland support? >> Success there would indicate that wayland support is the problem. Then >> we'd have to figure out a possible fix or just not support that option >> any more. >> >> chris >> >> > I've now also tried the other way around, enable wayland and disable > opencv (legacy) and it now runs without seg-faulting, which is the > opposite result of your test!. I'm open to more suggestions, although at > least it runs now, > I finished building wayland enabled (but otherwise standard) qt5 and vlc in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no segfault and I can play a test video with it. When run it from a terminal, the only new output is: libEGL warning: DRI2: failed to authenticate but it has no apparent effect to the running vlc. Since you're segfault-free after removing opencv-legacy, I guess that's the place to look for a cause - perhaps some exotic option it's built with? chris From psychi2009 at gmail.com Sat Feb 23 06:13:33 2019 From: psychi2009 at gmail.com (psychi) Date: Sat, 23 Feb 2019 14:13:33 +0800 Subject: [Slackbuilds-users] Merge Request for Riot-web Message-ID: Hi Willy, I submit a Merge Request for Riot-web to version 1.0.1 6 days ago. Please consider merge if there's no problem :) The MAINTAINER= was corrected to my name 'MDrights' which was 'Psychi' in its .info file. My commit of this is verified by my PGP key (also my gitlab email address is still psychi2009 at gmail.com) Thanks a lot. MDrights -- -- *[PGP key]* 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 - If I did not reply to you, please find another email address of mine. Cheers. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Sun Feb 24 00:06:43 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 24 Feb 2019 00:06:43 +0000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> Message-ID: On 23/02/2019 03:17, Christoph Willing wrote: > On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: >> On 22/02/2019 12:51, Christoph Willing wrote: >>> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >>> >>>> vlc was built with the options OPENCV=yes WAYLAND=yes >>>> I can provide all the build options chosen for all the deps if it would >>>> help. >>>> >>> I admit that I don't test that particular option combination very often. >>> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick >>> test of the resulting vlc was fine. >>> >>> However the wayland option is quite time consuming to test since it >>> requires qt5 to have been (re)built with wayland, wayland-egl & >>> wayland-protocols already installed. It's now late enough here that it >>> will be an overnight job to rebuild qt5 and then vlc. >>> >>> In the meantime, could you build & test vlc without wayland support? >>> Success there would indicate that wayland support is the problem. Then >>> we'd have to figure out a possible fix or just not support that option >>> any more. >>> >>> chris >>> >>> >> I've now also tried the other way around, enable wayland and disable >> opencv (legacy) and it now runs without seg-faulting, which is the >> opposite result of your test!. I'm open to more suggestions, although at >> least it runs now, >> > I finished building wayland enabled (but otherwise standard) qt5 and vlc > in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no > segfault and I can play a test video with it. > > When run it from a terminal, the only new output is: > libEGL warning: DRI2: failed to authenticate > but it has no apparent effect to the running vlc. > > Since you're segfault-free after removing opencv-legacy, I guess that's > the place to look for a cause - perhaps some exotic option it's built with? (looking at opencv-legacy, I built it will all options, including ffmpeg which is a recursive dependency via frie0r) > > chris > Although without opencv , vlc starts up ok, when I try to play an mp4 video file i get codec not supported VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) despite the fact that vlc and ffmpeg have been compiled with everything (all required and optional dependencies) except libva and libva-intel-driver (as I use amd apu's.) any ideas? From dchmelik at gmail.com Sun Feb 24 00:38:37 2019 From: dchmelik at gmail.com (David Melik) Date: Sat, 23 Feb 2019 16:38:37 -0800 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> Message-ID: <37b5cd29-506f-3053-8900-d50cad8db8d6@gmail.com> On 2/23/19 4:06 PM, Tim Dickson via SlackBuilds-users wrote: > > > On 23/02/2019 03:17, Christoph Willing wrote: >> On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: >>> On 22/02/2019 12:51, Christoph Willing wrote: >>>> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >>>> >>>>> vlc was built with the options OPENCV=yes WAYLAND=yes >>>>> I can provide all the build options chosen for all the deps if it >>>>> would >>>>> help. >>>>> >>>> I admit that I don't test that particular option combination very >>>> often. >>>> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick >>>> test of the resulting vlc was fine. >>>> >>>> However the wayland option is quite time consuming to test since it >>>> requires qt5 to have been (re)built with wayland, wayland-egl & >>>> wayland-protocols already installed. It's now late enough here that it >>>> will be an overnight job to rebuild qt5 and then vlc. >>>> >>>> In the meantime, could you build & test vlc without wayland support? >>>> Success there would indicate that wayland support is the problem. Then >>>> we'd have to figure out a possible fix or just not support that option >>>> any more. >>>> >>>> chris >>>> >>>> >>> I've now also tried the other way around, enable wayland and disable >>> opencv (legacy) and it now runs without seg-faulting, which is the >>> opposite result of your test!. I'm open to more suggestions, >>> although at >>> least it runs now, >>> >> I finished building wayland enabled (but otherwise standard) qt5 and vlc >> in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no >> segfault and I can play a test video with it. >> >> When run it from a terminal, the only new output is: >> ???? libEGL warning: DRI2: failed to authenticate >> but it has no apparent effect to the running vlc. >> >> Since you're segfault-free after removing opencv-legacy, I guess that's >> the place to look for a cause - perhaps some exotic option it's built >> with? > (looking at opencv-legacy, I built it will all options, including > ffmpeg which is a recursive dependency via frie0r) >> >> chris >> > Although without opencv , vlc starts up ok, when I try to play an mp4 > video file i get > > codec not supported > VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) > > despite the fact that vlc and ffmpeg have been compiled with everything > (all required and optional dependencies) except libva and > libva-intel-driver > (as I use amd apu's.) > any ideas? I think I already commented/replied at least once in recent weeks/months that vlc hasn't worked for me for over a year.? I get similar errors trying to play any sort of video, and it won't compile anymore either.? I know with some SlackBuilds (such as GNUtella) the flags, that SBo administrators have decided should be in every build (fpic, etc.) break the SlackBuild.? What about trying it without some of these so-called 'required'/default flags?? I don't have much hope for vlc because actually it's also totally broken when I try to play any video on some other GNU/Linux OS distributions that may have official packages... From chris.willing at linux.com Sun Feb 24 01:26:32 2019 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 24 Feb 2019 11:26:32 +1000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> Message-ID: <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> On 24/2/19 10:06 am, Tim Dickson via SlackBuilds-users wrote: > > > On 23/02/2019 03:17, Christoph Willing wrote: >> On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: >>> On 22/02/2019 12:51, Christoph Willing wrote: >>>> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >>>> >>>>> vlc was built with the options OPENCV=yes WAYLAND=yes >>>>> I can provide all the build options chosen for all the deps if it >>>>> would >>>>> help. >>>>> >>>> I admit that I don't test that particular option combination very >>>> often. >>>> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick >>>> test of the resulting vlc was fine. >>>> >>>> However the wayland option is quite time consuming to test since it >>>> requires qt5 to have been (re)built with wayland, wayland-egl & >>>> wayland-protocols already installed. It's now late enough here that it >>>> will be an overnight job to rebuild qt5 and then vlc. >>>> >>>> In the meantime, could you build & test vlc without wayland support? >>>> Success there would indicate that wayland support is the problem. Then >>>> we'd have to figure out a possible fix or just not support that option >>>> any more. >>>> >>>> chris >>>> >>>> >>> I've now also tried the other way around, enable wayland and disable >>> opencv (legacy) and it now runs without seg-faulting, which is the >>> opposite result of your test!. I'm open to more suggestions, although at >>> least it runs now, >>> >> I finished building wayland enabled (but otherwise standard) qt5 and vlc >> in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no >> segfault and I can play a test video with it. >> >> When run it from a terminal, the only new output is: >> ???? libEGL warning: DRI2: failed to authenticate >> but it has no apparent effect to the running vlc. >> >> Since you're segfault-free after removing opencv-legacy, I guess that's >> the place to look for a cause - perhaps some exotic option it's built >> with? > (looking at opencv-legacy, I built it will all options, including ffmpeg > which is a recursive dependency via frie0r) Maybe that is an issue - I never attempt to resolve that recursion. I choose to build opencv with ffmpeg support since I can accept that may be useful. I don't see how ffmpeg could benefit (for me) from opencv support so I don't bother with that. > Although without opencv , vlc starts up ok, when I try to play an mp4 > video file i get > > codec not supported > VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) > > despite the fact that vlc and ffmpeg have been compiled with everything > (all required and optional dependencies) except libva and > libva-intel-driver > (as I use amd apu's.) I just tried (with both my "normal" vlc and the wayland enabled vlc running in a VM) the box.mp4 and cup.mp4 that come in /usr/doc/opencv-4.0.1/html (although not in opencv-legacy) and both play fine, apart from a bad/noisy audio track in cup.mp4. Both my bare metal and VM systems contain libva and libva-intel-driver packages but I don't believe they have any effect since the bare metal system runs the nvidia binary blob for a physical nvidia card while the VM (qemu-kvm) has it's own virtual video output. When you say you build with everything "except libva and libva-intel-driver" do you mean they are not installed? If you don't have the libva* packages, which are part of a full Slackware-14.2 installation, I wonder if you are building/running without some other standard packages which may have impacted on your builds of vlc and it's many dependencies? chris From ricardo at palmtx.com.ar Sun Feb 24 02:17:15 2019 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Sat, 23 Feb 2019 23:17:15 -0300 Subject: [Slackbuilds-users] Updates - 20190223.1 In-Reply-To: <6ba2a4fe-09fd-cfff-53d4-0beb983f1edb@slackbuilds.org> References: <6ba2a4fe-09fd-cfff-53d4-0beb983f1edb@slackbuilds.org> Message-ID: <201902232317.15734.ricardo@palmtx.com.ar> El Viernes 22/02/2019 a las 22:47, Willy Sudiarto Raharjo escribi?: > On another note, Python 3.7 has entered -current and Audrius has pushed > his changes for Python3 in SBo to 3.7 in a separate branch for testing. > We plan to merge this changes to match what's being used in -current so > we need your help on testing whether the scripts in our repository is > working fine with the latest Python 3.7. FWIW, I'm using -current so I got the python 3.7 upgrade. I recompiled this slackbuilds against the new python: BeautifulSoup4 GitPython MarkupSafe Pygments alabaster asn1crypto atomicwrites cffi click colorama cryptography docopt google-apputils imagesize netifaces psutil pyasn1 pycparser pyinotify python3-dateutil python-argopt python-evdev python-gflags python-ipcalc python-mysqlclient python-sh pytz pyudev setuptools-scm simplejson snowballstemmer typing youtube-dl I also have modified feedparser slackbuild to add support for python3 without issues. Cheers, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From slackbuilds at jaxartes.net Sun Feb 24 03:21:08 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 23 Feb 2019 19:21:08 -0800 Subject: [Slackbuilds-users] Updates - 20190223.1 In-Reply-To: <201902232317.15734.ricardo@palmtx.com.ar> References: <6ba2a4fe-09fd-cfff-53d4-0beb983f1edb@slackbuilds.org> <201902232317.15734.ricardo@palmtx.com.ar> Message-ID: <2216964.jdzLmUNHoK@wintermute.sprawl.net> On Saturday, 23 February 2019 18:17:15 PST Ricardo J. Barberis wrote: > El Viernes 22/02/2019 a las 22:47, Willy Sudiarto Raharjo escribi?: > > FWIW, I'm using -current so I got the python 3.7 upgrade. > > I recompiled this slackbuilds against the new python: When moving from 3.6 to 3.7, a quick way to check which packages need to be rebuilt is to run the following in your packages directory (/var/lib/pkgtools/ packages or /var/log/packages for current and 14.2 respectively): grep "python3.6/site-packages" *SBo -l Any package listed there will need updating! Ben From dickson.tim at googlemail.com Sun Feb 24 11:50:11 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 24 Feb 2019 11:50:11 +0000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> Message-ID: <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> On 24/02/2019 01:26, Christoph Willing wrote: > On 24/2/19 10:06 am, Tim Dickson via SlackBuilds-users wrote: >> >> On 23/02/2019 03:17, Christoph Willing wrote: >>> On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: >>>> On 22/02/2019 12:51, Christoph Willing wrote: >>>>> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >>>>> >>>>>> vlc was built with the options OPENCV=yes WAYLAND=yes >>>>>> I can provide all the build options chosen for all the deps if it >>>>>> would >>>>>> help. >>>>>> >>>>> I admit that I don't test that particular option combination very >>>>> often. >>>>> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick >>>>> test of the resulting vlc was fine. >>>>> >>>>> However the wayland option is quite time consuming to test since it >>>>> requires qt5 to have been (re)built with wayland, wayland-egl & >>>>> wayland-protocols already installed. It's now late enough here that it >>>>> will be an overnight job to rebuild qt5 and then vlc. >>>>> >>>>> In the meantime, could you build & test vlc without wayland support? >>>>> Success there would indicate that wayland support is the problem. Then >>>>> we'd have to figure out a possible fix or just not support that option >>>>> any more. >>>>> >>>>> chris >>>>> >>>>> >>>> I've now also tried the other way around, enable wayland and disable >>>> opencv (legacy) and it now runs without seg-faulting, which is the >>>> opposite result of your test!. I'm open to more suggestions, although at >>>> least it runs now, >>>> >>> I finished building wayland enabled (but otherwise standard) qt5 and vlc >>> in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no >>> segfault and I can play a test video with it. >>> >>> When run it from a terminal, the only new output is: >>> ???? libEGL warning: DRI2: failed to authenticate >>> but it has no apparent effect to the running vlc. >>> >>> Since you're segfault-free after removing opencv-legacy, I guess that's >>> the place to look for a cause - perhaps some exotic option it's built >>> with? >> (looking at opencv-legacy, I built it will all options, including ffmpeg >> which is a recursive dependency via frie0r) > Maybe that is an issue - I never attempt to resolve that recursion. I > choose to build opencv with ffmpeg support since I can accept that may > be useful. I don't see how ffmpeg could benefit (for me) from opencv > support so I don't bother with that. > > >> Although without opencv , vlc starts up ok, when I try to play an mp4 >> video file i get >> >> codec not supported >> VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) >> >> despite the fact that vlc and ffmpeg have been compiled with everything >> (all required and optional dependencies) except libva and >> libva-intel-driver >> (as I use amd apu's.) by that I mean I don't enable them in the options, so that I don't have to "update" stock slackware packages > I just tried (with both my "normal" vlc and the wayland enabled vlc > running in a VM) the box.mp4 and cup.mp4 that come in > /usr/doc/opencv-4.0.1/html (although not in opencv-legacy) and both play > fine, apart from a bad/noisy audio track in cup.mp4. > > Both my bare metal and VM systems contain libva and libva-intel-driver > packages but I don't believe they have any effect since the bare metal > system runs the nvidia binary blob for a physical nvidia card while the > VM (qemu-kvm) has it's own virtual video output. > > When you say you build with everything "except libva and > libva-intel-driver" do you mean they are not installed? If you don't > have the libva* packages, which are part of a full Slackware-14.2 > installation, I wonder if you are building/running without some other > standard packages which may have impacted on your builds of vlc and it's > many dependencies? > > chris I start with a full (including kdei) slackware 14.2 install, then upgradepkg/installpkg everything in the latest patches/packages/*.t?z then I update the kernel taken from the same place (and source). I build (and install) all the sbo packages on? a qemu vm (using sbopkg), and then install them to test on a real pc (with amd apu) ( output of ?ls /var/log/packages/libva* is /var/log/packages/libva-1.6.2-x86_64-1 /var/log/packages/libva-intel-driver-1.6.2-x86_64-1 ) I? had to modify fluidsynth slackbuild adding -lpthread to -DCMAKE_EXE_LINKER_FLAGS and also to -DCMAKE_SHARED_LINKER_FLAGS in order for it to compile/link (thanks B. Watson) and avahi user and group were created on both vm and real machine as per the avahi readme. regards, Tim From chris.willing at linux.com Mon Feb 25 02:47:57 2019 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 25 Feb 2019 12:47:57 +1000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> Message-ID: On 24/2/19 9:50 pm, Tim Dickson via SlackBuilds-users wrote: > > > On 24/02/2019 01:26, Christoph Willing wrote: >> On 24/2/19 10:06 am, Tim Dickson via SlackBuilds-users wrote: >>> >>> On 23/02/2019 03:17, Christoph Willing wrote: >>>> On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: >>>>> On 22/02/2019 12:51, Christoph Willing wrote: >>>>>> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >>>>>> >>>>>>> vlc was built with the options OPENCV=yes WAYLAND=yes >>>>>>> I can provide all the build options chosen for all the deps if it >>>>>>> would >>>>>>> help. >>>>>>> >>>>>> I admit that I don't test that particular option combination very >>>>>> often. >>>>>> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick >>>>>> test of the resulting vlc was fine. >>>>>> >>>>>> However the wayland option is quite time consuming to test since it >>>>>> requires qt5 to have been (re)built with wayland, wayland-egl & >>>>>> wayland-protocols already installed. It's now late enough here >>>>>> that it >>>>>> will be an overnight job to rebuild qt5 and then vlc. >>>>>> >>>>>> In the meantime, could you build & test vlc without wayland support? >>>>>> Success there would indicate that wayland support is the problem. >>>>>> Then >>>>>> we'd have to figure out a possible fix or just not support that >>>>>> option >>>>>> any more. >>>>>> >>>>>> chris >>>>>> >>>>>> >>>>> I've now also tried the other way around, enable wayland and disable >>>>> opencv (legacy) and it now runs without seg-faulting, which is the >>>>> opposite result of your test!. I'm open to more suggestions, >>>>> although at >>>>> least it runs now, >>>>> >>>> I finished building wayland enabled (but otherwise standard) qt5 and >>>> vlc >>>> in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no >>>> segfault and I can play a test video with it. >>>> >>>> When run it from a terminal, the only new output is: >>>> ????? libEGL warning: DRI2: failed to authenticate >>>> but it has no apparent effect to the running vlc. >>>> >>>> Since you're segfault-free after removing opencv-legacy, I guess that's >>>> the place to look for a cause - perhaps some exotic option it's built >>>> with? >>> (looking at opencv-legacy, I built it will all options, including ffmpeg >>> which is a recursive dependency via frie0r) >> Maybe that is an issue - I never attempt to resolve that recursion. I >> choose to build opencv with ffmpeg support since I can accept that may >> be useful. I don't see how ffmpeg could benefit (for me) from opencv >> support so I don't bother with that. >> To test whether the recursive dependency of ffmpeg is an issue here, I rebuilt the relevant packages several times as follows, including tests of (rebuilt) vlc shown in square brackets: ffmpeg (no build opts) opencv-legacy (no build opts) frei0r ffmpeg FREI0R=yes OPENCV=yes opencv-legacy CVFFMPEG=yes frei0r [ vlc OPENCV=yes WAYLAND=yes ] ffmpeg FREI0R=yes OPENCV=yes [ vlc OPENCV=yes WAYLAND=yes ] opencv-legacy CVFFMPEG=yes [ vlc OPENCV=yes WAYLAND=yes ] At all test points, I couldn't find any problem with vlc, including playing of mp4 files. >>> Although without opencv , vlc starts up ok, when I try to play an mp4 >>> video file i get >>> >>> codec not supported >>> VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) >>> >>> despite the fact that vlc and ffmpeg have been compiled with everything >>> (all required and optional dependencies) except libva and >>> libva-intel-driver >>> (as I use amd apu's.) I think it's worth looking at your vlc build log, looking for references to h264. In my log, the configuration stage says: checking for x264 >= 0.148... yes checking for x264 >= 0.153... no Does yours have something like that? Feel free to attach your log (just up until configuration stage is done) > by that I mean I don't enable them in the options, so that I don't have > to "update" stock slackware packages >> I just tried (with both my "normal" vlc and the wayland enabled vlc >> running in a VM) the box.mp4 and cup.mp4 that come in >> /usr/doc/opencv-4.0.1/html (although not in opencv-legacy) and both play >> fine, apart from a bad/noisy audio track in cup.mp4. >> >> Both my bare metal and VM systems contain libva and libva-intel-driver >> packages but I don't believe they have any effect since the bare metal >> system runs the nvidia binary blob for a physical nvidia card while the >> VM (qemu-kvm) has it's own virtual video output. >> >> When you say you build with everything "except libva and >> libva-intel-driver" do you mean they are not installed? If you don't >> have the libva* packages, which are part of a full Slackware-14.2 >> installation, I wonder if you are building/running without some other >> standard packages which may have impacted on your builds of vlc and it's >> many dependencies? >> >> chris > I start with a full (including kdei) slackware 14.2 install, then > upgradepkg/installpkg everything in the latest patches/packages/*.t?z > then I update the kernel taken from the same place (and source). > I build (and install) all the sbo packages on? a qemu vm (using sbopkg), > and then install them to test on a real pc (with amd apu) > ( output of > ?ls /var/log/packages/libva* > is > /var/log/packages/libva-1.6.2-x86_64-1 > /var/log/packages/libva-intel-driver-1.6.2-x86_64-1 > ) OK, thanks for clearing that up. Do you ever use slapt-get or slackpkg to verify that all the packages are up to date? Manual updates are all very good but, given the number of patches involved, error prone. > I? had to modify fluidsynth slackbuild adding -lpthread to > -DCMAKE_EXE_LINKER_FLAGS and also to -DCMAKE_SHARED_LINKER_FLAGS > in order for it to compile/link (thanks B. Watson) > and avahi user and group were created on both vm and real machine as per > the avahi readme. > Good that it helps but I wonder why you need this addition? I just rebuilt fluidsynth without it. The fact that you need it is somewhat concerning - it may point to some problem with your system that, in turn, is affecting your vlc build ... chris From lramos.prof at yahoo.com.br Mon Feb 25 10:06:35 2019 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Mon, 25 Feb 2019 07:06:35 -0300 Subject: [Slackbuilds-users] qemu and capstone Message-ID: <20190225100635.GA4066@giustizia.org> Hello, recently I got a problem when building qemu (3.1.0). Basically, the compilation stops with this message: /tmp/SBo/qemu-3.1.0/include/disas/capstone.h:6:22: fatal error: capstone.h: Arquivo ou diret?rio n?o encontrado ("Arquivo ou diret?rio n?o encontrado": in Portuguese it means "File or directory not found") After some research I found that an additional include path should be added, that is, to /usr/include/capstone. About the environment: Slackware 14.2 multi-lib with a lot of slackbuilds installed. capstone is present in this machine. I could fix this issue changing qemu SlackBuild to have a better control of the capstone dependency. A variable was created ("CAPSTONE_ENABLE") which is "no" by default but can be set externally to "yes", allowing the build with capstone. I tested both cases in my machine and it worked. Additional tests may be necessary, that is, building in a machine without capstone. Below a patch which can be applied to qemu is included. Many thanks, Luiz Ramos lramos.prof at yahoo dot com dot br S?o Paulo - Brazil --- patch start --------------------------------- diff --git a/system/qemu/README b/system/qemu/README index 5a93f4648b..cd6b700334 100644 --- a/system/qemu/README +++ b/system/qemu/README @@ -34,6 +34,11 @@ users to use extended networking capabilities, do this: BRIDGE_HELPER_SETUID=yes ./qemu.SlackBuild +Build with capstone is disabled by default. To build a version with +capstone enabled, one should use this command: + + CAPSTONE_ENABLE=yes ./qemu.SlackBuild + Don't forget to load the 'kvm-intel' or 'kvm-amd' module (depending on your processor) prior to launching qemu-system-ARCH with kvm enabled. For older/unmaintained qemu frontends, this build also creates a symlink diff --git a/system/qemu/qemu.SlackBuild b/system/qemu/qemu.SlackBuild index 3f8fe1a59b..8be7e06153 100644 --- a/system/qemu/qemu.SlackBuild +++ b/system/qemu/qemu.SlackBuild @@ -54,6 +54,7 @@ # 4.4 17-Feb-2018 version update to 2.11.x release, Spectre/Meltdown mitigation # 4.5 03-Jun-2018 version update to 2.12.0 release, note new deps: sdl2, gtk+3 # 5.0 14-Dec-2018 verion update to 3.1.0 release, note minimum dependency versions on release notes +# 5.1 24-Feb-2019 added switch to better control dependency on capstone PRGNAM=qemu VERSION=${VERSION:-3.1.0} @@ -63,6 +64,7 @@ TAG=${TAG:-_SBo} KVMGROUP=${KVMGROUP:-users} TARGETS=${TARGETS:-some} VNC_ENABLE=${VNC_ENABLE:-yes} +CAPSTONE_ENABLE=${CAPSTONE_ENABLE:-no} AUDIODRIVERS=${AUDIODRIVERS:-pa,alsa,oss,sdl} BRIDGE_HELPER_SETUID=${BRIDGE_HELPER_SETUID:-no} @@ -132,6 +134,11 @@ else with_vnc="--disable-vnc" fi +# To allow compilation with capstone, use CAPSTONE_ENABLE=yes +with_capstone=$(test "$CAPSTONE_ENABLE" == "yes" \ + && echo "--enable-capstone --extra-cflags=-I/usr/include/capstone --extra-cxxflags=-I/usr/include/capstone" \ + || echo "--disable-capstone") + CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ @@ -150,6 +157,7 @@ CXXFLAGS="$SLKCFLAGS" \ --enable-nettle \ --audio-drv-list=${AUDIODRIVERS} \ $with_vnc \ + $with_capstone \ $targets # Make these first; otherwise make won't run in parallel. --- patch end ----------------------------------- From dickson.tim at googlemail.com Mon Feb 25 11:32:18 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 25 Feb 2019 11:32:18 +0000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> Message-ID: On 25/02/2019 02:47, Christoph Willing wrote: > On 24/2/19 9:50 pm, Tim Dickson via SlackBuilds-users wrote: >> >> On 24/02/2019 01:26, Christoph Willing wrote: >>> On 24/2/19 10:06 am, Tim Dickson via SlackBuilds-users wrote: >>>> On 23/02/2019 03:17, Christoph Willing wrote: >>>>> On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: >>>>>> On 22/02/2019 12:51, Christoph Willing wrote: >>>>>>> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >>>>>>> >>>>>>>> vlc was built with the options OPENCV=yes WAYLAND=yes >>>>>>>> I can provide all the build options chosen for all the deps if it >>>>>>>> would >>>>>>>> help. >>>>>>>> >>>>>>> I admit that I don't test that particular option combination very >>>>>>> often. >>>>>>> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a quick >>>>>>> test of the resulting vlc was fine. >>>>>>> >>>>>>> However the wayland option is quite time consuming to test since it >>>>>>> requires qt5 to have been (re)built with wayland, wayland-egl & >>>>>>> wayland-protocols already installed. It's now late enough here >>>>>>> that it >>>>>>> will be an overnight job to rebuild qt5 and then vlc. >>>>>>> >>>>>>> In the meantime, could you build & test vlc without wayland support? >>>>>>> Success there would indicate that wayland support is the problem. >>>>>>> Then >>>>>>> we'd have to figure out a possible fix or just not support that >>>>>>> option >>>>>>> any more. >>>>>>> >>>>>>> chris I did notice that using installpkg of the vlc with different build options instead of removepkg then installpkg when recompiling with, then without opencv-legacy caused an issue in that opencv files were left in /usr/lib64/vlc/plugins which continued to cause the problem. I had to do a removepkg, then clean (rm -r) that directory, before installpkg again in order to get vlc to start. >>>>>> I've now also tried the other way around, enable wayland and disable >>>>>> opencv (legacy) and it now runs without seg-faulting, which is the >>>>>> opposite result of your test!. I'm open to more suggestions, >>>>>> although at >>>>>> least it runs now, >>>>>> >>>>> I finished building wayland enabled (but otherwise standard) qt5 and >>>>> vlc >>>>> in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no >>>>> segfault and I can play a test video with it. >>>>> >>>>> When run it from a terminal, the only new output is: >>>>> ????? libEGL warning: DRI2: failed to authenticate >>>>> but it has no apparent effect to the running vlc. >>>>> >>>>> Since you're segfault-free after removing opencv-legacy, I guess that's >>>>> the place to look for a cause - perhaps some exotic option it's built >>>>> with? >>>> (looking at opencv-legacy, I built it will all options, including ffmpeg >>>> which is a recursive dependency via frie0r) >>> Maybe that is an issue - I never attempt to resolve that recursion. I >>> choose to build opencv with ffmpeg support since I can accept that may >>> be useful. I don't see how ffmpeg could benefit (for me) from opencv >>> support so I don't bother with that. >>> > To test whether the recursive dependency of ffmpeg is an issue here, I > rebuilt the relevant packages several times as follows, including tests > of (rebuilt) vlc shown in square brackets: > > ffmpeg (no build opts) > opencv-legacy (no build opts) > frei0r > ffmpeg FREI0R=yes OPENCV=yes > opencv-legacy CVFFMPEG=yes > frei0r > [ vlc OPENCV=yes WAYLAND=yes ] > ffmpeg FREI0R=yes OPENCV=yes > [ vlc OPENCV=yes WAYLAND=yes ] > opencv-legacy CVFFMPEG=yes > [ vlc OPENCV=yes WAYLAND=yes ] > > At all test points, I couldn't find any problem with vlc, including > playing of mp4 files. > helpful, thanks. I did.. create ffmpeg with no vars create quicktime, mjpegtools, transcode, vid.stab, opencv-legacy, frei0r ffmpeg with all vars ( ASS=yes BS2B=yes CELT=yes CHROMAPRINT=yes DC1394=yes EBUR128=yes FDK_AAC=yes FLITE=yes FREI0R=yes GME=yes ?GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes NETCDF=yes OPENAL=yes OPENCORE=yes OPENCV=yes OPENSSL=yes ?OPUS=yes RTMP=yes RUBBERBAND=yes SCHROEDINGER=yes SNAPPY=yes SPEEX=yes TESSERACT=yes TWOLAME=yes VIDSTAB=yes WEBP=yes ?X264=yes X265=yes XVID=yes ZMQ=yes ZVBI=yes ) recreate transcode and vid.stab ffmpeg recreate chromaprint ffmpeg >>>> Although without opencv , vlc starts up ok, when I try to play an mp4 >>>> video file i get >>>> >>>> codec not supported >>>> VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) >>>> >>>> despite the fact that vlc and ffmpeg have been compiled with everything >>>> (all required and optional dependencies) except libva and >>>> libva-intel-driver >>>> (as I use amd apu's.) > I think it's worth looking at your vlc build log, looking for references > to h264. In my log, the configuration stage says: > > checking for x264 >= 0.148... yes > checking for x264 >= 0.153... no > > Does yours have something like that? yes, see attached > Feel free to attach your log (just up until configuration stage is done) see attached section of log > .... > OK, thanks for clearing that up. Do you ever use slapt-get or slackpkg > to verify that all the packages are up to date? Manual updates are all > very good but, given the number of patches involved, error prone. no, but I do use the feature in sbopkg that does the same sort of thing. the only things at the moment I have on the "real" machine and not the vm is eric's libreoffice packages, flashplayer plugin and chromium browser with plugins. (and I have qemu and aquemu on the vm, and not the "real" machine) >> I? had to modify fluidsynth slackbuild adding -lpthread to >> -DCMAKE_EXE_LINKER_FLAGS and also to -DCMAKE_SHARED_LINKER_FLAGS >> in order for it to compile/link (thanks B. Watson) >> and avahi user and group were created on both vm and real machine as per >> the avahi readme. >> > Good that it helps but I wonder why you need this addition? I just > rebuilt fluidsynth without it. The fact that you need it is somewhat > concerning - it may point to some problem with your system that, in > turn, is affecting your vlc build ... it is because pkg-config doesn't add the -lpthread entry it needs to when using jack2. (whereas jack-audio-connection-kit does have the needed entry) i don't know if it effects any other builds, but i does effect fluidsynth built with jack2 instead of jack-audio-connection-kit, and as jack2 is needed for some other deps, and is supposed to be plug in compatible, that is what I used. > chris > I can include my own build notes if that would help, although the relevant ones are spread over building audacity and musescore as well as vlc. regards, Tim -------------- next part -------------- patching file modules/visualization/projectm.cpp Hunk #1 succeeded at 82 (offset 3 lines). patching file bin/Makefile.am Hunk #1 succeeded at 121 (offset 49 lines). patching file configure.ac Hunk #1 succeeded at 887 (offset 125 lines). autoreconf: Entering directory `.' autoreconf: running: autopoint --force Copying file m4/fcntl-o.m4 Copying file m4/threadlib.m4 Copying file po/Makevars.template autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'autotools'. libtoolize: copying file 'autotools/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' autoreconf: running: /usr/bin/autoconf --force autoreconf: running: /usr/bin/autoheader --force autoreconf: running: automake --add-missing --copy --force-missing configure.ac:46: installing 'autotools/compile' configure.ac:27: installing 'autotools/missing' bin/Makefile.am: installing 'autotools/depcomp' autoreconf: Leaving directory `.' checking build system type... x86_64-slackware-linux-gnu checking host system type... x86_64-slackware-linux-gnu checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether UID '0' is supported by ustar format... yes checking whether GID '0' is supported by ustar format... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... (cached) yes checking whether to enable maintainer-specific portions of Makefiles... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking whether gcc supports C11... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C preprocessor... gcc -E checking for gcc... gcc checking whether we are using the GNU Objective C compiler... yes checking whether gcc accepts -g... yes checking dependency style of gcc... gcc3 checking for egrep... (cached) /usr/bin/grep -E checking whether make sets $(MAKE)... (cached) yes checking dependency style of gcc... gcc3 checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking for bison... bison -y checking for desktop-file-validate... desktop-file-validate checking for c11-gcc... no checking for c11... no checking for c99-gcc... no checking for c99... c99 checking for an ANSI C-conforming const... yes checking for inline... inline checking for C/C++ restrict keyword... __restrict checking whether g++ supports C++11 features by default... no checking whether g++ supports C++11 features with -std=c++11... yes checking whether C compiler accepts -Werror=unknown-warning-option... no checking whether C compiler accepts -Werror=invalid-command-line-argument... no checking whether C compiler accepts -Werror=unknown-warning-option... (cached) no checking whether C compiler accepts -Werror=invalid-command-line-argument... (cached) no checking for an Android system... no checking for Tizen... no checking for 3rd party libraries path... not found checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/x86_64-slackware-linux/bin/ld checking if the linker (/usr/x86_64-slackware-linux/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking how to convert x86_64-slackware-linux-gnu file names to x86_64-slackware-linux-gnu format... func_convert_file_noop checking how to convert x86_64-slackware-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/x86_64-slackware-linux/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... (cached) pass_all checking for dlltool... dlltool checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for a working dd... /usr/bin/dd checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 checking for mt... mt checking if mt is a manifest tool... no checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... no checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/x86_64-slackware-linux/bin/ld -m elf_x86_64 checking if the linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for windres... windres checking for bash... /usr/bin/bash checking if dolt supports this host... yes, replacing libtool checking whether NLS is requested... yes checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for ld used by gcc... /usr/x86_64-slackware-linux/bin/ld -m elf_x86_64 checking if the linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no checking for CFLocaleCopyCurrent... no checking for GNU gettext in libc... yes checking whether to use NLS... yes checking where the gettext function comes from... libc checking for iconv... yes checking for working iconv... yes checking for iconv declaration... extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); checking for buggy GNU/libc versions... not present checking for shared objects suffix... .so checking for accept4... yes checking for daemon... yes checking for fcntl... yes checking for flock... yes checking for fstatvfs... yes checking for fork... yes checking for getenv... yes checking for getpwuid_r... yes checking for isatty... yes checking for lstat... yes checking for memalign... yes checking for mkostemp... yes checking for mmap... yes checking for newlocale... yes checking for open_memstream... yes checking for openat... yes checking for pipe2... yes checking for pread... yes checking for posix_fadvise... yes checking for posix_madvise... yes checking for posix_memalign... yes checking for setlocale... yes checking for stricmp... no checking for strnicmp... no checking for strptime... yes checking for uselocale... yes checking for aligned_alloc... yes checking for atof... yes checking for atoll... yes checking for dirfd... yes checking for fdopendir... yes checking for ffsll... yes checking for flockfile... yes checking for fsync... yes checking for getdelim... yes checking for getpid... yes checking for lfind... yes checking for lldiv... yes checking for memrchr... yes checking for nrand48... yes checking for poll... yes checking for recvmsg... yes checking for rewind... yes checking for sendmsg... yes checking for setenv... yes checking for strcasecmp... yes checking for strcasestr... yes checking for strdup... yes checking for strlcpy... no checking for strndup... yes checking for strnlen... yes checking for strnstr... no checking for strsep... yes checking for strtof... yes checking for strtok_r... yes checking for strtoll... yes checking for swab... yes checking for tdestroy... yes checking for tfind... yes checking for timegm... yes checking for timespec_get... yes checking for strverscmp... yes checking for pathconf... yes checking for gettimeofday... yes checking for fdatasync... yes checking whether realpath is declared... yes checking whether asprintf is declared... yes checking whether vasprintf is declared... yes checking whether gmtime_r is declared... yes checking whether localtime_r is declared... yes checking for static_assert in assert.h... yes checking for working strcoll... yes checking for eventfd... yes checking for vmsplice... yes checking for sched_getaffinity... yes checking for recvmmsg... yes checking for struct pollfd... yes checking for struct timespec... yes checking for max_align_t... yes checking for library containing connect... none required checking for library containing inet_pton... none required checking for struct if_nameindex... yes checking for if_nameindex... yes checking for if_nametoindex... yes checking for socklen_t in sys/socket.h... yes checking for struct sockaddr_storage... yes checking for getopt_long... yes checking for cos in -lm... yes checking for lrintf in -lm... yes checking for nanf in -lm... yes checking for sincos in -lm... yes checking _Thread_local support... ok checking threads.h usability... no checking threads.h presence... no checking for threads.h... no checking for getaddrinfo_a in -lanl... yes checking for library containing dlsym... -ldl checking for library containing pthread_rwlock_init... -lpthread checking for library containing clock_nanosleep... none required checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking search.h usability... yes checking search.h presence... yes checking for search.h... yes checking sys/shm.h usability... yes checking sys/shm.h presence... yes checking for sys/shm.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/uio.h usability... yes checking sys/uio.h presence... yes checking for sys/uio.h... yes checking for net/if.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking netinet/tcp.h usability... yes checking netinet/tcp.h presence... yes checking for netinet/tcp.h... yes checking netinet/udplite.h usability... no checking netinet/udplite.h presence... no checking for netinet/udplite.h... no checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/mount.h usability... yes checking sys/mount.h presence... yes checking for sys/mount.h... yes checking features.h usability... yes checking features.h presence... yes checking for features.h... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking linux/dccp.h usability... yes checking linux/dccp.h presence... yes checking for linux/dccp.h... yes checking linux/magic.h usability... yes checking linux/magic.h presence... yes checking for linux/magic.h... yes checking mntent.h usability... yes checking mntent.h presence... yes checking for mntent.h... yes checking sys/eventfd.h usability... yes checking sys/eventfd.h presence... yes checking for sys/eventfd.h... yes checking xlocale.h usability... yes checking xlocale.h presence... yes checking for xlocale.h... yes checking if C++ headers define locale_t... yes checking for ssize_t... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for gobject-2.0... yes checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for minizip ... yes checking for libidn... yes checking for dbus-1 >= 1.6.0... yes checking for libsystemd... no configure: WARNING: No package 'libsystemd' found. checking whether C compiler accepts -Wall... yes checking whether C compiler accepts -Wextra... yes checking whether C compiler accepts -Wsign-compare... yes checking whether C compiler accepts -Wundef... yes checking whether C compiler accepts -Wpointer-arith... yes checking whether C compiler accepts -Wvolatile-register-var... yes checking whether C compiler accepts -Wformat... yes checking whether C compiler accepts -Wformat-security... yes checking whether C compiler accepts -Wall... (cached) yes checking whether C compiler accepts -Wextra... (cached) yes checking whether C compiler accepts -Wsign-compare... (cached) yes checking whether C compiler accepts -Wundef... (cached) yes checking whether C compiler accepts -Wpointer-arith... (cached) yes checking whether C compiler accepts -Wvolatile-register-var... (cached) yes checking whether C compiler accepts -Wformat... (cached) yes checking whether C compiler accepts -Wformat-security... (cached) yes checking whether C compiler accepts -Wbad-function-cast... yes checking whether C compiler accepts -Wwrite-strings... yes checking whether C compiler accepts -Wmissing-prototypes... yes checking whether C compiler accepts -Werror-implicit-function-declaration... yes checking whether C compiler accepts -Winit-self... yes checking whether C compiler accepts -Wlogical-op... yes checking whether C compiler accepts -Wshadow=local... no checking whether C compiler accepts -pipe... yes checking if gcc accepts -fvisibility=hidden... yes checking if gcc accepts -O3... yes checking whether C compiler accepts -fno-math-errno... yes checking whether C compiler accepts -funsafe-math-optimizations... yes checking whether C compiler accepts -fno-rounding-math... yes checking whether C compiler accepts -fno-signaling-nans... yes checking whether C compiler accepts -fcx-limited-range... yes checking whether C compiler accepts -fno-math-errno... (cached) yes checking whether C compiler accepts -funsafe-math-optimizations... (cached) yes checking whether C compiler accepts -fno-rounding-math... (cached) yes checking whether C compiler accepts -fno-signaling-nans... (cached) yes checking whether C compiler accepts -fcx-limited-range... (cached) yes checking if gcc accepts -funroll-loops... yes checking if gcc accepts -fomit-frame-pointer... yes checking whether C compiler accepts -fstack-protector-strong... yes checking whether C compiler accepts -fstack-protector-strong... (cached) yes checking if linker supports -Bsymbolic... -Wl,-Bsymbolic checking if linker supports -z,defs... yes checking for __attribute__((packed))... yes checking execinfo.h usability... yes checking execinfo.h presence... yes checking for execinfo.h... yes checking for backtrace... yes checking if gcc groks MMX intrinsics... yes checking if gcc groks MMX inline assembly... yes checking if gcc groks MMX EXT inline assembly... yes checking if gcc groks SSE2 intrinsics... yes checking if gcc groks SSE inline assembly... yes checking if gcc groks SSE2 inline assembly... yes checking if gcc groks SSE3 inline assembly... yes checking if gcc groks SSSE3 inline assembly... yes checking if gcc groks SSE4.1 inline assembly... yes checking if gcc groks SSE4.2 inline assembly... yes checking if gcc groks SSE4A inline assembly... yes checking if gcc groks 3D Now! inline assembly... yes checking for lua5.2... no configure: WARNING: No package 'lua5.2' found, trying lua 5.1 instead checking for lua5.1... no configure: WARNING: No package 'lua5.1' found, trying lua >= 5.1 instead checking for lua >= 5.1... yes checking for luac... luac checking for libarchive >= 3.1.0... yes checking for live555... yes checking for libdc1394-2 >= 2.1.0... yes checking for libraw1394 >= 2.0.1 libavc1394 >= 0.5.3... yes checking for zvbi-0.2 >= 0.2.28... yes checking for dvdread > 4.9.0... yes checking for dvdnav > 4.9.0... yes checking for dvdnav_stream_cb in dvdnav/dvdnav.h... yes checking for libbluray >= 0.6.2... yes checking for smbclient... yes checking for libdsm >= 0.2.0... no configure: WARNING: Library libdsm >= 0.2.0 needed for dsm was not found checking for libssh2... yes checking for libnfs >= 1.10.0... yes checking linux/videodev2.h usability... yes checking linux/videodev2.h presence... yes checking for linux/videodev2.h... yes checking sys/videoio.h usability... no checking sys/videoio.h presence... no checking for sys/videoio.h... no checking DeckLinkAPIDispatch.cpp usability... no checking DeckLinkAPIDispatch.cpp presence... no checking for DeckLinkAPIDispatch.cpp... no configure: WARNING: Blackmagic DeckLink SDI include files not found checking for cdrom_msf0 in linux/cdrom.h... yes checking for scsireq in sys/scsiio.h... no checking for ioc_toc_header in sys/cdio.h... no checking for libcddb >= 0.9.5... yes checking for Linux DVB version 5.1... yes checking for libvncclient >= 0.9.9... yes checking for freerdp >= 1.0.1... no configure: WARNING: Library freerdp >= 1.0.1 needed for freerdp was not found checking for asdcplib... no checking for libdvbpsi >= 1.2.0... yes checking gme/gme.h usability... yes checking gme/gme.h presence... yes checking for gme/gme.h... yes checking for gme_identify_header in -lgme... yes checking for libsidplay2... yes checking sidplay/builders/resid.h usability... yes checking sidplay/builders/resid.h presence... yes checking for sidplay/builders/resid.h... yes checking for ogg >= 1.0... yes checking for vorbis >= 1.1... yes checking for ogg >= 1.0... yes checking for shout >= 2.1... yes checking for libebml libmatroska... yes checking for libmodplug >= 0.8.4 libmodplug != 0.8.8... yes checking mpc/mpcdec.h usability... yes checking mpc/mpcdec.h presence... yes checking for mpc/mpcdec.h... yes checking for shine >= 3.0.0... no configure: WARNING: Library shine >= 3.0.0 needed for shine was not found checking for libcrystalhd/libcrystalhd_if.h... no checking mad.h usability... yes checking mad.h presence... yes checking for mad.h... yes checking for mad_bit_init in -lmad... yes checking for libmpg123... yes checking for gstreamer-app-1.0... yes checking for gstreamer-video-1.0... yes checking for libavutil variant... ffmpeg checking for libavcodec >= 57.37.100 libavutil >= 52.0.0... yes checking libavcodec/avcodec.h usability... yes checking libavcodec/avcodec.h presence... yes checking for libavcodec/avcodec.h... yes checking libavutil/avutil.h usability... yes checking libavutil/avutil.h presence... yes checking for libavutil/avutil.h... yes checking dxgidebug.h usability... no checking dxgidebug.h presence... no checking for dxgidebug.h... no checking dxgi1_6.h usability... no checking dxgi1_6.h presence... no checking for dxgi1_6.h... no checking for libavformat >= 53.21.0 libavcodec libavutil... yes checking libavformat/avformat.h usability... yes checking libavformat/avformat.h presence... yes checking for libavformat/avformat.h... yes checking libavformat/avio.h usability... yes checking libavformat/avio.h presence... yes checking for libavformat/avio.h... yes checking for libavcodec/avcodec.h... (cached) yes checking for libavutil/avutil.h... (cached) yes checking for libswscale... yes checking libswscale/swscale.h usability... yes checking libswscale/swscale.h presence... yes checking for libswscale/swscale.h... yes checking for libavutil/avutil.h... (cached) yes checking for libpostproc libavutil... yes checking postproc/postprocess.h usability... no checking postproc/postprocess.h presence... no checking for postproc/postprocess.h... no checking neaacdec.h usability... yes checking neaacdec.h presence... yes checking for neaacdec.h... yes checking for NeAACDecOpen in -lfaad... yes checking for aom... no configure: WARNING: Library aom needed for aom was not found checking for dav1d... no configure: WARNING: Library dav1d needed for dav1d was not found checking for vpx >= 1.5.0... yes checking for vpx_codec_vp8_dx in -lvpx... yes checking for vpx_codec_vp9_dx in -lvpx... yes checking for vpx_codec_vp8_cx in -lvpx... yes checking for vpx_codec_vp9_cx in -lvpx... yes checking for twolame... yes checking a52dec/a52.h usability... yes checking a52dec/a52.h presence... yes checking for a52dec/a52.h... yes checking for a52_free in -la52... yes checking for libdca >= 0.0.5... yes checking for flac... yes checking for libmpeg2 > 0.3.2... yes checking for ogg vorbis >= 1.1 vorbisenc >= 1.1... yes checking for ogg speex >= 1.0.5... yes checking for speexdsp... yes checking for ogg opus >= 1.0.3... yes checking for spatialaudio... no configure: WARNING: Library spatialaudio needed for spatialaudio was not found checking for ogg theoradec >= 1.0 theoraenc... yes checking for ogg... yes checking for schroedinger-1.0 >= 1.0.10... yes checking png.h usability... yes checking png.h presence... yes checking for png.h... yes checking for png_set_alpha_mode in -lpng... yes checking jpeglib.h usability... yes checking jpeglib.h presence... yes checking for jpeglib.h... yes checking libbpg.h usability... no checking libbpg.h presence... no checking for libbpg.h... no checking for x262... no checking for x265... yes checking for x264 >= 0.148... yes checking for x264 >= 0.153... no checking for libmfx... no configure: WARNING: Library libmfx needed for mfx was not found checking for fluidsynth >= 1.1.2... yes checking for fluidlite... no configure: WARNING: Library fluidlite needed for fluidlite was not found checking fluidlite.h usability... no checking fluidlite.h presence... no checking for fluidlite.h... no checking for zvbi-0.2 >= 0.2.28... yes checking for libass >= 0.9.8... yes checking fontconfig/fontconfig.h usability... yes checking fontconfig/fontconfig.h presence... yes checking for fontconfig/fontconfig.h... yes checking for aribb24 >= 1.0.1... no configure: WARNING: Library aribb24 needed for aribsub was not found checking for aribb25 >= 0.2.6... no configure: WARNING: Library aribb25 >= 0.2.6 needed for aribb25 was not found checking for kate >= 0.3.0... yes checking for tiger >= 0.3.1... no checking for egl... yes checking for gl... yes checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking X11/Xlib.h usability... yes checking X11/Xlib.h presence... yes checking for X11/Xlib.h... yes checking for xcb >= 1.6... yes checking for xcb-shm... yes checking for xcb-composite... yes checking for xproto... yes checking for xcb-xv >= 1.1.90.1... yes checking for xcb-randr >= 1.3... yes checking for xcb-keysyms >= 0.3.4... yes checking for vdpau >= 0.6... yes configure: VDPAU decoding acceleration activated checking for SDL_image >= 1.2.10... yes checking for freetype2... yes checking for fontconfig >= 2.11... yes checking for fribidi... yes checking for harfbuzz... yes checking for ISpObjectToken... no configure: WARNING: sapi.h not found. Text to Speech renderer for Windows disabled checking for librsvg-2.0 >= 2.9.0... yes checking for librsvg-2.0 >= 2.9.0 cairo >= 1.13.1... yes checking linux/fb.h usability... yes checking linux/fb.h presence... yes checking for linux/fb.h... yes checking for caca >= 0.99.beta14... yes checking kva.h usability... no checking kva.h presence... no checking for kva.h... no checking interface/mmal/mmal.h usability... no checking interface/mmal/mmal.h presence... no checking for interface/mmal/mmal.h... no configure: WARNING: Cannot find development headers for mmal... checking for libpulse >= 1.0... yes checking for alsa >= 1.0.24... yes checking sndio.h usability... no checking sndio.h presence... no checking for sndio.h... no checking audioclient.h usability... no checking audioclient.h presence... no checking for audioclient.h... no checking for jack >= 1.9.7... yes checking for samplerate... yes checking for soxr >= 0.1.2... no configure: WARNING: Library soxr >= 0.1.2 needed for soxr was not found checking kai.h usability... no checking kai.h presence... no checking for kai.h... no checking for libchromaprint >= 0.6.0... yes checking for protoc... protoc checking for protobuf-lite >= 2.5.0... yes checking for Qt5Core >= 5.5.0 Qt5Widgets Qt5Gui Qt5Svg... yes checking for Qt5X11Extras... yes checking for moc-qt5... no checking for moc... /usr/lib64/qt5/bin/moc checking for rcc-qt5... no checking for rcc... /usr/lib64/qt5/bin/rcc checking for uic-qt5... no checking for uic... /usr/lib64/qt5/bin/uic checking for xpm... yes checking for xinerama... yes checking for xext... yes checking libtar.h usability... yes checking libtar.h presence... yes checking for libtar.h... yes checking VideoToolbox/VideoToolbox.h usability... no checking VideoToolbox/VideoToolbox.h presence... no checking for VideoToolbox/VideoToolbox.h... no checking AudioToolbox/AudioToolbox.h usability... no checking AudioToolbox/AudioToolbox.h presence... no checking for AudioToolbox/AudioToolbox.h... no checking for ncursesw... yes checking for srt >= 1.2.2... no configure: WARNING: Library srt >= 1.2.2 needed for srt was not found checking for libgoom2... no configure: WARNING: Library libgoom2 needed for goom was not found checking for libprojectM... yes checking for libvsxu... no configure: WARNING: No package 'libvsxu' found. checking for avahi-client >= 0.6... yes checking for libudev >= 142... yes checking for libmtp >= 1.0.0... yes checking for libupnp... yes checking for microdns... no configure: WARNING: Library microdns needed for microdns was not found checking for libxml-2.0 >= 2.5... yes checking for gcrypt 1.6.0 or later... yes checking for gnutls >= 3.3.6... yes checking for taglib >= 1.9... yes checking for libsecret-1 >= 0.18... yes checking for libnotify gtk+-3.0... yes checking for libplacebo >= 0.2.1... no checking whether byte ordering is bigendian... no checking that generated files are newer than configure... done configure: creating ./config.status From chris.willing at linux.com Mon Feb 25 12:55:19 2019 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 25 Feb 2019 22:55:19 +1000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> Message-ID: <44310ea2-d43b-af80-afd6-ee650044b26c@linux.com> On 25/2/19 9:32 pm, Tim Dickson via SlackBuilds-users wrote: > > On 25/02/2019 02:47, Christoph Willing wrote: >> On 24/2/19 9:50 pm, Tim Dickson via SlackBuilds-users wrote: >>> >>> On 24/02/2019 01:26, Christoph Willing wrote: >>>> On 24/2/19 10:06 am, Tim Dickson via SlackBuilds-users wrote: >>>>> On 23/02/2019 03:17, Christoph Willing wrote: >>>>>> On 23/2/19 3:51 am, Tim Dickson via SlackBuilds-users wrote: >>>>>>> On 22/02/2019 12:51, Christoph Willing wrote: >>>>>>>> On 22/2/19 8:33 pm, Tim Dickson via SlackBuilds-users wrote: >>>>>>>> >>>>>>>>> vlc was built with the options OPENCV=yes WAYLAND=yes >>>>>>>>> I can provide all the build options chosen for all the deps if it >>>>>>>>> would >>>>>>>>> help. >>>>>>>>> >>>>>>>> I admit that I don't test that particular option combination very >>>>>>>> often. >>>>>>>> I just rebuilt vlc with OPENCV=yes (using opencv-legacy) and a >>>>>>>> quick >>>>>>>> test of the resulting vlc was fine. >>>>>>>> >>>>>>>> However the wayland option is quite time consuming to test since it >>>>>>>> requires qt5 to have been (re)built with wayland, wayland-egl & >>>>>>>> wayland-protocols already installed. It's now late enough here >>>>>>>> that it >>>>>>>> will be an overnight job to rebuild qt5 and then vlc. >>>>>>>> >>>>>>>> In the meantime, could you build & test vlc without wayland >>>>>>>> support? >>>>>>>> Success there would indicate that wayland support is the problem. >>>>>>>> Then >>>>>>>> we'd have to figure out a possible fix or just not support that >>>>>>>> option >>>>>>>> any more. >>>>>>>> >>>>>>>> chris > I did notice that using installpkg of the vlc with different build > options instead of removepkg then installpkg when recompiling with, then > without opencv-legacy caused an issue in that opencv files were left in > /usr/lib64/vlc/plugins which continued to cause the problem. I had to do > a removepkg, then clean (rm -r) that directory, before installpkg again > in order to get vlc to start. >>>>>>> I've now also tried the other way around, enable wayland and disable >>>>>>> opencv (legacy) and it now runs without seg-faulting, which is the >>>>>>> opposite result of your test!. I'm open to more suggestions, >>>>>>> although at >>>>>>> least it runs now, >>>>>>> >>>>>> I finished building wayland enabled (but otherwise standard) qt5 and >>>>>> vlc >>>>>> in a stock 14.2 x86_64 VM with opencv-legacy. It runs normally - no >>>>>> segfault and I can play a test video with it. >>>>>> >>>>>> When run it from a terminal, the only new output is: >>>>>> ?????? libEGL warning: DRI2: failed to authenticate >>>>>> but it has no apparent effect to the running vlc. >>>>>> >>>>>> Since you're segfault-free after removing opencv-legacy, I guess >>>>>> that's >>>>>> the place to look for a cause - perhaps some exotic option it's built >>>>>> with? >>>>> (looking at opencv-legacy, I built it will all options, including >>>>> ffmpeg >>>>> which is a recursive dependency via frie0r) >>>> Maybe that is an issue - I never attempt to resolve that recursion. I >>>> choose to build opencv with ffmpeg support since I can accept that may >>>> be useful. I don't see how ffmpeg could benefit (for me) from opencv >>>> support so I don't bother with that. >>>> >> To test whether the recursive dependency of ffmpeg is an issue here, I >> rebuilt the relevant packages several times as follows, including tests >> of (rebuilt) vlc shown in square brackets: >> >> ffmpeg??????? (no build opts) >> opencv-legacy (no build opts) >> frei0r >> ffmpeg??????? FREI0R=yes OPENCV=yes >> opencv-legacy CVFFMPEG=yes >> frei0r >> [ vlc???????? OPENCV=yes WAYLAND=yes ] >> ffmpeg??????? FREI0R=yes OPENCV=yes >> [ vlc???????? OPENCV=yes WAYLAND=yes ] >> opencv-legacy CVFFMPEG=yes >> [ vlc???????? OPENCV=yes WAYLAND=yes ] >> >> At all test points, I couldn't find any problem with vlc, including >> playing of mp4 files. >> > helpful, thanks. > I did.. > create ffmpeg with no vars > create quicktime, mjpegtools, transcode, vid.stab, opencv-legacy, frei0r > ffmpeg with all vars ( ASS=yes BS2B=yes CELT=yes CHROMAPRINT=yes > DC1394=yes EBUR128=yes FDK_AAC=yes FLITE=yes FREI0R=yes GME=yes > ?GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes > NETCDF=yes OPENAL=yes OPENCORE=yes OPENCV=yes OPENSSL=yes > ?OPUS=yes RTMP=yes RUBBERBAND=yes SCHROEDINGER=yes SNAPPY=yes SPEEX=yes > TESSERACT=yes TWOLAME=yes VIDSTAB=yes WEBP=yes > ?X264=yes X265=yes XVID=yes ZMQ=yes ZVBI=yes ) > recreate transcode and vid.stab > ffmpeg > recreate chromaprint > ffmpeg In the VM I'm using to try to recreate your issue, I explicitly enabled only OPENCV & FREI0R - trying to keep things as simple as possible. However most options seem to be autodetected anyway e.g. h264 which you confirm a bit further down. Accordingly there is very little difference in our configuration logs (see below). On my bare metal, I do explicitly enable many options: ENVOPTS="ASS=yes BLURAY=yes CELT=yes DC1394=yes DECKLINK=yes FAAC=yes GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes NVENC=yes OPENAL=yes OPENCORE=yes OPENSSL=yes OPUS=yes PULSEAUDIO=yes RTMP=yes SCHROEDINGER=yes SPEEX=yes TWOLAME=yes VPX=yes X264=yes X265=yes ZVBI=yes XVID=yes " >>>>> Although without opencv , vlc starts up ok, when I try to play an mp4 >>>>> video file i get >>>>> >>>>> codec not supported >>>>> VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) >>>>> >>>>> despite the fact that vlc and ffmpeg have been compiled with >>>>> everything >>>>> (all required and optional dependencies) except libva and >>>>> libva-intel-driver >>>>> (as I use amd apu's.) >> I think it's worth looking at your vlc build log, looking for references >> to h264. In my log, the configuration stage says: >> >> checking for x264 >= 0.148... yes >> checking for x264 >= 0.153... no >> >> Does yours have something like that? > yes, see attached I'm running out of ideas as to why you're unable to play mp4 files (let alone your original segfaulting problem). Could you extract the two mp4 examples from the opencv-4.0.1.tar.gz tarball and try those please? They're at: opencv-4.0.1/doc/js_tutorials/js_assets/cup.mp4 and opencv-4.0.1/samples/cpp/tutorial_code/calib3d/real_time_pose_estimation/Data/box.mp4 Then we'll know we're testing the same thing. >> Feel free to attach your log (just up until configuration stage is done) > see attached section of log >> .... >> OK, thanks for clearing that up. Do you ever use slapt-get or slackpkg >> to verify that all the packages are up to date? Manual updates are all >> very good but, given the number of patches involved, error prone. > no, but I do use the feature in sbopkg that does the same sort of thing. > the only things at the moment I have on the "real" machine and not the > vm is eric's libreoffice packages, flashplayer plugin and chromium > browser with plugins. > (and I have qemu and aquemu on the vm, and not the "real" machine) >>> I? had to modify fluidsynth slackbuild adding -lpthread to >>> -DCMAKE_EXE_LINKER_FLAGS and also to -DCMAKE_SHARED_LINKER_FLAGS >>> in order for it to compile/link (thanks B. Watson) >>> and avahi user and group were created on both vm and real machine as per >>> the avahi readme. >>> >> Good that it helps but I wonder why you need this addition? I just >> rebuilt fluidsynth without it. The fact that you need it is somewhat >> concerning - it may point to some problem with your system that, in >> turn, is affecting your vlc build ... > it is because pkg-config doesn't add the -lpthread entry it needs to > when using jack2. (whereas jack-audio-connection-kit does have the > needed entry) > i don't know if it effects any other builds, but i does effect > fluidsynth built with jack2 instead of jack-audio-connection-kit, and as > jack2 is needed for some other deps, and is supposed to be plug in > compatible, that is what I used. OK the jack2 vs jack-audio-connection-kit shows up in the diff below but it's unlikely (I think) to be the cause of your vlc issues. Here is a diff of the configuration section of our log files. No clues unfortunately - there's not much difference between them and nothing that obviously points to segfault or mp4 difficulties.. diff chris.log tim.log 430d429 < checking for opencv > 2.0... yes 456,458c455,458 < checking gme/gme.h usability... no < checking gme/gme.h presence... no < checking for gme/gme.h... no --- > checking gme/gme.h usability... yes > checking gme/gme.h presence... yes > checking for gme/gme.h... yes > checking for gme_identify_header in -lgme... yes 597,600d596 < checking for wayland-client >= 1.5.91... yes < checking for the Wayland protocols... //usr/share/wayland-protocols < checking for the Wayland scanner... /usr/bin/wayland-scanner < checking for wayland-egl... yes 629,631c625 < checking for jack >= 1.9.7... no < configure: WARNING: Requested 'jack >= 1.9.7' but version of jack is 0.125.0, trying jack1 instead < checking for jack >= 0.120.1 jack < 1.0... yes --- > checking for jack >= 1.9.7... yes From matteo.bernardini at gmail.com Mon Feb 25 13:19:08 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 25 Feb 2019 14:19:08 +0100 Subject: [Slackbuilds-users] qemu and capstone In-Reply-To: <20190225100635.GA4066@giustizia.org> References: <20190225100635.GA4066@giustizia.org> Message-ID: I think the build system detects the external capstone and then wrongly tries to use the internal capstone headers in ./include/disas/ instead of the system's ones: there's a related discussion on the qemu mailing list https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg04159.html actually, if capstone is installed, with this patch applied qemu builds fine. Matteo From yalhcru at gmail.com Mon Feb 25 17:23:08 2019 From: yalhcru at gmail.com (B Watson) Date: Mon, 25 Feb 2019 12:23:08 -0500 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> Message-ID: On 2/24/19, Christoph Willing wrote: > >> I had to modify fluidsynth slackbuild adding -lpthread to >> -DCMAKE_EXE_LINKER_FLAGS and also to -DCMAKE_SHARED_LINKER_FLAGS >> in order for it to compile/link (thanks B. Watson) >> and avahi user and group were created on both vm and real machine as per >> the avahi readme. >> > > Good that it helps but I wonder why you need this addition? I just > rebuilt fluidsynth without it. The fact that you need it is somewhat > concerning - it may point to some problem with your system that, in > turn, is affecting your vlc build ... That's a jack2 problem. jack2 is supposed to be a drop-in replacement for jack-audio-connection-kit... but the .pc file for jack-audio-connection-kit has -lpthread and the one for jack2 does not. This is only an issue for fluidsynth when building with jack2 support. Adding -lpthread to fluidsynth is one way to fix it, but the correct fix is going to be to add it to jack2's .pc file. So far there's been no mention of jack in this thread... maybe try rebuilding fluidsynth without jack support at all, see if that affects vlc's segfaulting (doubt it, but worth a try). From dickson.tim at googlemail.com Mon Feb 25 21:54:10 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 25 Feb 2019 21:54:10 +0000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: <44310ea2-d43b-af80-afd6-ee650044b26c@linux.com> References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> <44310ea2-d43b-af80-afd6-ee650044b26c@linux.com> Message-ID: >>> rebuilt the relevant packages several times as follows, including tests >>> of (rebuilt) vlc shown in square brackets: >>> >>> ffmpeg??????? (no build opts) >>> opencv-legacy (no build opts) >>> frei0r >>> ffmpeg??????? FREI0R=yes OPENCV=yes >>> opencv-legacy CVFFMPEG=yes >>> frei0r >>> [ vlc???????? OPENCV=yes WAYLAND=yes ] >>> ffmpeg??????? FREI0R=yes OPENCV=yes >>> [ vlc???????? OPENCV=yes WAYLAND=yes ] >>> opencv-legacy CVFFMPEG=yes >>> [ vlc???????? OPENCV=yes WAYLAND=yes ] >>> >>> At all test points, I couldn't find any problem with vlc, including >>> playing of mp4 files. >>> >> helpful, thanks. >> I did.. >> create ffmpeg with no vars >> create quicktime, mjpegtools, transcode, vid.stab, opencv-legacy, frei0r >> ffmpeg with all vars ( ASS=yes BS2B=yes CELT=yes CHROMAPRINT=yes >> DC1394=yes EBUR128=yes FDK_AAC=yes FLITE=yes FREI0R=yes GME=yes >> ?GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes >> NETCDF=yes OPENAL=yes OPENCORE=yes OPENCV=yes OPENSSL=yes >> ?OPUS=yes RTMP=yes RUBBERBAND=yes SCHROEDINGER=yes SNAPPY=yes SPEEX=yes >> TESSERACT=yes TWOLAME=yes VIDSTAB=yes WEBP=yes >> ?X264=yes X265=yes XVID=yes ZMQ=yes ZVBI=yes ) >> recreate transcode and vid.stab >> ffmpeg >> recreate chromaprint >> ffmpeg > In the VM I'm using to try to recreate your issue, I explicitly enabled > only OPENCV & FREI0R - trying to keep things as simple as possible. > However most options seem to be autodetected anyway e.g. h264 which you > confirm a bit further down. Accordingly there is very little difference > in our configuration logs (see below). > > On my bare metal, I do explicitly enable many options: > ENVOPTS="ASS=yes BLURAY=yes CELT=yes DC1394=yes DECKLINK=yes FAAC=yes > GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes NVENC=yes > OPENAL=yes OPENCORE=yes OPENSSL=yes OPUS=yes PULSEAUDIO=yes RTMP=yes > SCHROEDINGER=yes SPEEX=yes TWOLAME=yes VPX=yes X264=yes X265=yes > ZVBI=yes XVID=yes > " > >>>>>> Although without opencv , vlc starts up ok, when I try to play an mp4 >>>>>> video file i get >>>>>> >>>>>> codec not supported >>>>>> VLC could not decode the format "h264" (H264 -MPEG-4 AVC (part 10)) >>>>>> >>>>>> despite the fact that vlc and ffmpeg have been compiled with >>>>>> everything >>>>>> (all required and optional dependencies) except libva and >>>>>> libva-intel-driver >>>>>> (as I use amd apu's.) >>> I think it's worth looking at your vlc build log, looking for references >>> to h264. In my log, the configuration stage says: >>> >>> checking for x264 >= 0.148... yes >>> checking for x264 >= 0.153... no >>> >>> Does yours have something like that? >> yes, see attached > I'm running out of ideas as to why you're unable to play mp4 files (let > alone your original segfaulting problem). Could you extract the two mp4 > examples from the opencv-4.0.1.tar.gz tarball and try those please? > They're at: > opencv-4.0.1/doc/js_tutorials/js_assets/cup.mp4 > and > > opencv-4.0.1/samples/cpp/tutorial_code/calib3d/real_time_pose_estimation/Data/box.mp4 > > Then we'll know we're testing the same thing. I've tried opening those two files (15sec and 8secs) but I get the "codec not supported: VLC could not decode the format "h264" (H264 - MPEG-4 AVC (part 10))" error message with both files > OK the jack2 vs jack-audio-connection-kit shows up in the diff below but > it's unlikely (I think) to be the cause of your vlc issues. > > Here is a diff of the configuration section of our log files. No clues > unfortunately - there's not much difference between them and nothing > that obviously points to segfault or mp4 difficulties.. > > diff chris.log tim.log > 430d429 > < checking for opencv > 2.0... yes > 456,458c455,458 > < checking gme/gme.h usability... no > < checking gme/gme.h presence... no > < checking for gme/gme.h... no > --- >> checking gme/gme.h usability... yes >> checking gme/gme.h presence... yes >> checking for gme/gme.h... yes >> checking for gme_identify_header in -lgme... yes > 597,600d596 > < checking for wayland-client >= 1.5.91... yes > < checking for the Wayland protocols... //usr/share/wayland-protocols > < checking for the Wayland scanner... /usr/bin/wayland-scanner > < checking for wayland-egl... yes > 629,631c625 > < checking for jack >= 1.9.7... no > < configure: WARNING: Requested 'jack >= 1.9.7' but version of jack is > 0.125.0, trying jack1 instead > < checking for jack >= 0.120.1 jack < 1.0... yes > --- >> checking for jack >= 1.9.7... yes > _ I'll try re-doing the opencv-legacy build with ffmpeg support, then redoing ffmpeg without opencv (legacy) again, and see if that makes any difference. .... some hours later deliberately uninstalled ffmpeg before creating and installing chromaprint so it doesn't depend on ffmpeg. create and install ffmpeg with all options except opencv(legacy) create and install opencv-legacy with ffmpeg support created and installed frei0r create and install ffmpeg with all options except opencv(legacy) create and install vlc with opencv and wayland it now works. both playing the example( opencv4) mp4 files box and cup, and playing the original mp4 file I tested with. Thanks chris and others for looking at this. at the moment, I'm? blaming chromaprint for the problem, and possibly the option of compiling ffmpeg with opencv support. (indirect via frei0r seems to be ok), as chromaprint without ffmpeg at compile time gets rid of one circular ffmpeg dependency, and turning off opencv option in ffmpeg brought my config more in line with chris's. thanks again, everyone. regards, Tim From dickson.tim at googlemail.com Mon Feb 25 22:03:31 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 25 Feb 2019 22:03:31 +0000 Subject: [Slackbuilds-users] MuseScore Slackbuild. Message-ID: <4c8fe995-e863-1c8c-f441-70905027889f@googlemail.com> Just sending this via sbo mailing list in case klaatu didn't get my email sent a couple of weeks ago.. Hi Klaatu, any chance of an update to Musescore? The current one is 3.0.2 changing the version number, and adding the line sed -i 's| qmake| qmake-qt5|' build/FindQt5.cmake just before the "make " lines in the buildscript is all that is required to make it work with v3.0.2. Regards, Tim From klaatu at mixedsignals.ml Mon Feb 25 22:55:41 2019 From: klaatu at mixedsignals.ml (klaatu at mixedsignals.ml) Date: Mon, 25 Feb 2019 16:55:41 -0600 Subject: [Slackbuilds-users] MuseScore Slackbuild. In-Reply-To: <4c8fe995-e863-1c8c-f441-70905027889f@googlemail.com> References: <4c8fe995-e863-1c8c-f441-70905027889f@googlemail.com> Message-ID: On 2019-02-25 16:03, Tim Dickson via SlackBuilds-users wrote: > Just sending this via sbo mailing list in case klaatu didn't get my > email sent a couple of weeks ago.. > > Hi Klaatu, any chance of an update to Musescore? The current one is > 3.0.2 > changing the version number, and adding the line > sed -i 's| qmake| qmake-qt5|' build/FindQt5.cmake > just before the "make " lines in the buildscript is all that is > required to make it work with v3.0.2. > Regards, Tim > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ Thanks, Tim. I did get your email and did mean to respond. I can't get it to build even with your suggested patch, so I need to dig into why that's not working for me. What version of Qt5 are you building against? From chris.willing at linux.com Mon Feb 25 23:17:11 2019 From: chris.willing at linux.com (Christoph Willing) Date: Tue, 26 Feb 2019 09:17:11 +1000 Subject: [Slackbuilds-users] vlc slackbuild In-Reply-To: References: <8ee31b5a-c948-22a3-7e24-8a122cfa322d@googlemail.com> <1e901ebd-41a2-33c9-5664-7751da81ca5d@linux.com> <7b843beb-b58e-4e6e-85ec-49726cbe6f9b@www.fastmail.com> <3dfc1ea3-5fde-b28a-1d99-4d70b014cb88@googlemail.com> <4e4760d9-4667-cbcc-bc5d-be125d2c7064@linux.com> <694c7899-f48f-3206-fe40-d6187baa292a@linux.com> <6633acd7-9fb6-341b-08cb-8872f4347a8f@googlemail.com> <44310ea2-d43b-af80-afd6-ee650044b26c@linux.com> Message-ID: On 26/2/19 7:54 am, Tim Dickson via SlackBuilds-users wrote: > > I'll try re-doing the opencv-legacy build with ffmpeg support, then > redoing ffmpeg without opencv (legacy) again, and see if that makes any > difference. > .... some hours later > deliberately uninstalled ffmpeg before creating and installing > chromaprint so it doesn't depend on ffmpeg. > create and install ffmpeg with all options except opencv(legacy) > create and install opencv-legacy with ffmpeg support > created and installed frei0r > create and install ffmpeg with all options except opencv(legacy) > create and install vlc with opencv and wayland > it now works. both playing the example( opencv4) mp4 files box and cup, > and playing the original mp4 file I tested with. > Thanks chris and others for looking at this. > at the moment, I'm? blaming chromaprint for the problem, and possibly > the option of compiling ffmpeg with opencv support. (indirect via frei0r > seems to be ok), as chromaprint without ffmpeg at compile time gets rid > of one circular ffmpeg dependency, and turning off opencv option in > ffmpeg brought my config more in line with chris's. > Whew! Glad it's working now. chris From kingbeowulf at gmail.com Tue Feb 26 01:28:42 2019 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 25 Feb 2019 17:28:42 -0800 Subject: [Slackbuilds-users] qemu and capstone In-Reply-To: References: <20190225100635.GA4066@giustizia.org> Message-ID: On 2/25/19 5:19 AM, Matteo Bernardini wrote: > I think the build system detects the external capstone and then > wrongly tries to use the internal capstone headers in ./include/disas/ > instead of the system's ones: there's a related discussion on the qemu > mailing list > > https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg04159.html > > actually, if capstone is installed, with this patch applied qemu builds fine. > > Matteo > That patch is a year old, for the 2.x series. From the thread, it looks like they abandoned it. qemu "should" be smart enough to find the correct headers via pkg-config. I'll double check for the next release. This is the 1st time I recall anyone mentioning qemu with capstone. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: From dickson.tim at googlemail.com Tue Feb 26 13:19:25 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Tue, 26 Feb 2019 13:19:25 +0000 Subject: [Slackbuilds-users] MuseScore Slackbuild. In-Reply-To: References: <4c8fe995-e863-1c8c-f441-70905027889f@googlemail.com> Message-ID: <4902d3c4-8fb6-8ab2-c3ce-900afc792272@googlemail.com> On 25/02/2019 22:55, klaatu at mixedsignals.ml wrote: > On 2019-02-25 16:03, Tim Dickson via SlackBuilds-users wrote: >> Just sending this via sbo mailing list in case klaatu didn't get my >> email sent a couple of weeks ago.. >> >> Hi Klaatu, any chance of an update to Musescore? The current one is >> 3.0.2 >> changing the version number, and adding the line >> sed -i 's| qmake| qmake-qt5|' build/FindQt5.cmake >> just before the "make " lines in the buildscript is all that is >> required to make it work with v3.0.2. >> Regards, Tim >> >> > > Thanks, Tim. I did get your email and did mean to respond. > > I can't get it to build even with your suggested patch, so I need to > dig into why that's not working for me. What version of Qt5 are you > building against? > qt 5.9.7 (SBo version) built with following DOCS=yes PROPRIETARY_CODECS=yes graphviz built with gts, qt5 built with optional freetds,? OpenAL, libwebp, opus, pcre2, snappy and wayland qt5-webkit 5.9.0 with optional libwebp regards, Tim PS. note the space before qmake instances in the sed line patch I made. From dickson.tim at googlemail.com Tue Feb 26 17:43:05 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Tue, 26 Feb 2019 17:43:05 +0000 Subject: [Slackbuilds-users] anki slackbuild Message-ID: <5a6ae355-3cd5-4de0-d2d4-c8762a8aa3c5@googlemail.com> the source (for the info file) has moved to https://apps.ankiweb.net/downloads/archive/anki-2.0.52-source.tgz regards, Tim