Re: [Slackbuilds-users] vlc fails
Le 2018-02-18 01:47, Christoph Willing a écrit : About vlc dependencies - I have seen this particular error and believe it is due to vlc building with optional opencv support (and opencv is built with VTK support - the default). It (vlc) certainly builds OK when opencv if _not_ present at build time. Alternatively, opencv could be built without VTK support: CVVTK=no sh opencv.SlackBuild although I haven't tried this since I think VTK is probably more valuable to opencv's functionality than opencv is to vlc's functionality. I'll investigate this further during the coming week. chris I tried first ' --without-opencv ' without success, then I removed opencv, build vlc and reinstall opencv. Thanks Christoph! ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] vlc fails
> On 18/02/18 02:10, Willy Sudiarto Raharjo wrote: > >> /tmp/SBo/vlc-3.0.0/bin/.libs/lt-vlc-cache-gen: symbol lookup > >> error: /usr/lib/libvtkCommonDataModel.so.1: undefined symbol: > >> _ZN49vtkInformationQuadratureSchemeDefinitionVectorKeyD1Ev Makefile:1789 : > >> la recette pour la cible « ../modules/plugins.dat » a échouée make[2]: *** > >> [../modules/plugins.dat] Erreur 127 make[2] : on quitte le répertoire > >> « /tmp/SBo/vlc-3.0.0/bin » > > > > Hi > > > > Have you tried to rebuild all vlc dependencies? > > > > About vlc dependencies - I have seen this particular error and believe > it is due to vlc building with optional opencv support (and opencv is > built with VTK support - the default). It (vlc) certainly builds OK when > opencv if _not_ present at build time. > > Alternatively, opencv could be built without VTK support: > CVVTK=no sh opencv.SlackBuild > although I haven't tried this since I think VTK is probably more > valuable to opencv's functionality than opencv is to vlc's functionality. > > I'll investigate this further during the coming week. > > chris > I was exactly there. VLC fails complaining about a missing symbol in /usr/lib64/libvtkCommonDataModel.so.1 So I rebuilt VTK, then opencv, then VLC, and it failed again. And VLC builds fine without opencv. As VTK and opencv are both the latest releases available, I guess there isn't much we can do about it here. I haven't found any help on google for now... -- Arnaud ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware
On 16 February 2018 at 12:29, Jheengut Pritvi wrote: > The big question::: > Is it worthwhile for a ports/portage/pacman like package manager for > Slackware that manages both binary and source packages? > > > It could be tool on top of pkgtool and sbopkg. On 18 February 2018 at 11:37, B Watson wrote: > On 2/18/18, Jheengut Pritvi wrote: >> But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages. > > Have you looked at sbotools? It's at least somewhat similar to > ports/pkgsrc (or anyway it's been described to me that way, I haven't > actually used it). > Sbotools provide a big overhead in providing dependency resolution in the form of handling of requirements from a slackbuild’s .info file, I am looking forward for something that can manage packages from both Slackware and slackbuilds.org. Slackpkg+ deals with multiple online/offline repositories. Slax used to build a Live ISO from Slackbuilds from the Slackware Source repo. In the long run, I am projecting to alleviate between building packages from scratch like gentoo for an optimized built for my SlackBoxes, for testing purposes. > If you google for Slackware + pkgsrc, you probably will find an ancient > set of directions that you should *not* follow (it involves replacing > most of the OS with pkgsrc equivalents, and "rm -rf /var/log/packages" > is one of the steps in the procedure...) I tried it along time back and still not fancy it that much. My supposition is the ability to manage packages from a singular command from maybe multiple binary repo and source repo. Slackware is meant to be installed as a whole. What if you want the simplicity of Slackware and the ability to install a small base along with with a few other packages and optimize it with reduced dependencies for new packages. This is a lot to ask, other distro offer some of these options but gives you too much overhead and headache. The answer might lie in using something else, I am unable to put it in words,.. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware
Hello, Le 18/02/2018 à 10:52, Jheengut Pritvi a écrit : <>> My supposition is the ability to manage packages from a singular > command from maybe multiple binary repo and source repo. > > > Slackware is meant to be installed as a whole. > What if you want the simplicity of Slackware and the ability to > install a small base along with with a few other packages and optimize > it with reduced dependencies for new packages. This is a lot to ask, > other distro offer some of these options but gives you too much > overhead and headache. > > The answer might lie in using something else, I am unable to put it in > words,.. A possible answer is spi from George Vlahavas: https://github.com/gapan/spi From the README: > spi (Salix Package Installer) is a command line tool that acts as a > wrapper around slapt-get and slapt-src. > > It searches both package (slapt-get) and SlackBuild (slapt-get) local > caches for software. It can also update both local caches. > > When installing software, if a package is available through slapt-get, > it will install it, otherwise it will install it through slapt-src. If > any SlackBuild dependencies are available through slapt-get, it will > install them through slapt-get. slap-src, slapt-get, their GUIs gslapt and sourcery and spi are included in Salix, Slackel and Slint and usable on Slackware. All command-line tools have associated man pages. Several packages repositories can be used with priorities and automatic dependencies management is provided and optional. Usual caveat for these features: know what you are doing and be aware of the limitations of the tools. If you want to begin with a small base (as do Salix and Slackel) you will need dependency information about genuine Slackware packages. To do that, just include as SOURCE in /etc/slapt-get/slapt-getrc e.g. this repository: http://slackware.uk/salix/x86_64/slackware-14.2/ as George has computed the deps listed in PACKAGES.TXT in the PACKAGE REQUIRED field. Some other repos also provided this information as e.g. the repositories sbrepos kindly provided by Eric: http://slackware.uk/people/alien/sbrepos/ Be aware though that deps can vary upon the environment in which the package has been built. For instance sbrepos assume a full Slackware installation hence only list dependencies beyond that. And in case anyone wonders: this post is *not* a request to include these tools in Slackware. Have a good day, Didier ___ SlackBuilds-users mailing list SlackBuilds-users@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] uripareser requires graphviz
Hi, It looks that uripareser requires graphviz in order to build. -- Best regards, Andrzej Telszewski diff --git a/libraries/uriparser/uriparser.info b/libraries/uriparser/uriparser.info index 4499490d60..fc7a0829d8 100644 --- a/libraries/uriparser/uriparser.info +++ b/libraries/uriparser/uriparser.info @@ -5,6 +5,6 @@ DOWNLOAD="https://github.com/uriparser/uriparser/releases/download/uriparser-0.8 MD5SUM="80c110ec22b70570ec124563a7a63075" DOWNLOAD_x86_64="" MD5SUM_x86_64="" -REQUIRES="" +REQUIRES="graphviz" MAINTAINER="Matteo Bernardini" EMAIL="po...@slackbuilds.org" ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] uripareser requires graphviz
2018-02-18 15:08 GMT+01:00 Andrzej Telszewski : > Hi, > > It looks that uripareser requires graphviz in order to build. thanks Andrzej, I removed by mistake in the update. It will get fixed soon. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] vlc fails
On Sun, 18 Feb 2018 09:18:54 +0100 false...@clansco.org wrote: > I tried first ' --without-opencv ' without success, then I removed > opencv, build vlc and reinstall opencv. > --enable-opencv=no do the job ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware
On 2/18/18, Didier Spaier wrote: >> >> When installing software, if a package is available through slapt-get, >> it will install it, otherwise it will install it through slapt-src. If >> any SlackBuild dependencies are available through slapt-get, it will >> install them through slapt-get. This sounds like a recipe for disaster. SBo packages are tested with dependencies from SBo, this thing would install binaries from elsewhere if it can find them? Right now there's a guy on IRC complaining that alienbob's vlc package segfaults, and it turns out to be because he's using SBo's qt5 instead of alienbob's. Mixing and matching repos is the cause, in other words. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware
Le 18/02/2018 à 21:19, B Watson a écrit : > On 2/18/18, Didier Spaier wrote: >>> >>> When installing software, if a package is available through slapt-get, >>> it will install it, otherwise it will install it through slapt-src. If >>> any SlackBuild dependencies are available through slapt-get, it will >>> install them through slapt-get. > > This sounds like a recipe for disaster. Possibly,indeed, it it's misused. > SBo packages are tested with > dependencies from SBo, this thing would install binaries from elsewhere if > it can find them? From elsewhere but not from anywhere. I did my best to warn at least the Slint users, cf. http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-get/slapt-getrc.x86_64 which links to: http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-get/README.slaptgetrc.Slint But have all users read the docs won't happen, I know... > Right now there's a guy on IRC complaining that alienbob's vlc package > segfaults, and it turns out to be because he's using SBo's qt5 instead > of alienbob's. Mixing and matching repos is the cause, in other words. Yes. Incidentally that's why I ended up including in the Slint repo a vlc-2.2.8 package built against qt4, using Eric's SlackBuild. Cheers, Didier ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] vlc fails
Since this issue involves three different projects (VTK, opencv, vlc), I don't expect a speedy resolution. I've therefore updated the SlackBuild to disable opencv support. Experimenters can explicitly turn it back on at build time with the OPENCV environment variable e.g. OPENCV=yes sh vlc.SlackBuild At the same time (but unrelated) I've added libnfs and protobuf to REQUIRES, adding support for NFS and Chromecast. chris signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] vlc fails
On 2/18/18, Christoph Willing wrote: > Since this issue involves three different projects (VTK, opencv, vlc), I > don't expect a speedy resolution. I've therefore updated the SlackBuild > to disable opencv support. Experimenters can explicitly turn it back on > at build time with the OPENCV environment variable e.g. > OPENCV=yes sh vlc.SlackBuild For those of us who don't use vlc regularly... what vlc feature(s) depend on opencv? From the description, is for "computer vision and machine learning". What does vlc use it for, exactly? Also, I notice there's an older opencv version in the repo, as opencv-legacy. Does it work with vlc? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] vlc fails
> Also, I notice there's an older opencv version in the repo, as > opencv-legacy. Does it work with vlc? opencv-legacy was needed by libkface since it's not working well with latest opencv, so Christoph has decided to put opencv-legacy in order for libkface to build properly while other scripts depending on opencv can work with the latest version. -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] vlc fails
On 19/02/18 11:20, B Watson wrote: > On 2/18/18, Christoph Willing wrote: >> Since this issue involves three different projects (VTK, opencv, vlc), I >> don't expect a speedy resolution. I've therefore updated the SlackBuild >> to disable opencv support. Experimenters can explicitly turn it back on >> at build time with the OPENCV environment variable e.g. >> OPENCV=yes sh vlc.SlackBuild > > For those of us who don't use vlc regularly... what vlc feature(s) > depend on opencv? From the description, is for "computer vision and > machine learning". What does vlc use it for, exactly? > OpenCV as well as other "computer vision and machine learning" software often use video streams as their input. Although OpenCV has its own video input module, it's easy to imagine that a specialised video tool like vlc might have greater functionality that make it more attractive as a video reader than OpenCV's native video reader. The opencv plugin for vlc enables opencv's video processing tools to be applied directly within vlc. The example plugin (the one causing the build problem with the latest vlc at the moment) is a face recognition filter. A simple non-opencv filter that gives an idea of how these filters work is the built in motion detection tool. Test it as follows: play a video and select Tools->Effects & Filters, then select Video Effects tab in the resulting window, then the Advanced tab and its Motion detect selector. See moving parts of video highlighted. Not great for watching movies but useful for those who find these things useful :) > Also, I notice there's an older opencv version in the repo, as > opencv-legacy. Does it work with vlc? > Yes, good point. I'll add that to the README. chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
