From z.coldplayer at gmail.com Wed Apr 1 10:09:23 2020 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Wed, 1 Apr 2020 14:09:23 +0400 Subject: [Slackbuilds-users] help In-Reply-To: <9217930D-7259-44E2-95F6-7A6AE4CAAF7D@posteo.net> References: <9217930D-7259-44E2-95F6-7A6AE4CAAF7D@posteo.net> Message-ID: what is the issue here ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdiamond at acadiau.ca Wed Apr 1 15:47:21 2020 From: jdiamond at acadiau.ca (Jim Diamond) Date: Wed, 1 Apr 2020 12:47:21 -0300 Subject: [Slackbuilds-users] intel-microcode Message-ID: <20200401154721.GA30034@jdiamond-mb.acadiau.ca> All, I see there is a newer version (20191115 vs. 20190618 in SBo). Is there concern about this version, or is it just that the slackbuild needs updating? Thanks. Jim From matteo.bernardini at gmail.com Wed Apr 1 16:01:32 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 1 Apr 2020 18:01:32 +0200 Subject: [Slackbuilds-users] intel-microcode In-Reply-To: <20200401154721.GA30034@jdiamond-mb.acadiau.ca> References: <20200401154721.GA30034@jdiamond-mb.acadiau.ca> Message-ID: Il giorno mer 1 apr 2020 alle ore 17:47 Jim Diamond via SlackBuilds-users ha scritto: > > All, > > I see there is a newer version (20191115 vs. 20190618 in SBo). > > Is there concern about this version, or is it just that the slackbuild > needs updating? > > Thanks. > > Jim Hi Jim, have you tried asking the maintainer? I'll put him in cc. Matteo From jdiamond at acadiau.ca Wed Apr 1 16:36:48 2020 From: jdiamond at acadiau.ca (Jim Diamond) Date: Wed, 1 Apr 2020 13:36:48 -0300 Subject: [Slackbuilds-users] intel-microcode Message-ID: <20200401163648.GC4066@jdiamond-mb.acadiau.ca> On Wed, Apr 1, 2020 at 18:01 (+0200), Matteo Bernardini wrote: > Il giorno mer 1 apr 2020 alle ore 17:47 Jim Diamond via > SlackBuilds-users ha scritto: >> All, >> I see there is a newer version (20191115 vs. 20190618 in SBo). >> Is there concern about this version, or is it just that the slackbuild >> needs updating? >> Thanks. >> Jim > Hi Jim, > have you tried asking the maintainer? > I'll put him in cc. Hi Matteo, I didn't... a long time ago someone suggested that I just mail the list, rather than the individual maintainer. But I agree, cc:ing the maintainer seems like a good idea. Cheers. Jim From mariolpantunes at gmail.com Wed Apr 1 17:48:49 2020 From: mariolpantunes at gmail.com (=?UTF-8?Q?M=c3=a1rio_Antunes?=) Date: Wed, 1 Apr 2020 18:48:49 +0100 Subject: [Slackbuilds-users] snappy 1.1.8 Slackbuild fails to build on 14.2 In-Reply-To: <20200329235211.GB7712@chirva-slack.chirva-slack> References: <20200329232254.GA7712@chirva-slack.chirva-slack> <20200329235211.GB7712@chirva-slack.chirva-slack> Message-ID: <881afe44-62c9-d1af-c995-c3ff55517d10@gmail.com> Have fixed the slackbuild to avoid build the tests. Can you please check if it works with you? If it works I will upload this version to the slackbuilds.org On 3/30/20 12:52 AM, Stuart Little wrote: > Indeed, turning off the tests worked. > > I could not find a flag-driven way to do this, so I made a small change to the source (cloned from github[0]): > > --- cut here --- > > commit b9bb9d34f062e20c9e3df5eff4faa02eba6e1f17 (HEAD -> testsoff) > Date: Sun Mar 29 19:49:26 2020 -0400 > > turn tests off > > diff --git a/CMakeLists.txt b/CMakeLists.txt > index 68686f7..ee5bc0d 100644 > --- a/CMakeLists.txt > +++ b/CMakeLists.txt > @@ -41,7 +41,7 @@ endif(NOT CMAKE_CXX_STANDARD) > # it prominent in the GUI. > option(BUILD_SHARED_LIBS "Build shared libraries(DLLs)." OFF) > > -option(SNAPPY_BUILD_TESTS "Build Snappy's own tests." ON) > +option(SNAPPY_BUILD_TESTS "Build Snappy's own tests." OFF) > > option(SNAPPY_FUZZING_BUILD "Build Snappy for fuzzing." OFF) > > --- end --- > > Everything worked fine afterwards (i.e. built and installed the Slackbuild as usual). > > --- > > References: > > [0] https://github.com/google/snappy > > > On Sun, Mar 29, 2020 at 07:22:54PM -0400, Stuart Little wrote: >> Hello, >> >> I am on Slackware 14.2 and I tried to update snappy[0] just now from the Slackbuild. I am getting a suite of errors relating to tests (log attached). >> >> I'll be looking into whether it's possible to pass snappy some flag that suppresses the compilation of snappy_unittest, see if that helps. >> >> Thank you, and al the best >> >> --- >> >> References: >> >> [0] https://slackbuilds.org/repository/14.2/development/snappy/?search=snappy >> ########################################### >> New queue process started on: >> Sun Mar 29 19:17:19 EDT 2020 >> ########################################### >> >> +++++++++++++++++++++++++++++++++++++++++++ >> PRE-CHECK LOG >> Using the SBo repository for Slackware 14.2 >> Queue Process: Download, build, and install >> >> snappy: >> Checking GPG for snappy.tar.gz ... OK >> Processing snappy 1.1.8-1 >> Using original .info file >> Using original SlackBuild file >> No build options selected. >> >> +++++++++++++++++++++++++++++++++++++++++++ >> >> Pre-check complete. >> >> Do you wish to proceed based on the search results above? Packages not >> found will be skipped during the process. >> >> (P)roceed or (Q)uit?: p >> >> >> Processing snappy >> >> snappy: >> Found snappy-1.1.8.tar.gz in /var/cache/sbopkg. >> Checking MD5SUM: >> MD5SUM check for snappy-1.1.8.tar.gz ... OK >> Building package for snappy... >> snappy-1.1.8/ >> snappy-1.1.8/.appveyor.yml >> snappy-1.1.8/.gitignore >> snappy-1.1.8/.travis.yml >> snappy-1.1.8/AUTHORS >> snappy-1.1.8/CMakeLists.txt >> snappy-1.1.8/CONTRIBUTING.md >> snappy-1.1.8/COPYING >> snappy-1.1.8/NEWS >> snappy-1.1.8/README.md >> snappy-1.1.8/cmake/ >> snappy-1.1.8/cmake/SnappyConfig.cmake.in >> snappy-1.1.8/cmake/config.h.in >> snappy-1.1.8/docs/ >> snappy-1.1.8/docs/README.md >> snappy-1.1.8/format_description.txt >> snappy-1.1.8/framing_format.txt >> snappy-1.1.8/snappy-c.cc >> snappy-1.1.8/snappy-c.h >> snappy-1.1.8/snappy-internal.h >> snappy-1.1.8/snappy-sinksource.cc >> snappy-1.1.8/snappy-sinksource.h >> snappy-1.1.8/snappy-stubs-internal.cc >> snappy-1.1.8/snappy-stubs-internal.h >> snappy-1.1.8/snappy-stubs-public.h.in >> snappy-1.1.8/snappy-test.cc >> snappy-1.1.8/snappy-test.h >> snappy-1.1.8/snappy.cc >> snappy-1.1.8/snappy.h >> snappy-1.1.8/snappy_compress_fuzzer.cc >> snappy-1.1.8/snappy_uncompress_fuzzer.cc >> snappy-1.1.8/snappy_unittest.cc >> snappy-1.1.8/testdata/ >> snappy-1.1.8/testdata/alice29.txt >> snappy-1.1.8/testdata/asyoulik.txt >> snappy-1.1.8/testdata/baddata1.snappy >> snappy-1.1.8/testdata/baddata2.snappy >> snappy-1.1.8/testdata/baddata3.snappy >> snappy-1.1.8/testdata/fireworks.jpeg >> snappy-1.1.8/testdata/geo.protodata >> snappy-1.1.8/testdata/html >> snappy-1.1.8/testdata/html_x_4 >> snappy-1.1.8/testdata/kppkn.gtb >> snappy-1.1.8/testdata/lcet10.txt >> snappy-1.1.8/testdata/paper-100k.pdf >> snappy-1.1.8/testdata/plrabn12.txt >> snappy-1.1.8/testdata/urls.10K >> -- The C compiler identification is GNU 5.5.0 >> -- The CXX compiler identification is GNU 5.5.0 >> -- Check for working C compiler: /usr/bin/cc >> -- Check for working C compiler: /usr/bin/cc -- works >> -- Detecting C compiler ABI info >> -- Detecting C compiler ABI info - done >> -- Detecting C compile features >> -- Detecting C compile features - done >> -- Check for working CXX compiler: /usr/bin/c++ >> -- Check for working CXX compiler: /usr/bin/c++ -- works >> -- Detecting CXX compiler ABI info >> -- Detecting CXX compiler ABI info - done >> -- Detecting CXX compile features >> -- Detecting CXX compile features - done >> -- Check if the system is big endian >> -- Searching 16 bit integer >> -- Looking for sys/types.h >> -- Looking for sys/types.h - found >> -- Looking for stdint.h >> -- Looking for stdint.h - found >> -- Looking for stddef.h >> -- Looking for stddef.h - found >> -- Check size of unsigned short >> -- Check size of unsigned short - done >> -- Using unsigned short >> -- Check if the system is big endian - little endian >> -- Looking for byteswap.h >> -- Looking for byteswap.h - found >> -- Looking for sys/endian.h >> -- Looking for sys/endian.h - not found >> -- Looking for sys/mman.h >> -- Looking for sys/mman.h - found >> -- Looking for sys/resource.h >> -- Looking for sys/resource.h - found >> -- Looking for sys/time.h >> -- Looking for sys/time.h - found >> -- Looking for sys/uio.h >> -- Looking for sys/uio.h - found >> -- Looking for unistd.h >> -- Looking for unistd.h - found >> -- Looking for windows.h >> -- Looking for windows.h - not found >> -- Looking for zlibVersion in z >> -- Looking for zlibVersion in z - found >> -- Looking for lzo1x_1_15_compress in lzo2 >> -- Looking for lzo1x_1_15_compress in lzo2 - found >> -- Performing Test HAVE_VISUAL_STUDIO_ARCH_AVX >> -- Performing Test HAVE_VISUAL_STUDIO_ARCH_AVX - Failed >> -- Performing Test HAVE_VISUAL_STUDIO_ARCH_AVX2 >> -- Performing Test HAVE_VISUAL_STUDIO_ARCH_AVX2 - Failed >> -- Performing Test HAVE_CLANG_MAVX >> -- Performing Test HAVE_CLANG_MAVX - Success >> -- Performing Test HAVE_CLANG_MBMI2 >> -- Performing Test HAVE_CLANG_MBMI2 - Success >> -- Performing Test HAVE_BUILTIN_EXPECT >> -- Performing Test HAVE_BUILTIN_EXPECT - Success >> -- Performing Test HAVE_BUILTIN_CTZ >> -- Performing Test HAVE_BUILTIN_CTZ - Success >> -- Performing Test SNAPPY_HAVE_SSSE3 >> -- Performing Test SNAPPY_HAVE_SSSE3 - Failed >> -- Performing Test SNAPPY_HAVE_BMI2 >> -- Performing Test SNAPPY_HAVE_BMI2 - Failed >> -- Looking for mmap >> -- Looking for mmap - found >> -- Looking for sysconf >> -- Looking for sysconf - found >> -- Configuring done >> -- Generating done >> -- Build files have been written to: /tmp/SBo/snappy-1.1.8/build >> Scanning dependencies of target snappy >> [ 25%] Building CXX object CMakeFiles/snappy.dir/snappy-sinksource.cc.o >> [ 25%] Building CXX object CMakeFiles/snappy.dir/snappy.cc.o >> [ 37%] Building CXX object CMakeFiles/snappy.dir/snappy-c.cc.o >> [ 50%] Building CXX object CMakeFiles/snappy.dir/snappy-stubs-internal.cc.o >> [ 62%] Linking CXX shared library libsnappy.so >> [ 62%] Built target snappy >> Scanning dependencies of target snappy_unittest >> [ 87%] Building CXX object CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o >> [ 87%] Building CXX object CMakeFiles/snappy_unittest.dir/snappy-test.cc.o >> [100%] Linking CXX executable snappy_unittest >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::scoped_ptr, std::allocator > >::reset(std::basic_stringstream, std::allocator >*) [clone .constprop.163]': >> snappy_unittest.cc:(.text+0x1d10): undefined reference to `testing::internal::IsTrue(bool)' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_ZeroOffsetCopy_Test::TestBody()': >> snappy_unittest.cc:(.text+0x3319): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x3340): undefined reference to `testing::internal::GetBoolAssertionFailureMessage(testing::AssertionResult const&, char const*, char const*, char const*)' >> snappy_unittest.cc:(.text+0x3363): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x336e): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x3376): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x33df): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_ZeroOffsetCopyValidation_Test::TestBody()': >> snappy_unittest.cc:(.text+0x3461): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x3488): undefined reference to `testing::internal::GetBoolAssertionFailureMessage(testing::AssertionResult const&, char const*, char const*, char const*)' >> snappy_unittest.cc:(.text+0x34ab): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x34b6): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x34be): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x3527): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_FindMatchLengthRandom_Test::TestBody()': >> snappy_unittest.cc:(.text+0x7639): undefined reference to `testing::AssertionSuccess()' >> snappy_unittest.cc:(.text+0x7657): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x768f): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x769a): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x76a2): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x76b7): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0x76e9): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0x7985): undefined reference to `testing::internal::PrintTo(unsigned char, std::ostream*)' >> snappy_unittest.cc:(.text+0x7cdd): undefined reference to `testing::internal::PrintTo(unsigned char, std::ostream*)' >> snappy_unittest.cc:(.text+0x7f1e): undefined reference to `testing::internal::EqFailure(char const*, char const*, std::string const&, std::string const&, bool)' >> snappy_unittest.cc:(.text+0x7f66): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x7f9e): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x7fa9): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x7fb1): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x7fc6): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0x7ff9): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0x8176): undefined reference to `testing::AssertionSuccess()' >> snappy_unittest.cc:(.text+0x8924): undefined reference to `testing::internal::PrintStringTo(std::string const&, std::ostream*)' >> snappy_unittest.cc:(.text+0x8966): undefined reference to `testing::internal::PrintStringTo(std::string const&, std::ostream*)' >> snappy_unittest.cc:(.text+0x89a9): undefined reference to `testing::internal::EqFailure(char const*, char const*, std::string const&, std::string const&, bool)' >> snappy_unittest.cc:(.text+0x89ed): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x8a25): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x8a30): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x8a38): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x8b6f): undefined reference to `testing::AssertionSuccess()' >> snappy_unittest.cc:(.text+0x8e03): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x8e30): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x8f1f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_FindMatchLength_Test::TestBody()': >> snappy_unittest.cc:(.text+0x8fdd): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x900a): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9015): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x901d): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x907b): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x90a8): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x90b3): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x90bb): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x911d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x914a): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9155): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x915d): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x91bb): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x91e8): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x91f3): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x91fb): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x925d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x928a): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9295): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x929d): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x92ff): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x932c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9337): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x933f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x93a1): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x93ce): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x93d9): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x93e1): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9443): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9470): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x947b): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9483): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x94e5): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9512): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x951d): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9525): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9587): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x95b4): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x95bf): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x95c7): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9629): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9656): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9661): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9669): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x96cb): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x96f8): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9703): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x970b): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x976d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x979a): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x97a5): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x97ad): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x980f): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x983c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9847): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x984f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x98b1): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x98de): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x98e9): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x98f1): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9953): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9980): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x998b): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9993): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x99f5): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9a22): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9a2d): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9a35): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9a97): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9ac4): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9acf): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9ad7): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9b39): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9b66): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9b71): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9b79): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9bdb): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9c08): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9c13): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9c1b): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9c7d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9caa): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9cb5): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9cbd): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9d1f): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9d4c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9d57): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9d5f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9dc1): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9dee): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9df9): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9e01): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9e5f): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9e8c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9e97): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9e9f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9efd): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9f2a): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9f35): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9f3d): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0x9f9b): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0x9fc8): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0x9fd3): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0x9fdb): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa039): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa066): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa071): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa079): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa0db): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa108): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa113): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa11b): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa17d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa1aa): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa1b5): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa1bd): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa21f): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa24c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa257): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa25f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa2c1): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa2ee): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa2f9): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa301): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa363): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa390): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa39b): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa3a3): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa405): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa432): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa43d): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa445): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa4a7): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa4d4): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa4df): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa4e7): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa549): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa576): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa581): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa589): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa5eb): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa618): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa623): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa62b): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa68d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa6ba): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa6c5): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa6cd): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa72f): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa75c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa767): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa76f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa7d1): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa7fe): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa809): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa811): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa873): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa8a0): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa8ab): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa8b3): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa915): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa942): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa94d): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa955): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xa9b7): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xa9e4): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xa9ef): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xa9f7): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xaa59): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xaa86): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xaa91): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xaa99): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xaafb): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xab28): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xab33): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xab3b): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xab9d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xabca): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xabd5): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xabdd): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xac31): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xac68): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xace3): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xad27): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:snappy_unittest.cc:(.text+0xad59): more undefined references to `testing::internal::AssertHelper::~AssertHelper()' follow >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_VerifyCharTable_Test::TestBody()': >> snappy_unittest.cc:(.text+0xbae2): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xbb69): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xbb79): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xbb81): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xbbb4): undefined reference to `testing::AssertionSuccess()' >> snappy_unittest.cc:(.text+0xbbcc): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xbc2c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xbc39): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xbc41): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xbc56): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0xbc89): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0xc485): undefined reference to `testing::internal::EqFailure(char const*, char const*, std::string const&, std::string const&, bool)' >> snappy_unittest.cc:(.text+0xc4c5): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text+0xc52c): undefined reference to `testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)' >> snappy_unittest.cc:(.text+0xc537): undefined reference to `testing::internal::AssertHelper::operator=(testing::Message const&) const' >> snappy_unittest.cc:(.text+0xc53f): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xc554): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0xc581): undefined reference to `testing::internal::IsTrue(bool)' >> snappy_unittest.cc:(.text+0xc686): undefined reference to `testing::AssertionSuccess()' >> snappy_unittest.cc:(.text+0xcbfd): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xcc28): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> snappy_unittest.cc:(.text+0xcc60): undefined reference to `testing::internal::AssertHelper::~AssertHelper()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_VerifyCharTable_Test::~Snappy_VerifyCharTable_Test()': >> snappy_unittest.cc:(.text._ZN6snappy27Snappy_VerifyCharTable_TestD2Ev[_ZN6snappy27Snappy_VerifyCharTable_TestD5Ev]+0xf): undefined reference to `testing::Test::~Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_VerifyCharTable_Test::~Snappy_VerifyCharTable_Test()': >> snappy_unittest.cc:(.text._ZN6snappy27Snappy_VerifyCharTable_TestD0Ev[_ZN6snappy27Snappy_VerifyCharTable_TestD5Ev]+0x13): undefined reference to `testing::Test::~Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_FindMatchLengthRandom_Test::~Snappy_FindMatchLengthRandom_Test()': >> snappy_unittest.cc:(.text._ZN6snappy33Snappy_FindMatchLengthRandom_TestD2Ev[_ZN6snappy33Snappy_FindMatchLengthRandom_TestD5Ev]+0xf): undefined reference to `testing::Test::~Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_FindMatchLengthRandom_Test::~Snappy_FindMatchLengthRandom_Test()': >> snappy_unittest.cc:(.text._ZN6snappy33Snappy_FindMatchLengthRandom_TestD0Ev[_ZN6snappy33Snappy_FindMatchLengthRandom_TestD5Ev]+0x13): undefined reference to `testing::Test::~Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_FindMatchLength_Test::~Snappy_FindMatchLength_Test()': >> snappy_unittest.cc:(.text._ZN6snappy27Snappy_FindMatchLength_TestD2Ev[_ZN6snappy27Snappy_FindMatchLength_TestD5Ev]+0xf): undefined reference to `testing::Test::~Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:snappy_unittest.cc:(.text._ZN6snappy27Snappy_FindMatchLength_TestD0Ev[_ZN6snappy27Snappy_FindMatchLength_TestD5Ev]+0x13): more undefined references to `testing::Test::~Test()' follow >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::TestFactoryImpl::CreateTest()': >> snappy_unittest.cc:(.text._ZN7testing8internal15TestFactoryImplIN6snappy34CorruptedTest_VerifyCorrupted_TestEE10CreateTestEv[_ZN7testing8internal15TestFactoryImplIN6snappy34CorruptedTest_VerifyCorrupted_TestEE10CreateTestEv]+0x17): undefined reference to `testing::Test::Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::TestFactoryImpl::CreateTest()': >> snappy_unittest.cc:(.text._ZN7testing8internal15TestFactoryImplIN6snappy23Snappy_SimpleTests_TestEE10CreateTestEv[_ZN7testing8internal15TestFactoryImplIN6snappy23Snappy_SimpleTests_TestEE10CreateTestEv]+0x17): undefined reference to `testing::Test::Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::TestFactoryImpl::CreateTest()': >> snappy_unittest.cc:(.text._ZN7testing8internal15TestFactoryImplIN6snappy21Snappy_MaxBlowup_TestEE10CreateTestEv[_ZN7testing8internal15TestFactoryImplIN6snappy21Snappy_MaxBlowup_TestEE10CreateTestEv]+0x17): undefined reference to `testing::Test::Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::TestFactoryImpl::CreateTest()': >> snappy_unittest.cc:(.text._ZN7testing8internal15TestFactoryImplIN6snappy22Snappy_RandomData_TestEE10CreateTestEv[_ZN7testing8internal15TestFactoryImplIN6snappy22Snappy_RandomData_TestEE10CreateTestEv]+0x17): undefined reference to `testing::Test::Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::TestFactoryImpl::CreateTest()': >> snappy_unittest.cc:(.text._ZN7testing8internal15TestFactoryImplIN6snappy26Snappy_FourByteOffset_TestEE10CreateTestEv[_ZN7testing8internal15TestFactoryImplIN6snappy26Snappy_FourByteOffset_TestEE10CreateTestEv]+0x17): undefined reference to `testing::Test::Test()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:snappy_unittest.cc:(.text._ZN7testing8internal15TestFactoryImplIN6snappy26Snappy_IOVecEdgeCases_TestEE10CreateTestEv[_ZN7testing8internal15TestFactoryImplIN6snappy26Snappy_IOVecEdgeCases_TestEE10CreateTestEv]+0x17): more undefined references to `testing::Test::Test()' follow >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `__static_initialization_and_destruction_0(int, int) [clone .constprop.154]': >> snappy_unittest.cc:(.text.startup+0x5b): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0xbd): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x118): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x168): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x1bc): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x20c): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x260): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x2b0): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x304): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x354): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x3a8): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x3f8): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x44c): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x49c): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x4f0): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x540): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x594): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x5e5): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x639): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x68a): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x6de): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x72f): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x783): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x7d4): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x828): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x878): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x8cc): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x91c): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0x970): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0x9c0): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0xa14): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0xa64): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> snappy_unittest.cc:(.text.startup+0xab8): undefined reference to `testing::internal::GetTestTypeId()' >> snappy_unittest.cc:(.text.startup+0xb08): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `main': >> snappy_unittest.cc:(.text.startup+0x115e): undefined reference to `testing::InitGoogleTest(int*, char**)' >> snappy_unittest.cc:(.text.startup+0x179c): undefined reference to `testing::UnitTest::GetInstance()' >> snappy_unittest.cc:(.text.startup+0x17a4): undefined reference to `testing::UnitTest::Run()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::scoped_ptr::reset(std::string*)': >> snappy_unittest.cc:(.text._ZN7testing8internal10scoped_ptrISsE5resetEPSs[_ZN7testing8internal10scoped_ptrISsE5resetEPSs]+0x19): undefined reference to `testing::internal::IsTrue(bool)' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::AssertionResult& testing::AssertionResult::operator<< (char const* const&)': >> snappy_unittest.cc:(.text._ZN7testing15AssertionResultlsIPKcEERS0_RKT_[_ZN7testing15AssertionResultlsIPKcEERS0_RKT_]+0x17): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text._ZN7testing15AssertionResultlsIPKcEERS0_RKT_[_ZN7testing15AssertionResultlsIPKcEERS0_RKT_]+0x54): undefined reference to `testing::Message::GetString() const' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::AssertionResult& testing::AssertionResult::operator<< (char const (&) [5])': >> snappy_unittest.cc:(.text._ZN7testing15AssertionResultlsIA5_cEERS0_RKT_[_ZN7testing15AssertionResultlsIA5_cEERS0_RKT_]+0x19): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text._ZN7testing15AssertionResultlsIA5_cEERS0_RKT_[_ZN7testing15AssertionResultlsIA5_cEERS0_RKT_]+0x55): undefined reference to `testing::Message::GetString() const' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `std::string testing::PrintToString(char const&)': >> snappy_unittest.cc:(.text._ZN7testing13PrintToStringIcEESsRKT_[_ZN7testing13PrintToStringIcEESsRKT_]+0x2c): undefined reference to `testing::internal::PrintTo(unsigned char, std::ostream*)' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::AssertionResult testing::internal::CmpHelperOpFailure(char const*, char const*, char const&, char const&, char const*)': >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x46): undefined reference to `testing::AssertionFailure()' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0xf1): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x132): undefined reference to `testing::Message::GetString() const' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x18d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x1bd): undefined reference to `testing::Message::GetString() const' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIccEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x200): undefined reference to `testing::AssertionResult::AssertionResult(testing::AssertionResult const&)' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::AssertionResult testing::internal::CmpHelperEQ(char const*, char const*, int const&, int const&)': >> snappy_unittest.cc:(.text._ZN7testing8internal11CmpHelperEQIiiEENS_15AssertionResultEPKcS4_RKT_RKT0_[_ZN7testing8internal11CmpHelperEQIiiEENS_15AssertionResultEPKcS4_RKT_RKT0_]+0x54): undefined reference to `testing::internal::EqFailure(char const*, char const*, std::string const&, std::string const&, bool)' >> snappy_unittest.cc:(.text._ZN7testing8internal11CmpHelperEQIiiEENS_15AssertionResultEPKcS4_RKT_RKT0_[_ZN7testing8internal11CmpHelperEQIiiEENS_15AssertionResultEPKcS4_RKT_RKT0_]+0x91): undefined reference to `testing::AssertionSuccess()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::AssertionResult testing::internal::CmpHelperOpFailure(char const*, char const*, int const&, unsigned short const&, char const*)': >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x46): undefined reference to `testing::AssertionFailure()' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0xf1): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x132): undefined reference to `testing::Message::GetString() const' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x18d): undefined reference to `testing::Message::Message()' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x1bd): undefined reference to `testing::Message::GetString() const' >> snappy_unittest.cc:(.text._ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_[_ZN7testing8internal18CmpHelperOpFailureIitEENS_15AssertionResultEPKcS4_RKT_RKT0_S4_]+0x200): undefined reference to `testing::AssertionResult::AssertionResult(testing::AssertionResult const&)' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTIN6snappy34CorruptedTest_VerifyCorrupted_TestE[_ZTIN6snappy34CorruptedTest_VerifyCorrupted_TestE]+0x10): undefined reference to `typeinfo for testing::Test' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTIN6snappy23Snappy_SimpleTests_TestE[_ZTIN6snappy23Snappy_SimpleTests_TestE]+0x10): undefined reference to `typeinfo for testing::Test' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTIN6snappy21Snappy_MaxBlowup_TestE[_ZTIN6snappy21Snappy_MaxBlowup_TestE]+0x10): undefined reference to `typeinfo for testing::Test' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTIN6snappy22Snappy_RandomData_TestE[_ZTIN6snappy22Snappy_RandomData_TestE]+0x10): undefined reference to `typeinfo for testing::Test' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTIN6snappy26Snappy_FourByteOffset_TestE[_ZTIN6snappy26Snappy_FourByteOffset_TestE]+0x10): undefined reference to `typeinfo for testing::Test' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTIN6snappy26Snappy_IOVecEdgeCases_TestE[_ZTIN6snappy26Snappy_IOVecEdgeCases_TestE]+0x10): more undefined references to `typeinfo for testing::Test' follow >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy34CorruptedTest_VerifyCorrupted_TestE[_ZTVN6snappy34CorruptedTest_VerifyCorrupted_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy34CorruptedTest_VerifyCorrupted_TestE[_ZTVN6snappy34CorruptedTest_VerifyCorrupted_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy23Snappy_SimpleTests_TestE[_ZTVN6snappy23Snappy_SimpleTests_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy23Snappy_SimpleTests_TestE[_ZTVN6snappy23Snappy_SimpleTests_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy21Snappy_MaxBlowup_TestE[_ZTVN6snappy21Snappy_MaxBlowup_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy21Snappy_MaxBlowup_TestE[_ZTVN6snappy21Snappy_MaxBlowup_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy22Snappy_RandomData_TestE[_ZTVN6snappy22Snappy_RandomData_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy22Snappy_RandomData_TestE[_ZTVN6snappy22Snappy_RandomData_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy26Snappy_FourByteOffset_TestE[_ZTVN6snappy26Snappy_FourByteOffset_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy26Snappy_FourByteOffset_TestE[_ZTVN6snappy26Snappy_FourByteOffset_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy26Snappy_IOVecEdgeCases_TestE[_ZTVN6snappy26Snappy_IOVecEdgeCases_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy26Snappy_IOVecEdgeCases_TestE[_ZTVN6snappy26Snappy_IOVecEdgeCases_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy32Snappy_IOVecLiteralOverflow_TestE[_ZTVN6snappy32Snappy_IOVecLiteralOverflow_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy32Snappy_IOVecLiteralOverflow_TestE[_ZTVN6snappy32Snappy_IOVecLiteralOverflow_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy29Snappy_IOVecCopyOverflow_TestE[_ZTVN6snappy29Snappy_IOVecCopyOverflow_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy29Snappy_IOVecCopyOverflow_TestE[_ZTVN6snappy29Snappy_IOVecCopyOverflow_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy37SnappyCorruption_TruncatedVarint_TestE[_ZTVN6snappy37SnappyCorruption_TruncatedVarint_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy37SnappyCorruption_TruncatedVarint_TestE[_ZTVN6snappy37SnappyCorruption_TruncatedVarint_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy40SnappyCorruption_UnterminatedVarint_TestE[_ZTVN6snappy40SnappyCorruption_UnterminatedVarint_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy40SnappyCorruption_UnterminatedVarint_TestE[_ZTVN6snappy40SnappyCorruption_UnterminatedVarint_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy39SnappyCorruption_OverflowingVarint_TestE[_ZTVN6snappy39SnappyCorruption_OverflowingVarint_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy39SnappyCorruption_OverflowingVarint_TestE[_ZTVN6snappy39SnappyCorruption_OverflowingVarint_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy31Snappy_ReadPastEndOfBuffer_TestE[_ZTVN6snappy31Snappy_ReadPastEndOfBuffer_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy31Snappy_ReadPastEndOfBuffer_TestE[_ZTVN6snappy31Snappy_ReadPastEndOfBuffer_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy26Snappy_ZeroOffsetCopy_TestE[_ZTVN6snappy26Snappy_ZeroOffsetCopy_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy26Snappy_ZeroOffsetCopy_TestE[_ZTVN6snappy26Snappy_ZeroOffsetCopy_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy36Snappy_ZeroOffsetCopyValidation_TestE[_ZTVN6snappy36Snappy_ZeroOffsetCopyValidation_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy36Snappy_ZeroOffsetCopyValidation_TestE[_ZTVN6snappy36Snappy_ZeroOffsetCopyValidation_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_FindMatchLength_TestE[_ZTVN6snappy27Snappy_FindMatchLength_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_FindMatchLength_TestE[_ZTVN6snappy27Snappy_FindMatchLength_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE[_ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE[_ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x20): undefined reference to `testing::Test::SetUp()' >> CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x28): undefined reference to `testing::Test::TearDown()' >> collect2: error: ld returned 1 exit status >> CMakeFiles/snappy_unittest.dir/build.make:121: recipe for target 'snappy_unittest' failed >> make[2]: *** [snappy_unittest] Error 1 >> CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/snappy_unittest.dir/all' failed >> make[1]: *** [CMakeFiles/snappy_unittest.dir/all] Error 2 >> Makefile:138: recipe for target 'all' failed >> make: *** [all] Error 2 >> >> snappy: >> Would you like to continue processing the rest of the >> queue or would you like to abort? If this failed >> package is a dependency of another package in the queue >> then it may not make sense to continue. >> >> (Y)es to continue, (N)o to abort, (R)etry the build?: n >> >> +++++++++++++++++++++++++++++++++++++++++++ >> SUMMARY LOG >> Using the SBo repository for Slackware 14.2 >> Queue Process: Download, build, and install >> >> snappy: >> MD5SUM check for snappy-1.1.8.tar.gz ... OK >> Error occurred with build. Please check the log. >> >> +++++++++++++++++++++++++++++++++++++++++++ >> >> ########################################### >> Queue process complete! >> ########################################### >> >> [?12l[?25h -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: snappy.SlackBuild URL: From matteo.bernardini at gmail.com Wed Apr 1 17:51:42 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 1 Apr 2020 19:51:42 +0200 Subject: [Slackbuilds-users] intel-microcode In-Reply-To: <20200401163648.GC4066@jdiamond-mb.acadiau.ca> References: <20200401163648.GC4066@jdiamond-mb.acadiau.ca> Message-ID: Il giorno mer 1 apr 2020 alle ore 18:36 Jim Diamond via SlackBuilds-users ha scritto: > Hi Matteo, > > I didn't... a long time ago someone suggested that I just mail the > list, rather than the individual maintainer. But I agree, cc:ing the > maintainer seems like a good idea. > > Cheers. > > Jim as a general rule the maintainer could surely clarify better that anyone else why a particular script he is maintaining is at a specific version. Matteo From atelszewski at gmail.com Wed Apr 1 18:17:07 2020 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 1 Apr 2020 20:17:07 +0200 Subject: [Slackbuilds-users] intel-microcode In-Reply-To: <20200401163520.GB4066@jdiamond-mb.acadiau.ca> References: <20200401154721.GA30034@jdiamond-mb.acadiau.ca> <20200401163520.GB4066@jdiamond-mb.acadiau.ca> Message-ID: <1a59739f-e20b-0300-657c-8e922291b650@gmail.com> > But I agree, cc:ing the maintainer seems like a good idea. > Indeed. :-D I'll take a look as soon as I can. From kingbeowulf at gmail.com Thu Apr 2 17:20:04 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 2 Apr 2020 10:20:04 -0700 Subject: [Slackbuilds-users] intel-microcode In-Reply-To: <1a59739f-e20b-0300-657c-8e922291b650@gmail.com> References: <20200401154721.GA30034@jdiamond-mb.acadiau.ca> <20200401163520.GB4066@jdiamond-mb.acadiau.ca> <1a59739f-e20b-0300-657c-8e922291b650@gmail.com> Message-ID: <9400eafe-c29d-56c8-0e87-236c5907167a@gmail.com> On 4/1/20 11:17 AM, Andrzej Telszewski wrote: > >> But I agree, cc:ing the maintainer seems like a good idea. >> > > Indeed. :-D > > I'll take a look as soon as I can. > I've noted that newer microcodes do not have support for older intel CPUs. For example, I'm still using 'microcode-20180807' for my i7-6850K on both 14.2 and current. Newer microcodes don't appear to have any updates (dropped ?) and MSI (motherboard) also has not updated the microcode since 2018-06-19. When last I attempted a newer 2019 microcode release, checking the boot log showed that the latest microcode was NOT updated. I've looked at Intel's changelogs, but it isn't clear when they dropped support. The i7-6850K is listed as discontinued on ark.intel.com TL;DR: An update may not be useful to those with older intel CPUS. Perhaps a note in the README? -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From lenardrspencer at gmail.com Fri Apr 3 13:59:34 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Fri, 3 Apr 2020 09:59:34 -0400 Subject: [Slackbuilds-users] nvidia-driver persistencd Message-ID: I am in the process of adding an rc.persistenced to nvidia-driver, and would like to run it as user/group nvidia. Looking at uid_gid.txt, I see the next available number is 365. Can I appropriate that number and have it added to the list? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Apr 3 14:04:06 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 3 Apr 2020 21:04:06 +0700 Subject: [Slackbuilds-users] nvidia-driver persistencd In-Reply-To: References: Message-ID: > I am in the process of adding an rc.persistenced to nvidia-driver, and > would like to run it as user/group nvidia. Looking at uid_gid.txt, I see > the next available number is 365. Can I appropriate that number and have > it added to the list? Thanks. 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 lenardrspencer at gmail.com Fri Apr 3 14:17:56 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Fri, 3 Apr 2020 10:17:56 -0400 Subject: [Slackbuilds-users] nvidia-driver persistencd In-Reply-To: References: Message-ID: Thanks! On Fri, Apr 3, 2020, 10:04 Willy Sudiarto Raharjo wrote: > > I am in the process of adding an rc.persistenced to nvidia-driver, and > > would like to run it as user/group nvidia. Looking at uid_gid.txt, I see > > the next available number is 365. Can I appropriate that number and have > > it added to the list? Thanks. > > Done > > > -- > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Apr 4 03:06:34 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Apr 2020 10:06:34 +0700 Subject: [Slackbuilds-users] Updates - 20200404.1 Message-ID: Sat Apr 4 02:50:46 UTC 2020 academic/fet: Updated for version 5.44.0. academic/h5utils: Fixed the md5sum. academic/sage: Fix build on x86. academic/veusz: Updated for version 3.2.1. academic/zotero: Updated for version 5.0.85. accessibility/xdotool: Fix potential security issue. audio/qmmp-plugin-pack-qt5: Updated for version 1.3.2. audio/qmmp-qt5: Updated for version 1.3.7. business/stansoft: Updated for version 7.18. desktop/numix-icon-theme-circle: Fix VERSION. desktop/numix-icon-theme: Fix VERSION. desktop/wmix: Updated for version 3.4. desktop/wmsysmon: Added (Dock Applications). development/bpython: Updated for version 0.19. development/dotnet-runtime: Updated for version 3.1.3. development/dotnet-sdk: Updated for version 3.1.201. development/gede: Updated for version 2.16.2. development/nim: Added (Programming Language). development/sbcl: Updated for version 2.0.3. development/xnedit: Updated for version 1.2.0. games/nethack: Updated for version 3.6.6. games/stella: Updated for version 6.1. gis/basemap: Removed. gis/qmapshack: Updated for version 3.0.1. graphics/flameshot: Fixed DBUS path. graphics/vuescan: Updated for version 9.7.27. ham/SDRPlay: Updated for version 2.13.1. ham/SoapyRemote: Added (Remote support for Soapy SDR). ham/SoapySDR: Updated for version 0.7.2. ham/SoapySDRPlay: Updated for version 0.2.0. libraries/SDL2: Updated for version 2.0.12. libraries/aspnetcore-runtime: Updated for version 3.1.3. libraries/ctemplate: Updated for version 2.4. libraries/libuv: Disable static. libraries/libwebp: Updated for version 1.1.0. libraries/opencl-amd: Added (OpenCL Userspace Driver). libraries/protobuf-c: Updated for version 1.3.3. libraries/wayland: Updated for version 1.18.0. multimedia/LBRY: Added (Browser to LBRY Network). multimedia/plexmediaserver: Updated for v 1.18.9.2578_513b381af. network/asterisk: Update DOWNLOAD url. network/brave-browser: Updated for version 1.5.115. network/dissenter-browser: Updated for version 1.5.114. network/dropbox: Updated for version 93.4.273. network/newsboat: Updated for version 2.19. network/palemoon-bin: Update DOWNLOAD URLs. network/palemoon: Updated for version 28.9.0.2. network/prosody-mod-cloud-notify: Updated for version hg3944. network/prosody-mod-http-upload: Updated for version hg3963. network/prosody-mod-smacks-offline: Updated for version hg3938. network/prosody-mod-smacks: Updated for version hg3956. network/shorewall-core: Updated for version 5.2.4. network/shorewall6: Updated for version 5.2.4. network/shorewall: Updated for version 5.2.4. network/signal-desktop: Updated for version 1.32.3. network/syncthing: Updated for version 1.4.0. network/t38modem: Updated for version 3.15. network/telegram: Updated for version 2.0.0. network/telegram: Updated for version 2.0.1. network/weechat: Updated for version 2.8. network/wireguard-linux-compat: Updated for version 1.0.20200330. office/gnucash-doc: Updated for version 3.9. office/gnucash: Updated for version 3.9. office/hamster: Updated for version 3.0.1. office/libreoffice-helppack: Updated for version 6.2.8.2. office/libreoffice-langpack: Updated for version 6.2.8.2. office/libreoffice: Updated for version 6.2.8.2. office/pandoc-bin: Updated for version 2.9.2.1. perl/perl-List-SomeUtils: Added (Missing methods from List::Util). perl/perl-Template-Toolkit: Updated for version 3.008. python/obspy: Removed. python/python-unicodedata2: Updated for version 13.0.0_2. python/python3-aiohttp-socks: Updated for version 0.3.7. python/python3-obspy: Updated for version 1.2.1. ruby/ruby-build: Updated for version 2.7.1. ruby/rubygem-parser: Updated for version 2.7.0.5 system/duply: Updated for version 2.2.2. system/fzf: Updated for version 0.21.1. system/gnu-unifont: Updated for version 13.0.01. system/nvidia-driver: Fix URLs. system/nvidia-legacy390-driver: Fix empty email. system/nvidia-legacy390-kernel: Fix empty email. system/pcf2bdf: Added (convert X fonts). system/rEFInd: Updated for version 0.12.0. system/refind: Updated for version 0.12.0. system/ripgrep: Updated for version 12.0.1. system/slpkg: Updated for version 3.8.7. system/symbola-font-ttf: Updated for version 13.00. system/tbsm: Update README. system/vice: Updated for version 3.4. +--------------------------+ -- 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 isaacyu1 at isaacyu1.com Sat Apr 4 07:27:16 2020 From: isaacyu1 at isaacyu1.com (=?utf-8?q?isaacyu1=40isaacyu1=2Ecom?=) Date: Sat, 04 Apr 2020 09:27:16 +0200 Subject: [Slackbuilds-users] Orphaning some SlackBuilds Message-ID: <1540-5e883700-53-5b8c3f80@31242536> I will no longer maintain the following packages (they are up-to-date): qmmp-qt5 qmmp-plugin-pack-qt5 tea image-analyzer I am no longer using them. I have other packages that I am maintaining: https://github.com/isaackwy/slackbuilds https://github.com/isaackwy/slackbuilds-data-science - Isaac -------------- next part -------------- An HTML attachment was scrubbed... URL: From korgie at gmail.com Sat Apr 4 10:16:01 2020 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Sat, 4 Apr 2020 13:16:01 +0300 Subject: [Slackbuilds-users] Orphaning some SlackBuilds In-Reply-To: <1540-5e883700-53-5b8c3f80@31242536> References: <1540-5e883700-53-5b8c3f80@31242536> Message-ID: <02912600-ED53-4ABC-9DCF-789CAB4ACA92@gmail.com> 4 ??? 2020, 10:27 ??, ? ??????? ?isaacyu1 at isaacyu1.com ? ??????: > I will no longer maintain the following packages (they are up-to-date): > qmmp-qt5 > qmmp-plugin-pack-qt5 I can take those *if* no one cares. Due to lack of time I update on demand or in problem. I hope in September I will have time and I will update all my scripts. From yth at ythogtha.org Sat Apr 4 15:26:02 2020 From: yth at ythogtha.org (Arnaud) Date: Sat, 04 Apr 2020 15:26:02 +0000 Subject: [Slackbuilds-users] Orphaning some SlackBuilds In-Reply-To: <02912600-ED53-4ABC-9DCF-789CAB4ACA92@gmail.com> References: <1540-5e883700-53-5b8c3f80@31242536> <02912600-ED53-4ABC-9DCF-789CAB4ACA92@gmail.com> Message-ID: I can take tea. Le April 4, 2020 10:16:01 AM UTC, "??????? ??????????" a ?crit : >4 ??? 2020, 10:27 ??, ? ??????? ?isaacyu1 at isaacyu1.com >? ??????: > >> I will no longer maintain the following packages (they are >up-to-date): >> qmmp-qt5 >> qmmp-plugin-pack-qt5 > >I can take those *if* no one cares. > >Due to lack of time I update on demand or in problem. > >I hope in September I will have time and I will update all my scripts. >_______________________________________________ >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/ -- Yth -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenardrspencer at gmail.com Sun Apr 5 16:38:21 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 5 Apr 2020 12:38:21 -0400 Subject: [Slackbuilds-users] dvdbackup Message-ID: Willy, I tried to email the maintainer of dvdbackup about taking it over, but it got bounced back. Do you have any problem with me taking it? I found a new patch to make it build against the new libdvdread in -current. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Apr 5 16:39:45 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Apr 2020 23:39:45 +0700 Subject: [Slackbuilds-users] dvdbackup In-Reply-To: References: Message-ID: <0193968c-8264-6c27-e8d8-61afe44ae8ec@slackbuilds.org> > I tried to email the maintainer of dvdbackup about taking it over, but it > got bounced back. Do you have any problem with me taking it? I found a > new patch to make it build against the new libdvdread in -current. Thanks. Sure, go ahead -- 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 willysr at slackbuilds.org Mon Apr 6 04:38:38 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 6 Apr 2020 11:38:38 +0700 Subject: [Slackbuilds-users] Updates - 20200406.1 Message-ID: <707cb03f-d4f2-0792-88fc-e565442f40d8@slackbuilds.org> Hi This is unscheduled public update, but we think we have good news for everyone. Dive has been doing some work on new Qt5 for a while and we think we are ready to push out his work. So for this public update, it's only qt5-related commits. We might skip some scripts during our testing, so please test your newly or existing scripts to the latest Qt5 which is now at 5.12.x branch. We will fix the remaining issue in this weeks normal public update. Big thanks Dive for updating qt5 :) Stay safe everyone Mon Apr 6 04:12:40 UTC 2020 development/qbs: Requires qt5-legacy. development/sqlitebrowser: downgrade to 3.10.1. graphics/qelectrotech: Requires qt5-legacy. graphics/scantailor: Requires qt5-legacy. libraries/PyQt5: Updated for version 5.13.2. libraries/python3-PyQt5: Updated for version 5.13.2. libraries/qt5-legacy: Update README libraries/qt5-legacy: Update to 5.9.9. libraries/qt5: Fix QtWebEngine libraries/qt5: Fix typo libraries/qt5: Remove old benchmarks file libraries/qt5: Remove patch for private includes libraries/qt5: Remove unneeded find for libqgsttools_p.prl libraries/qt5: Update README libraries/qt5: Update to 5.12.6 libraries/qt5: Updated for version 5.12.7. network/qutebrowser: Add python3-PyQtWebEngine to REQUIRES python/python2-sip: Updated for version 4.19.20. python/python3-sip: Added private sip module python/python3-sip: Updated for version 4.19.20. +--------------------------+ -- 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 tonus1 at gmail.com Mon Apr 6 10:36:03 2020 From: tonus1 at gmail.com (Tonus) Date: Mon, 6 Apr 2020 12:36:03 +0200 Subject: [Slackbuilds-users] xmpppy In-Reply-To: References: Message-ID: <20200406103603.t742mhlepptptyel@Baldr.vingolf.info> Hi all, I tried to use the xmpppy slackbuild with weechat with no luck. After a few searchs, I found that it is very outdated. I made a Slackbuild that works with current and I tried to send it to the maintainer at felipe.gonzalesr1 at gmail.com His adress is no longer working so asking here if he is around. If not, I could submit an up-to-date slackbuild (have to test it on 14.2). Please tell me when/if I can. Regards Tonus From dave at slackbuilds.org Mon Apr 6 09:42:02 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 6 Apr 2020 10:42:02 +0100 Subject: [Slackbuilds-users] xmpppy In-Reply-To: <20200406103603.t742mhlepptptyel@Baldr.vingolf.info> References: <20200406103603.t742mhlepptptyel@Baldr.vingolf.info> Message-ID: <20200406094202.GD30137@blackswan.r0t.uk> Hi Tonus, On 2020-04-06 12:36, Tonus put forth the proposition: > Hi all, > > I tried to use the xmpppy slackbuild with weechat with no luck. > After a few searchs, I found that it is very outdated. > > I made a Slackbuild that works with current and I tried to send it to the > maintainer at felipe.gonzalesr1 at gmail.com > > His adress is no longer working so asking here if he is around. If not, I > could submit an up-to-date slackbuild (have to test it on 14.2). > > Please tell me when/if I can. Just in case he's watching this list, can you wait a few days to see if he responds please? If not, then you may send in an update, and take over as maintainer if you wish. Cheers, -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Mon Apr 6 14:55:36 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 6 Apr 2020 07:55:36 -0700 (PDT) Subject: [Slackbuilds-users] PyQt5 and sip Message-ID: Seeking to update installed packages based on Saturday's list and using sbopkg I hit an issue with PyQt5. It wants sip > 4.19 and did not find it. Yet when I queried /var/log/packages for sip packages it returned: python2-sip-4.19.20-x86_64-4_SBo python3-sip-4.19.20-x86_64-1_SBo sip-4.18-x86_64-1 I assume the plain sip is for python2 but the SBo packages should be used by those applications wanting a newer version than the distribution one. What am I missing? Rich From 1.41421 at gmail.com Mon Apr 6 15:52:30 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 6 Apr 2020 09:52:30 -0600 Subject: [Slackbuilds-users] Snappy not building Message-ID: This is for the latest version of snappy (1.1.8) for 14.2, as retrieved from the link in slackbuilds.org: [ 62%] Built target snappy Scanning dependencies of target snappy_unittest [ 75%] Building CXX object CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o [ 87%] Building CXX object CMakeFiles/snappy_unittest.dir/snappy-test.cc.o [100%] Linking CXX executable snappy_unittest CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `testing::internal::scoped_ptr, std::allocator > >::reset(std::basic_stringstream, std::allocator >*) [clone .constprop.163]': snappy_unittest.cc:(.text+0x1d10): undefined reference to `testing::internal::IsTrue(bool)' CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function `snappy::Snappy_ZeroOffsetCopy_Test::TestBody()': snappy_unittest.cc:(.text+0x3319): undefined reference to `testing::Message::Message()' (scores of similar lines) CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE[_ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE]+0x28): undefined reference to `testing::Test::TearDown()' CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x20): undefined reference to `testing::Test::SetUp()' CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x28): undefined reference to `testing::Test::TearDown()' collect2: error: ld returned 1 exit status CMakeFiles/snappy_unittest.dir/build.make:121: recipe for target 'snappy_unittest' failed make[2]: *** [snappy_unittest] Error 1 CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/snappy_unittest.dir/all' failed make[1]: *** [CMakeFiles/snappy_unittest.dir/all] Error 2 Makefile:138: recipe for target 'all' failed make: *** [all] Error 2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Apr 6 17:16:47 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Apr 2020 00:16:47 +0700 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: Message-ID: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> > This is for the latest version of snappy (1.1.8) for 14.2, as retrieved > from the link in slackbuilds.org: > > > [ 62%] Built target snappy > Scanning dependencies of target snappy_unittest > [ 75%] Building CXX object > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o > [ 87%] Building CXX object CMakeFiles/snappy_unittest.dir/snappy-test.cc.o > [100%] Linking CXX executable snappy_unittest > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function > `testing::internal::scoped_ptr std::char_traits, std::allocator > >> ::reset(std::basic_stringstream, > std::allocator >*) [clone .constprop.163]': > snappy_unittest.cc:(.text+0x1d10): undefined reference to > `testing::internal::IsTrue(bool)' > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function > `snappy::Snappy_ZeroOffsetCopy_Test::TestBody()': > snappy_unittest.cc:(.text+0x3319): undefined reference to > `testing::Message::Message()' > > (scores of similar lines) > > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE[_ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE]+0x28): > undefined reference to `testing::Test::TearDown()' > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x20): > undefined reference to `testing::Test::SetUp()' > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x28): > undefined reference to `testing::Test::TearDown()' > collect2: error: ld returned 1 exit status > CMakeFiles/snappy_unittest.dir/build.make:121: recipe for target > 'snappy_unittest' failed > make[2]: *** [snappy_unittest] Error 1 > CMakeFiles/Makefile2:104: recipe for target > 'CMakeFiles/snappy_unittest.dir/all' failed > make[1]: *** [CMakeFiles/snappy_unittest.dir/all] Error 2 > Makefile:138: recipe for target 'all' failed > make: *** [all] Error 2 Did you have any package that relates to unit testing? i tested this on clean VM and it built 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 1.41421 at gmail.com Mon Apr 6 17:47:23 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 6 Apr 2020 11:47:23 -0600 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> Message-ID: Can you be more specific? I have lots of packages in my system, and I don't know which ones would be related to unit testing. I know I have not intentionally and knowingly installed anything like that though. On Mon, Apr 6, 2020 at 11:16 AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > This is for the latest version of snappy (1.1.8) for 14.2, as > retrieved > > from the link in slackbuilds.org: > > > > > > [ 62%] Built target snappy > > Scanning dependencies of target snappy_unittest > > [ 75%] Building CXX object > > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o > > [ 87%] Building CXX object > CMakeFiles/snappy_unittest.dir/snappy-test.cc.o > > [100%] Linking CXX executable snappy_unittest > > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function > > `testing::internal::scoped_ptr > std::char_traits, std::allocator > > >> ::reset(std::basic_stringstream, > > std::allocator >*) [clone .constprop.163]': > > snappy_unittest.cc:(.text+0x1d10): undefined reference to > > `testing::internal::IsTrue(bool)' > > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o: In function > > `snappy::Snappy_ZeroOffsetCopy_Test::TestBody()': > > snappy_unittest.cc:(.text+0x3319): undefined reference to > > `testing::Message::Message()' > > > > (scores of similar lines) > > > > > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE[_ZTVN6snappy33Snappy_FindMatchLengthRandom_TestE]+0x28): > > undefined reference to `testing::Test::TearDown()' > > > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x20): > > undefined reference to `testing::Test::SetUp()' > > > CMakeFiles/snappy_unittest.dir/snappy_unittest.cc.o:(.data.rel.ro._ZTVN6snappy27Snappy_VerifyCharTable_TestE[_ZTVN6snappy27Snappy_VerifyCharTable_TestE]+0x28): > > undefined reference to `testing::Test::TearDown()' > > collect2: error: ld returned 1 exit status > > CMakeFiles/snappy_unittest.dir/build.make:121: recipe for target > > 'snappy_unittest' failed > > make[2]: *** [snappy_unittest] Error 1 > > CMakeFiles/Makefile2:104: recipe for target > > 'CMakeFiles/snappy_unittest.dir/all' failed > > make[1]: *** [CMakeFiles/snappy_unittest.dir/all] Error 2 > > Makefile:138: recipe for target 'all' failed > > make: *** [all] Error 2 > > Did you have any package that relates to unit testing? > i tested this on clean VM and it built fine > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Apr 6 17:52:11 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Apr 2020 00:52:11 +0700 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> Message-ID: <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> > Can you be more specific? I have lots of packages in my system, and I don't > know which ones would be related to unit testing. I know I have not > intentionally and knowingly installed anything like that though. Can you list what packages you have that comes from SBo? -- 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 willysr at slackbuilds.org Mon Apr 6 18:11:52 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Apr 2020 01:11:52 +0700 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: > Here you are: > gtest-1.8.0-x86_64-3_SBo If my assumption is correct, this is the one that caused snappy failed to build in your machine. I can't test right now as i'm building the new Qt5 on my VM -- 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 1.41421 at gmail.com Mon Apr 6 17:58:56 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 6 Apr 2020 11:58:56 -0600 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: Here you are: BeautifulSoup4-4.6.1-x86_64-1_SBo ClusterSSH-4.09-x86_64-1_SBo GeoIP-1.6.12-x86_64-1_SBo HandBrake-1.0.7-x86_64-1_SBo Markdown-2.6.11-x86_64-1_SBo Markups-3.0.0-x86_64-1_SBo Net-SSLeay-1.81-x86_64-1_SBo OpenAL-1.18.0-x86_64-1_SBo PyQt5-5.9.2-x86_64-1_SBo Pygments-2.5.2-x86_64-1_SBo ReText-7.0.4-x86_64-1_SBo SDL2-2.0.12-x86_64-1_SBo acpica-20170531-x86_64-1_SBo android-file-transfer-3.9-x86_64-1_SBo android-studio-3.5.0_191.5791312-x86_64-1_SBo android-tools-8.0.0_r24-x86_64-1_SBo apsw-3.13.0_r1-x86_64-1_SBo argon2-20190702-x86_64-1_SBo asn1crypto-0.24.0-x86_64-1_SBo audacity-2.3.2-x86_64-1_SBo augeas-1.4.0-x86_64-1_SBo autossh-1.4g-x86_64-1_SBo avahi-0.7-x86_64-1_SBo brotli-1.0.7-x86_64-1_SBo bullet-2.89-x86_64-1_SBo calc-2.12.7.2-x86_64-1_SBo calibre-3.34.0-x86_64-1_SBo celestia-1.6.1-x86_64-2_SBo celt-0.11.3-x86_64-1_SBo cffi-1.11.5-x86_64-1_SBo chromaprint-1.4.3-x86_64-1_SBo claws-mail-3.17.3-x86_64-1_SBo clementine-1.4.0rc1-x86_64-1_SBo cmark-0.29.0-x86_64-1_SBo configobj-5.0.6-x86_64-1_SBo cryptography-2.1.4-x86_64-1_SBo cryptopp-8.2.0-x86_64-1_SBo cssselect-1.1.0-x86_64-1_SBo cssutils-1.0.2-x86_64-1_SBo ddrescue-gui-2.0.2-x86_64-1_SBo deb2tgz-0.2-noarch-1_SBo dnsmap-0.30-x86_64-1_SBo dnspython-1.16.0-x86_64-1_SBo dnstop-20121017-x86_64-1_SBo dnstracer-1.10-x86_64-1_SBo dovecot-2.3.4-x86_64-1_SBo dukpy-0.3-x86_64-1_SBo eaglemode-0.94.2-x86_64-1_SBo efl-1.21.1-x86_64-1_SBo enlightenment-0.22.4-x86_64-1_SBo enum34-1.1.6-x86_64-1_SBo fbreader-0.99.4-x86_64-1_SBo ffmpeg-3.2.4-x86_64-1_SBo flite-2.1-x86_64-2_SBo frei0r-1.7.0-x86_64-2_SBo funcsigs-1.0.2-x86_64-1_SBo geoclue2-2.4.7-x86_64-1_SBo getdevinfo-1.0.2-x86_64-1_SBo giblib-1.2.4-x86_64-3_SBo google-apputils-0.4.2-x86_64-1_SBo google-earth-7.3.2.5776-x86_64-1_SBo graphviz-2.40.1-x86_64-1_SBo gsm-1.0.13-x86_64-2_SBo gtest-1.8.0-x86_64-3_SBo gtkglext-1.2.0-x86_64-3_SBo guile1.8-1.8.8-x86_64-3_SBo hdf5-1.8.21-x86_64-1_SBo hostapd-2.9-x86_64-1_SBo html5-parser-0.4.5-x86_64-1_SBo html5lib-1.0.1-x86_64-2_SBo hwinfo-21.67-x86_64-1_SBo hyphen-2.8.8-x86_64-1_SBo idna-2.6-x86_64-1_SBo imlib2-1.6.1-x86_64-1_SBo ipaddress-1.0.22-x86_64-1_SBo jack-1.9.14-x86_64-1_SBo jansson-2.12-x86_64-1_SBo jdk-8u241-x86_64-1_SBo josepy-1.3.0-x86_64-1_SBo json-glib-1.2.8-x86_64-1_SBo keepassx-0.4.4-x86_64-1_SBo keepassxc-2.5.3-x86_64-1_SBo ladspa_sdk-1.13-x86_64-4_SBo lame-3.100-x86_64-1_SBo leptonica-1.79.0-x86_64-1_SBo letsencrypt-1.3.0-x86_64-1_SBo libass-0.14.0-x86_64-1_SBo libavc1394-0.5.4-x86_64-1_SBo libbluray-1.1.0-x86_64-1_SBo libbs2b-3.1.0-x86_64-2_SBo libdaemon-0.14-x86_64-1_SBo libdc1394-2.2.6-x86_64-1_SBo libebur128-1.2.4-x86_64-1_SBo libechonest-2.3.1-x86_64-1_SBo libetpan-1.9.3-x86_64-1_SBo libfdk-aac-2.0.1-x86_64-1_SBo libgme-0.6.2-x86_64-1_SBo libiec61883-1.2.0-x86_64-2_SBo libilbc-2.0.2-x86_64-2_SBo libinput-1.15.4-x86_64-1_SBo libmodplug-0.8.9.0-x86_64-1_SBo libreoffice-6.2.8.2-x86_64-1_SBo librsync-0.9.7-x86_64-1_SBo libsodium-1.0.18-x86_64-1_SBo libunibreak-3.0-x86_64-1_SBo libwacom-1.3-x86_64-1_SBo libwebp-1.1.0-x86_64-1_SBo libwww-perl-6.13-x86_64-1_SBo libx86emu-2.4-x86_64-1_SBo libxkbcommon-0.10.0-x86_64-1_SBo lshw-B.02.18-x86_64-1_SBo lua-5.1.5-x86_64-1_SBo luajit-2.0.5-x86_64-2_SBo lxml-4.4.1-x86_64-1_SBo lyx-2.3.4.3-x86_64-1_SBo maxima-5.39.0-x86_64-1_SBo mechanize-0.2.5-x86_64-1_SBo meson-0.52.1-x86_64-1_SBo mkchroot-1.4-noarch-1_SBo mkvtoolnix-34.0.0-x86_64-1_SBo mock-2.0.0-x86_64-2_SBo mplayer-codecs64-20061022-x86_64-1_SBo msgpack-python-0.5.6-x86_64-1_SBo multitail-6.5.0-x86_64-1_SBo ndg_httpsclient-0.5.1-x86_64-1_SBo netcdf-4.6.2-x86_64-2_SBo netifaces-0.10.9-x86_64-1_SBo ninja-1.10.0-x86_64-1_SBo obconf-2.0.4-x86_64-1_SBo opencore-amr-0.1.5-x86_64-1_SBo opencv-legacy-3.1.0-x86_64-1_SBo opera-67.0.3575.115-x86_64-1_SBo opera-ffmpeg-codecs-0.44.1-x86_64-1_SBo optipng-0.7.7-x86_64-1_SBo opus-1.3.1-x86_64-2_SBo p7zip-16.02-x86_64-2_SBo packaging-17.1-x86_64-1_SBo pangox-compat-0.0.2-x86_64-1_SBo pathlib2-2.3.2-x86_64-1_SBo pbr-5.1.1-x86_64-1_SBo pcre2-10.33-x86_64-1_SBo perl-Algorithm-Diff-1.1903-x86_64-1_SBo perl-CPAN-Changes-0.27-x86_64-1_SBo perl-Canary-Stability-2006-x86_64-1_SBo perl-Capture-Tiny-0.48-x86_64-1_SBo perl-Class-Data-Inheritable-0.08-x86_64-1_SBo perl-Devel-StackTrace-2.03-x86_64-1_SBo perl-Devel-Symdump-2.18-x86_64-1_SBo perl-Exception-Class-1.41-x86_64-1_SBo perl-ExtUtils-Config-0.008-x86_64-1_SBo perl-ExtUtils-Helpers-0.026-x86_64-1_SBo perl-ExtUtils-InstallPaths-0.012-x86_64-1_SBo perl-File-Finder-0.53-x86_64-1_SBo perl-File-Slurp-9999.19-x86_64-1_SBo perl-File-Which-1.23-x86_64-1_SBo perl-IO-HTML-1.001-x86_64-1_SBo perl-IO-Socket-SSL-2.067-x86_64-1_SBo perl-JSON-4.02-x86_64-1_SBo perl-JSON-XS-4.02-x86_64-1_SBo perl-LWP-Protocol-https-6.07-x86_64-1_SBo perl-Module-Build-0.4231-x86_64-1_SBo perl-Module-Build-Tiny-0.039-x86_64-1_SBo perl-Module-Manifest-1.08-x86_64-1_SBo perl-Mozilla-CA-20130114-x86_64-1_SBo perl-Net-LibIDN-0.12-x86_64-1_SBo perl-PAR-Dist-0.49-x86_64-1_SBo perl-Params-Util-1.07-x86_64-1_SBo perl-Pod-Coverage-0.23-x86_64-1_SBo perl-Readonly-2.05-x86_64-1_SBo perl-Sort-Naturally-1.03-x86_64-1_SBo perl-Sub-Uplevel-0.25-x86_64-1_SBo perl-Test-Differences-0.64-x86_64-2_SBo perl-Test-DistManifest-1.014-x86_64-1_SBo perl-Test-Exception-0.43-x86_64-1_SBo perl-Test-Harness-3.42-x86_64-1_SBo perl-Test-NoWarnings-1.04-x86_64-1_SBo perl-Test-PerlTidy-20130104-x86_64-1_SBo perl-Test-Pod-1.51-x86_64-1_SBo perl-Test-Pod-Coverage-1.10-x86_64-1_SBo perl-Test-RequiresInternet-0.05-x86_64-1_SBo perl-Test-Trap-0.3.2-x86_64-1_SBo perl-Text-Diff-1.43-x86_64-1_SBo perl-Text-Glob-0.11-x86_64-1_SBo perl-Tidy-20130922-x86_64-1_SBo perl-Try-Tiny-0.28-x86_64-1_SBo perl-Types-Serialiser-1.0-x86_64-1_SBo perl-X11-Protocol-Other-29-x86_64-1_SBo perl-common-sense-3.74-x86_64-1_SBo perl-data-dump-1.23-x86_64-1_SBo perl-encode-locale-1.05-x86_64-1_SBo perl-file-listing-6.04-x86_64-1_SBo perl-html-parser-3.71-x86_64-1_SBo perl-html-tagset-3.20-x86_64-1_SBo perl-http-cookies-6.01-x86_64-1_SBo perl-http-daemon-6.01-x86_64-1_SBo perl-http-date-6.02-x86_64-1_SBo perl-http-message-6.11-x86_64-1_SBo perl-http-negotiate-6.01-x86_64-1_SBo perl-lwp-mediatypes-6.02-x86_64-1_SBo perl-lwp-useragent-cached-0.08-x86_64-1_SBo perl-net-http-6.09-x86_64-1_SBo perl-test-warn-0.36-x86_64-1_SBo perl-tk-804.033-x86_64-1_SBo perl-www-robotrules-6.02-x86_64-1_SBo perl-x11-protocol-0.56-x86_64-1_SBo pip-9.0.3-x86_64-1_SBo pkgconf-1.6.3-x86_64-1_SBo podofo-0.9.5-x86_64-2_SBo protobuf-2.6.1-x86_64-1_SBo psutil-5.6.7-x86_64-1_SBo pyOpenSSL-17.5.0-x86_64-1_SBo pyasn1-0.4.4-x86_64-1_SBo pycparser-2.19-x86_64-1_SBo pyparsing-2.3.1-x86_64-1_SBo pyrfc3339-1.1-x86_64-1_SBo python-certifi-2019.9.11-x86_64-2_SBo python-chardet-3.0.4-x86_64-1_SBo python-configargparse-1.1-x86_64-1_SBo python-dateutil-2.8.0-x86_64-1_SBo python-distro-1.4.0-x86_64-1_SBo python-evdev-1.3.0-x86_64-1_SBo python-future-0.18.0-x86_64-1_SBo python-gflags-3.1.0-x86_64-1_SBo python-markdown-math-0.6-x86_64-1_SBo python-parsedatetime-2.5-x86_64-2_SBo python-requests-2.23.0-x86_64-1_SBo python-scandir-1.10.0-x86_64-1_SBo python-urllib3-1.25.7-x86_64-1_SBo python-webencodings-0.5.1-x86_64-2_SBo python2-sip-4.19.20-x86_64-1_SBo python3-3.7.2-x86_64-1_SBo python3-PyQt5-5.13.2-x86_64-1_SBo python3-attrs-19.3.0-x86_64-1_SBo python3-augeas-0.5.0-x86_64-1_SBo python3-certifi-2019.6.16-x86_64-1_SBo python3-packaging-20.1-x86_64-1_SBo python3-pyparsing-2.2.0-x86_64-1_SBo python3-pythondialog-3.5.1-x86_64-1_SBo python3-sip-4.19.20-x86_64-2_SBo python3-six-1.13.0-x86_64-1_SBo pytz-2018.3-x86_64-1_SBo pyudev-0.22.0-x86_64-1_SBo qcomicbook-0.9.0-x86_64-1_SBo qemu-4.1.0-x86_64-1_SBo qrencode-4.0.2-x86_64-1_SBo qt5-5.9.9-x86_64-1_SBo qt5-webkit-5.9.0-x86_64-1_SBo rar-5.5.0-x86_64-1_SBo rdiff-backup-1.2.8-x86_64-1_SBo reduce-algebra-20200301svn5286-x86_64-1_SBo regex-2019.08.19-x86_64-1_SBo requests-toolbelt-0.8.0-x86_64-1_SBo rtmpdump-20151223_fa8646d-x86_64-1_SBo rubberband-1.8.2-x86_64-1_SBo sage-bin-9.0-x86_64-1_SBo sbbdep-0.3.2-x86_64-1_SBo sbotools-2.7-noarch-1_SBo schroedinger-1.0.11-x86_64-1_SBo scrot-0.8-x86_64-4_SBo setuptools-scm-3.3.3-x86_64-1_SBo six-1.14.0-x86_64-1_SBo slack-4.3.2-x86_64-1_SBo speedcrunch-0.12.0-x86_64-1_SBo speex-1.2.0-x86_64-1_SBo ssvnc-1.0.30-x86_64-1_SBo stellarium-0.18.1-x86_64-1_SBo syncthing-1.4.0-x86_64-1_SBo teams-1.3.00.958-x86_64-1_SBo tesseract-4.1.1-x86_64-1_SBo texlive-2019.190626-x86_64-2_SBo texlive-docs-2019.190626-noarch-1_SBo texlive-extra-2019.190626-x86_64-1_SBo texmacs-1.99.12-x86_64-1_SBo tor-browser-9.0.7-x86_64-1_SBo twolame-0.3.13-x86_64-1_SBo unrar-5.6.1-x86_64-1_SBo unrardll-0.1.4-x86_64-1_SBo vamp-plugin-sdk-2.9.0-x86_64-1_SBo vid.stab-97c6ae2-x86_64-1_SBo virtualbox-5.0.40-x86_64-1_SBo virtualbox-extension-pack-5.0.40-x86_64-1_SBo virtualbox-kernel-5.0.40_4.4.208-x86_64-2_SBo vivaldi-2.11.1811.47-x86_64-1_SBo webcore-fonts-3.0-noarch-5_SBo webkit2gtk-2.20.5-x86_64-1_SBo werkzeug-0.16.1-x86_64-1_SBo wheel-0.33.0-x86_64-1_SBo wireshark-3.2.2-x86_64-1_SBo woff2-1.0.2-x86_64-1_SBo wxGTK3-3.0.4-x86_64-2_SBo wxMaxima-16.04.2-x86_64-1_SBo wxPython-2.8.12.1-x86_64-2_SBo wxPython4-4.0.7.post2-x86_64-1_SBo x11vnc-0.9.16-x86_64-1_SBo x264-20170225-x86_64-1_SBo x265-3.3-x86_64-1_SBo xdotool-3.20160805.1-x86_64-3_SBo xephem-3.7.7-x86_64-1_SBo xfce-hkmon-20180315git-x86_64-1_SBo xfce4-cpugraph-plugin-1.0.5-x86_64-1_SBo xfce4-datetime-plugin-0.8.0-x86_64-1_SBo xfce4-mailwatch-plugin-1.2.0-x86_64-1_SBo xfce4-netload-plugin-1.2.4-x86_64-1_SBo xfce4-sensors-plugin-1.2.6-x86_64-1_SBo xvidcore-1.3.5-x86_64-1_SBo youtube-dl-2020.03.08-x86_64-1_SBo youtube-dl-gui-0.3.8-x86_64-1_SBo youtube-viewer-3.7.4-noarch-1_SBo zeromq-4.3.2-x86_64-1_SBo zoom-linux-3.5.374815.0324-x86_64-1_SBo zope.component-4.2.1-x86_64-1_SBo zope.event-4.0.3-x86_64-1_SBo zope.interface-4.1.2-x86_64-1_SBo zvbi-0.2.35-x86_64-1_SBo On Mon, Apr 6, 2020 at 11:52 AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Can you be more specific? I have lots of packages in my system, and I > don't > > know which ones would be related to unit testing. I know I have not > > intentionally and knowingly installed anything like that though. > > Can you list what packages you have that comes from SBo? > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Mon Apr 6 18:15:59 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 6 Apr 2020 12:15:59 -0600 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: After removing gtest I was able to build snappy without any problems. After that, I was able to reinstall gtest all right. On Mon, Apr 6, 2020 at 12:11 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Here you are: > > > gtest-1.8.0-x86_64-3_SBo > > If my assumption is correct, this is the one that caused snappy failed > to build in your machine. > > I can't test right now as i'm building the new Qt5 on my VM > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Apr 6 18:18:31 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Apr 2020 01:18:31 +0700 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: <48f68037-84b7-fc79-96e0-073d68503914@slackbuilds.org> > After removing gtest I was able to build snappy without any problems. After > that, I was able to reinstall gtest all right. Yes, in previous version, there's a parameter to disable gtest, but on latest commit, the maintainer removed it since it has changed into using cmake instead of autotools https://git.slackbuilds.org/slackbuilds/commit/development/snappy?h=14.2&id=f276b9d70d1908199d0e08fc5a1f47298e0d85ba -- 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 zhu.qunying at gmail.com Mon Apr 6 18:19:28 2020 From: zhu.qunying at gmail.com (Qun-Ying) Date: Mon, 6 Apr 2020 11:19:28 -0700 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: I have the same problem, but I have gtest installed, after uninstall gtest, it compiled fine. Maybe gtest is a little old and causing the problem. On 4/6/20, Willy Sudiarto Raharjo wrote: >> Can you be more specific? I have lots of packages in my system, and I >> don't >> know which ones would be related to unit testing. I know I have not >> intentionally and knowingly installed anything like that though. > > Can you list what packages you have that comes from SBo? > > > -- > Willy Sudiarto Raharjo > > -- Qun-Ying From willysr at slackbuilds.org Mon Apr 6 18:21:54 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Apr 2020 01:21:54 +0700 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: > I have the same problem, but I have gtest installed, after uninstall > gtest, it compiled fine. > > Maybe gtest is a little old and causing the problem. It's a known issue https://github.com/google/snappy/pull/73 -- 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 dave at slackbuilds.org Mon Apr 6 18:26:47 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 6 Apr 2020 19:26:47 +0100 Subject: [Slackbuilds-users] PyQt5 and sip In-Reply-To: References: Message-ID: <20200406182647.GE30137@blackswan.r0t.uk> On 2020-04-06 07:55, Rich Shepard put forth the proposition: > Seeking to update installed packages based on Saturday's list and using > sbopkg I hit an issue with PyQt5. It wants sip > 4.19 and did not find it. > Yet when I queried /var/log/packages for sip packages it returned: > python2-sip-4.19.20-x86_64-4_SBo > python3-sip-4.19.20-x86_64-1_SBo > sip-4.18-x86_64-1 > > I assume the plain sip is for python2 but the SBo packages should be used by > those applications wanting a newer version than the distribution one. What > am I missing? Hi, python2-sip is for PyQt5 python3-sip is for python3-PyQt5 The other sip can be ignored. Which version of Qt5 did you have installed? NB: Qt5 and some other things were updated this morning so you may want to try again with the latest builds. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Mon Apr 6 18:42:38 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 6 Apr 2020 11:42:38 -0700 (PDT) Subject: [Slackbuilds-users] PyQt5 and sip In-Reply-To: <20200406182647.GE30137@blackswan.r0t.uk> References: <20200406182647.GE30137@blackswan.r0t.uk> Message-ID: On Mon, 6 Apr 2020, Dave Woodfall wrote: > python2-sip is for PyQt5 > python3-sip is for python3-PyQt5 > The other sip can be ignored. Dave, I thought this is the case. > Which version of Qt5 did you have installed? PyQt5-5.9.2-x86_64-1_SBo python3-PyQt5-5.9.2-x86_64-1_SBo > NB: Qt5 and some other things were updated this morning so you may > want to try again with the latest builds. Hmm-m-m. Looks like plain old Qt5 was removed. I'll grab the latest from the repo and build/install it. Then I'll try the Py versions again. Thanks, Rich From erich.public at protonmail.com Mon Apr 6 22:15:08 2020 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 06 Apr 2020 22:15:08 +0000 Subject: [Slackbuilds-users] python3-PyQt5 REQUIRES list Message-ID: Hi Dave, https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=443d2ef9f372f3b1b943b0c7636dfbc3d81e60fa updates the REQUIRES: -REQUIRES="python3-sip qt5-webkit" +REQUIRES="qt5-webkit python2-sip enum34" I'm guessing the REQUIRES should have been left on the old version (just qt5-webkit and python3-sip)? Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Mon Apr 6 23:35:30 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 7 Apr 2020 00:35:30 +0100 Subject: [Slackbuilds-users] python3-PyQt5 REQUIRES list In-Reply-To: References: Message-ID: <20200406233530.GF30137@blackswan.r0t.uk> On 2020-04-06 22:15, Erich Ritz put forth the proposition: > Hi Dave, > > https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=443d2ef9f372f3b1b943b0c7636dfbc3d81e60fa updates the REQUIRES: > > -REQUIRES="python3-sip qt5-webkit" > +REQUIRES="qt5-webkit python2-sip enum34" > > I'm guessing the REQUIRES should have been left on the old version (just qt5-webkit and python3-sip)? Yes indeed. Correction pushed to my qt5-5.12 branch. Thanks, -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Mon Apr 6 23:45:58 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 6 Apr 2020 16:45:58 -0700 (PDT) Subject: [Slackbuilds-users] python3-PyQt5 REQUIRES list In-Reply-To: <20200406233530.GF30137@blackswan.r0t.uk> References: <20200406233530.GF30137@blackswan.r0t.uk> Message-ID: On Tue, 7 Apr 2020, Dave Woodfall wrote: >> +REQUIRES="qt5-webkit python2-sip enum34" > Yes indeed. Correction pushed to my qt5-5.12 branch. Dave, I'm curious, and perhaps you know, why qt5-webkit is required for PyQt5 since Qt5 itself can be built with WEBENGINE=no? (Both Qt5 and PyQT5 take > 2 hours to build on my 8-core/16-thread Ryzen 7 2700 desktop with 32G RAM.) Regards, Rich From mrvladislavovich at gmail.com Tue Apr 7 05:36:42 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Tue, 7 Apr 2020 09:36:42 +0400 Subject: [Slackbuilds-users] qt5-styleplugins Message-ID: <20200407053642.GA13331@lenovo.myrequiem.net> Hi All System: Slackware64 14.2 After qt5 package upgrade to version 5.12.7 (I build this without support webengine: WEBENGINE=${WEBENGINE:-no}), I'm trying to build qt5-styleplugins package, but build fails with errors: collect2: error: ld returned 1 exit status make[4]: *** [../../../../plugins/platformthemes/libqgtk2.so] Error 1 make[3]: *** [sub-gtk2-make_first] Error 2 make[2]: *** [sub-platformthemes-make_first] Error 2 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [sub-plugins-make_first] Error 2 make: *** [sub-src-make_first] Error 2 Any ideas? From dave at slackbuilds.org Tue Apr 7 10:30:00 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 7 Apr 2020 11:30:00 +0100 Subject: [Slackbuilds-users] qt5-styleplugins In-Reply-To: <20200407053642.GA13331@lenovo.myrequiem.net> References: <20200407053642.GA13331@lenovo.myrequiem.net> Message-ID: <20200407102959.GG30137@blackswan.r0t.uk> On 2020-04-07 09:36, MyRequiem put forth the proposition: > Hi All > > System: Slackware64 14.2 > > After qt5 package upgrade to version 5.12.7 (I build this without > support webengine: WEBENGINE=${WEBENGINE:-no}), I'm trying to build > qt5-styleplugins package, but build fails with errors: > > collect2: error: ld returned 1 exit status > make[4]: *** [../../../../plugins/platformthemes/libqgtk2.so] Error 1 > make[3]: *** [sub-gtk2-make_first] Error 2 > make[2]: *** [sub-platformthemes-make_first] Error 2 > make[2]: *** Waiting for unfinished jobs.... > make[1]: *** [sub-plugins-make_first] Error 2 > make: *** [sub-src-make_first] Error 2 Hi, This will need to be built against qt5-legacy now. I've updated the REQUIRES list to reflect this. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From mrvladislavovich at gmail.com Tue Apr 7 10:54:50 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Tue, 7 Apr 2020 14:54:50 +0400 Subject: [Slackbuilds-users] qt5-styleplugins In-Reply-To: <20200407102959.GG30137@blackswan.r0t.uk> References: <20200407053642.GA13331@lenovo.myrequiem.net> <20200407102959.GG30137@blackswan.r0t.uk> Message-ID: <20200407105450.GA32676@lenovo.myrequiem.net> Re: Dave Woodfall 07.04.2020 <20200407102959.GG30137 at blackswan.r0t.uk> >On 2020-04-07 09:36, >MyRequiem put forth the proposition: >> Hi All >> >> System: Slackware64 14.2 >> >> After qt5 package upgrade to version 5.12.7 (I build this without >> support webengine: WEBENGINE=${WEBENGINE:-no}), I'm trying to build >> qt5-styleplugins package, but build fails with errors: >> >> collect2: error: ld returned 1 exit status >> make[4]: *** [../../../../plugins/platformthemes/libqgtk2.so] Error 1 >> make[3]: *** [sub-gtk2-make_first] Error 2 >> make[2]: *** [sub-platformthemes-make_first] Error 2 >> make[2]: *** Waiting for unfinished jobs.... >> make[1]: *** [sub-plugins-make_first] Error 2 >> make: *** [sub-src-make_first] Error 2 > >Hi, > >This will need to be built against qt5-legacy now. I've updated the >REQUIRES list to reflect this. > >-- >Dave > >The antibloat squad! >For those interested in no bloat, minimal desktop Linux >gopher://tty1.uk/1/?minimal-linux >http://tty1.uk/minimal-linux >#minimallinux @ chat.freenode.net Packages qt5-legace and qt5 not compatible for simultaneous installation. I understand correctly? I need to remove qt5 and install qt5-legacy in order to use the package qt5-styleplugins? >_______________________________________________ >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 lramos.prof at yahoo.com.br Tue Apr 7 11:40:48 2020 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Tue, 7 Apr 2020 08:40:48 -0300 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: <20200407114048.GB991@giustizia.org> Hello, in a previous post, I suggested a different workaround for this problem, based in some findings at Google. The starting point was the same problem with the unit test, and the solution I chose doesn't disable it. If you'd like to make an experiment, try the patch mentioned in this email: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-March/024230.html which has to be applied in the previous version of the SlackBuild (prior to 28/Mar). Anyway, it is not hard to make the changes manually, as it adds one line to the SlackBuild and creates a patch file. Hope it helps, Luiz Carlos Ramos lramos dot prof at yahoo dot com dot br On Mon, Apr 06, 2020 at 12:15:59PM -0600, Luveh Keraph wrote: > After removing gtest I was able to build snappy without any problems. After > that, I was able to reinstall gtest all right. > > On Mon, Apr 6, 2020 at 12:11 PM Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > > > > Here you are: > > > > > gtest-1.8.0-x86_64-3_SBo > > > > If my assumption is correct, this is the one that caused snappy failed > > to build in your machine. > > > > I can't test right now as i'm building the new Qt5 on my VM > > > > -- > > 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/ > From lramos.prof at yahoo.com.br Tue Apr 7 11:40:48 2020 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Tue, 7 Apr 2020 08:40:48 -0300 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> Message-ID: <20200407114048.GB991@giustizia.org> Hello, in a previous post, I suggested a different workaround for this problem, based in some findings at Google. The starting point was the same problem with the unit test, and the solution I chose doesn't disable it. If you'd like to make an experiment, try the patch mentioned in this email: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-March/024230.html which has to be applied in the previous version of the SlackBuild (prior to 28/Mar). Anyway, it is not hard to make the changes manually, as it adds one line to the SlackBuild and creates a patch file. Hope it helps, Luiz Carlos Ramos lramos dot prof at yahoo dot com dot br On Mon, Apr 06, 2020 at 12:15:59PM -0600, Luveh Keraph wrote: > After removing gtest I was able to build snappy without any problems. After > that, I was able to reinstall gtest all right. > > On Mon, Apr 6, 2020 at 12:11 PM Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > > > > Here you are: > > > > > gtest-1.8.0-x86_64-3_SBo > > > > If my assumption is correct, this is the one that caused snappy failed > > to build in your machine. > > > > I can't test right now as i'm building the new Qt5 on my VM > > > > -- > > 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/ > From dave at slackbuilds.org Tue Apr 7 11:46:53 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 7 Apr 2020 12:46:53 +0100 Subject: [Slackbuilds-users] python3-PyQt5 REQUIRES list In-Reply-To: References: <20200406233530.GF30137@blackswan.r0t.uk> Message-ID: <20200407114653.GH30137@blackswan.r0t.uk> On 2020-04-06 16:45, Rich Shepard put forth the proposition: > Dave, > > I'm curious, and perhaps you know, why qt5-webkit is required for PyQt5 > since Qt5 itself can be built with WEBENGINE=no? (Both Qt5 and PyQT5 take > > 2 hours to build on my 8-core/16-thread Ryzen 7 2700 desktop with 32G RAM.) Hi Rich, qt5-webkit was listed as required to build both PyQt5 and python3-PyQt5 when I took them over, and I left the dependency lists as they were. I've just tested building them both without it and didn't see any problems, so I've now moved qt5-webkit to `optional'. It's quite possible that something still uses qt5-webkit, but not qtwebengine. I'll be taking a look at it shortly. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Tue Apr 7 13:10:23 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 7 Apr 2020 06:10:23 -0700 (PDT) Subject: [Slackbuilds-users] python3-PyQt5 REQUIRES list In-Reply-To: <20200407114653.GH30137@blackswan.r0t.uk> References: <20200406233530.GF30137@blackswan.r0t.uk> <20200407114653.GH30137@blackswan.r0t.uk> Message-ID: On Tue, 7 Apr 2020, Dave Woodfall wrote: > qt5-webkit was listed as required to build both PyQt5 and python3-PyQt5 > when I took them over, and I left the dependency lists as they were. I've > just tested building them both without it and didn't see any problems, so > I've now moved qt5-webkit to `optional'. > > It's quite possible that something still uses qt5-webkit, but not > qtwebengine. I'll be taking a look at it shortly. Dave, Thanks very much for the explanation. Best regards, Rich From willysr at slackbuilds.org Tue Apr 7 14:11:26 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Apr 2020 21:11:26 +0700 Subject: [Slackbuilds-users] Snappy not building In-Reply-To: <20200407114048.GB991@giustizia.org> References: <8f079f44-e4b2-ea31-a98e-f45eb4d1c0dc@slackbuilds.org> <5b457da6-36f0-ec28-ba57-cd6d80417815@slackbuilds.org> <20200407114048.GB991@giustizia.org> Message-ID: > in a previous post, I suggested a different workaround for this problem, > based in some findings at Google. The starting point was the same > problem with the unit test, and the solution I chose doesn't disable it. > > If you'd like to make an experiment, try the patch mentioned in this > email: > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-March/024230.html > > which has to be applied in the previous version of the SlackBuild (prior > to 28/Mar). Anyway, it is not hard to make the changes manually, as it > adds one line to the SlackBuild and creates a patch file. I fixed it already on my branch with a much simpler patch https://git.slackbuilds.org/slackbuilds/commit/?id=094df1d52 -- 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 dave at slackbuilds.org Tue Apr 7 21:05:11 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 7 Apr 2020 22:05:11 +0100 Subject: [Slackbuilds-users] qt5-styleplugins In-Reply-To: <20200407105450.GA32676@lenovo.myrequiem.net> References: <20200407053642.GA13331@lenovo.myrequiem.net> <20200407102959.GG30137@blackswan.r0t.uk> <20200407105450.GA32676@lenovo.myrequiem.net> Message-ID: <20200407210510.GB26673@blackswan.r0t.uk> On 2020-04-07 14:54, MyRequiem put forth the proposition: > Packages qt5-legace and qt5 not compatible for simultaneous > installation. I understand correctly? I need to remove qt5 and install > qt5-legacy in order to use the package qt5-styleplugins? That's correct. You can only have one or the other installed. You could try installing 5.12.6 to see if it works. There were a few changes from 5.12.6 -> .7, but there's no guarantee. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From mrvladislavovich at gmail.com Tue Apr 7 21:11:55 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Wed, 8 Apr 2020 01:11:55 +0400 Subject: [Slackbuilds-users] qt5-styleplugins In-Reply-To: <20200407210510.GB26673@blackswan.r0t.uk> References: <20200407053642.GA13331@lenovo.myrequiem.net> <20200407102959.GG30137@blackswan.r0t.uk> <20200407105450.GA32676@lenovo.myrequiem.net> <20200407210510.GB26673@blackswan.r0t.uk> Message-ID: <20200407211155.GA13268@lenovo.myrequiem.net> Re: Dave Woodfall 08.04.2020 <20200407210510.GB26673 at blackswan.r0t.uk> >On 2020-04-07 14:54, >MyRequiem put forth the proposition: >> Packages qt5-legace and qt5 not compatible for simultaneous >> installation. I understand correctly? I need to remove qt5 and install >> qt5-legacy in order to use the package qt5-styleplugins? > >That's correct. You can only have one or the other installed. > >You could try installing 5.12.6 to see if it works. There were >a few changes from 5.12.6 -> .7, but there's no guarantee. > >-- >Dave > >The antibloat squad! >For those interested in no bloat, minimal desktop Linux >gopher://tty1.uk/1/?minimal-linux >http://tty1.uk/minimal-linux >#minimallinux @ chat.freenode.net >_______________________________________________ >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/ > Thank you very much. It's easier for me to install the old package qt5-legacy. I use qt5 package only for flacon and flameshot, so it makes no difference to me which version qt5 will be installed. From dickson.tim at googlemail.com Tue Apr 7 21:26:31 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Tue, 7 Apr 2020 22:26:31 +0100 Subject: [Slackbuilds-users] qt5 build fail Message-ID: trying to build the updated qt5? 5.12.7 (using sbopkg) is failing for me. with the error message. ninja: build stopped: subcommand failed. Makefile.gn_run:1237: recipe for target 'run_ninja' failed make[4]: *** [run_ninja] Error 1 make[4]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src/core' Makefile:82: recipe for target 'sub-gn_run-pro-make_first' failed make[3]: *** [sub-gn_run-pro-make_first] Error 2 make[3]: leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src' Makefile:80: recipe for target 'sub-core-make_first' failed make[2]: *** [sub-core-make_first] Error 2 make[2]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src' Makefile:48: recipe for target 'sub-src-make_first' failed make[1]: *** [sub-arc-make_first] Error 2 make[1]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine' Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed make: *** [module-qtwebengine-make_first] Error 2 I do have Jinja installed /var/log/packages/ninja-1.10.0-x86_64-1_SBo I am building with proprietry codecs and webengine options Anyone any ideas regards, Tim --- This email has been checked for viruses by AVG. https://www.avg.com From yalhcru at gmail.com Tue Apr 7 21:30:29 2020 From: yalhcru at gmail.com (B Watson) Date: Tue, 7 Apr 2020 17:30:29 -0400 Subject: [Slackbuilds-users] qt5 build fail In-Reply-To: References: Message-ID: On 4/7/20, Tim Dickson via SlackBuilds-users wrote: > trying to build the updated qt5 5.12.7 (using sbopkg) is failing for me. > with the error message. > > ninja: build stopped: subcommand failed. > Makefile.gn_run:1237: recipe for target 'run_ninja' failed You didn't include enough of the log... presumably, whatever actual command failed, spewed out an error message, which would have occurred before the "ninja: build stopped" line. From yalhcru at gmail.com Wed Apr 8 05:09:41 2020 From: yalhcru at gmail.com (B Watson) Date: Wed, 8 Apr 2020 01:09:41 -0400 Subject: [Slackbuilds-users] icon theme symlink optimization Message-ID: Ever notice most of the *-icon-theme builds take *forever* to build? Even though they're just copying data, with no compiling happening? The culprit is makepkg's symlink detection and doinst.sh generation. To anyone who maintains a build that contains thousands of symlinks... please consider doing this to your build. The changes come at the end of the script, just before makepkg is called. Example: cd $PKG find . -type l \ -printf '( cd %h ; rm -rf %f )\n( cd %h ; ln -sf %l %f )\n' -delete | \ sed 's,cd \./,cd ,' >> $PKG/install/doinst.sh /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} This produces an install/doinst.sh that's identical[1] to the one makepkg would have generated, but it happens a *lot* faster. If you're using an SSD for /tmp, you can expect the build to run in seconds rather than minutes. Even on a hard drive, expect at least a 2x to 10x speedup. [1] Unless there are spaces in the filenames. To decide whether or not this is worth doing to your build, first build it the usual way. Then: grep -c 'ln -sf' /tmp/SBo/package-/install/doinst.sh ...which will show you how many symlinks exist in your package. If the number's above 1000 or so (some are closer to 20,000 or 40,000), it's worth trying this speedup technique. When you do this to your build, you should keep a copy of the old install/doinst.sh from before the modification. Paste the above code (the giant find|sed stanza) into your build, run it (it should be noticeably faster), then diff the old doinst.sh and the newly-generated one. They should be identical. If not, either figure out why & fix it, or revert the change and leave the build alone. In my git branch, I've done this to these builds: Qogir-icon-theme Zafiro-icons arc-icon-theme areao43-icon-theme awoken-icon-theme faba-mono-icons faenza-icon-theme faience-icon-theme flatwoken-icon-theme kfaenza-icon-theme meliae-icon-theme numix-icon-theme numix-icon-theme-circle numix-icon-theme-square oranchelo-icon-theme papirus-icon-theme vivacious-colors-gtk-icon-theme If you're the maintainer of one of these, you may want to double-check that the generated doinst.sh hasn't changed (I checked them myself, but why take my word for it?) Before anyone asks: yes, I'm planning to send Pat a patch for him to consider adding to makepkg. However I've got to deal with the spaces-in-filenames issue first. From dickson.tim at googlemail.com Wed Apr 8 10:27:39 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 8 Apr 2020 11:27:39 +0100 Subject: [Slackbuilds-users] qt5 build issue Message-ID: extra log info from /var/log/sbopkg/sbopkg-build-log|tail -n50 [258/2543] /usr/bin/g++ -MMD -MF obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBLINK_CORE_IMPLEMENTATION=1 -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DBLINK_IMPLEMENTATION=1 -DINSIDE_BLINK -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DWTF_USE_WEBAUDIO_FFMPEG=1 -DSUPPORT_WEBGL2_COMPUTE_CONTEXT=1 -DWTF_USE_DEFAULT_RENDER_THEME=1 -DUSE_SYSTEM_LIBJPEG -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DLIBXSLT_STATIC -DUSE_SYSTEM_ZLIB=1 -I. -Igen -I../../3rdparty/chromium -Igen -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/khronos -I../../3rdparty/chromium/gpu -I../../3rdparty/chromium/third_party/libyuv/include -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/ced/src -I../../3rdparty/chromium/third_party/icu/source/common -I../../3rdparty/chromium/third_party/icu/source/i18n -I../../3rdparty/chromium/third_party/protobuf/src -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/skia/config -I../../3rdparty/chromium/skia/ext -I../../3rdparty/chromium/third_party/skia/include/c -I../../3rdparty/chromium/third_party/skia/include/config -I../../3rdparty/chromium/third_party/skia/include/core -I../../3rdparty/chromium/third_party/skia/include/effects -I../../3rdparty/chromium/third_party/skia/include/encode -I../../3rdparty/chromium/third_party/skia/include/gpu -I../../3rdparty/chromium/third_party/skia/include/images -I../../3rdparty/chromium/third_party/skia/include/lazy -I../../3rdparty/chromium/third_party/skia/include/pathops -I../../3rdparty/chromium/third_party/skia/include/pdf -I../../3rdparty/chromium/third_party/skia/include/pipe -I../../3rdparty/chromium/third_party/skia/include/ports -I../../3rdparty/chromium/third_party/skia/include/utils -I../../3rdparty/chromium/third_party/skia/src/gpu -I../../3rdparty/chromium/third_party/skia/src/sksl -I../../3rdparty/chromium/third_party/angle/include -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base -Igen/angle -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/webrtc_overrides -I../../3rdparty/chromium/third_party/webrtc -I../../3rdparty/chromium/third_party/iccjpeg -I../../3rdparty/chromium/third_party/ots/include -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/libxml/src/include -I../../3rdparty/chromium/third_party/libxml/linux/include -I../../3rdparty/chromium/third_party/libxslt/src -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-dangling-else -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-unused-parameter -fno-omit-frame-pointer -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections -g0 -isystem../../../../../../../usr/include/nss -isystem../../../../../../../usr/include/nspr -isystem ../../3rdparty/chromium/third_party/abseil-cpp -isystem../../../../../../../usr/include/libpng16 -DLIBXML_STATIC= -std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c gen/third_party/blink/renderer/core/frame/frame_jumbo_10.cc -o obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o FAILED: obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o /usr/bin/g++ -MMD -MF obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBLINK_CORE_IMPLEMENTATION=1 -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DBLINK_IMPLEMENTATION=1 -DINSIDE_BLINK -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DWTF_USE_WEBAUDIO_FFMPEG=1 -DSUPPORT_WEBGL2_COMPUTE_CONTEXT=1 -DWTF_USE_DEFAULT_RENDER_THEME=1 -DUSE_SYSTEM_LIBJPEG -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DLIBXSLT_STATIC -DUSE_SYSTEM_ZLIB=1 -I. -Igen -I../../3rdparty/chromium -Igen -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/khronos -I../../3rdparty/chromium/gpu -I../../3rdparty/chromium/third_party/libyuv/include -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/ced/src -I../../3rdparty/chromium/third_party/icu/source/common -I../../3rdparty/chromium/third_party/icu/source/i18n -I../../3rdparty/chromium/third_party/protobuf/src -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/skia/config -I../../3rdparty/chromium/skia/ext -I../../3rdparty/chromium/third_party/skia/include/c -I../../3rdparty/chromium/third_party/skia/include/config -I../../3rdparty/chromium/third_party/skia/include/core -I../../3rdparty/chromium/third_party/skia/include/effects -I../../3rdparty/chromium/third_party/skia/include/encode -I../../3rdparty/chromium/third_party/skia/include/gpu -I../../3rdparty/chromium/third_party/skia/include/images -I../../3rdparty/chromium/third_party/skia/include/lazy -I../../3rdparty/chromium/third_party/skia/include/pathops -I../../3rdparty/chromium/third_party/skia/include/pdf -I../../3rdparty/chromium/third_party/skia/include/pipe -I../../3rdparty/chromium/third_party/skia/include/ports -I../../3rdparty/chromium/third_party/skia/include/utils -I../../3rdparty/chromium/third_party/skia/src/gpu -I../../3rdparty/chromium/third_party/skia/src/sksl -I../../3rdparty/chromium/third_party/angle/include -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base -Igen/angle -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/webrtc_overrides -I../../3rdparty/chromium/third_party/webrtc -I../../3rdparty/chromium/third_party/iccjpeg -I../../3rdparty/chromium/third_party/ots/include -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/libxml/src/include -I../../3rdparty/chromium/third_party/libxml/linux/include -I../../3rdparty/chromium/third_party/libxslt/src -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-dangling-else -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-unused-parameter -fno-omit-frame-pointer -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections -g0 -isystem../../../../../../../usr/include/nss -isystem../../../../../../../usr/include/nspr -isystem ../../3rdparty/chromium/third_party/abseil-cpp -isystem../../../../../../../usr/include/libpng16 -DLIBXML_STATIC= -std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c gen/third_party/blink/renderer/core/frame/frame_jumbo_10.cc -o obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o virtual memory exhausted: Cannot allocate memory [259/2543] /usr/bin/g++ -MMD -MF obj/third_party/blink/renderer/core/exported/exported/exported_jumbo_2.o.d -DBLINK_IMPLEMENTATION=1 -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBLINK_CORE_IMPLEMENTATION=1 -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DBLINK_IMPLEMENTATION=1 -DINSIDE_BLINK -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DWTF_USE_WEBAUDIO_FFMPEG=1 -DSUPPORT_WEBGL2_COMPUTE_CONTEXT=1 -DWTF_USE_DEFAULT_RENDER_THEME=1 -DUSE_SYSTEM_LIBJPEG -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DLIBXSLT_STATIC -DUSE_SYSTEM_ZLIB=1 -I. -Igen -I../../3rdparty/chromium -Igen -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/khronos -I../../3rdparty/chromium/gpu -I../../3rdparty/chromium/third_party/libyuv/include -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/ced/src -I../../3rdparty/chromium/third_party/icu/source/common -I../../3rdparty/chromium/third_party/icu/source/i18n -I../../3rdparty/chromium/third_party/protobuf/src -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/skia/config -I../../3rdparty/chromium/skia/ext -I../../3rdparty/chromium/third_party/skia/include/c -I../../3rdparty/chromium/third_party/skia/include/config -I../../3rdparty/chromium/third_party/skia/include/core -I../../3rdparty/chromium/third_party/skia/include/effects -I../../3rdparty/chromium/third_party/skia/include/encode -I../../3rdparty/chromium/third_party/skia/include/gpu -I../../3rdparty/chromium/third_party/skia/include/images -I../../3rdparty/chromium/third_party/skia/include/lazy -I../../3rdparty/chromium/third_party/skia/include/pathops -I../../3rdparty/chromium/third_party/skia/include/pdf -I../../3rdparty/chromium/third_party/skia/include/pipe -I../../3rdparty/chromium/third_party/skia/include/ports -I../../3rdparty/chromium/third_party/skia/include/utils -I../../3rdparty/chromium/third_party/skia/src/gpu -I../../3rdparty/chromium/third_party/skia/src/sksl -I../../3rdparty/chromium/third_party/angle/include -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base -Igen/angle -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/webrtc_overrides -I../../3rdparty/chromium/third_party/webrtc -I../../3rdparty/chromium/third_party/iccjpeg -I../../3rdparty/chromium/third_party/ots/include -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/libxml/src/include -I../../3rdparty/chromium/third_party/libxml/linux/include -I../../3rdparty/chromium/third_party/libxslt/src -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-dangling-else -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-unused-parameter -fno-omit-frame-pointer -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections -g0 -isystem../../../../../../../usr/include/nss -isystem../../../../../../../usr/include/nspr -isystem ../../3rdparty/chromium/third_party/abseil-cpp -isystem../../../../../../../usr/include/libpng16 -DLIBXML_STATIC= -std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c gen/third_party/blink/renderer/core/exported/exported_jumbo_2.cc -o obj/third_party/blink/renderer/core/exported/exported/exported_jumbo_2.o [260/2543] /usr/bin/g++ -MMD -MF obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_7.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBLINK_CORE_IMPLEMENTATION=1 -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DBLINK_IMPLEMENTATION=1 -DINSIDE_BLINK -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DWTF_USE_WEBAUDIO_FFMPEG=1 -DSUPPORT_WEBGL2_COMPUTE_CONTEXT=1 -DWTF_USE_DEFAULT_RENDER_THEME=1 -DUSE_SYSTEM_LIBJPEG -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DLIBXSLT_STATIC -DUSE_SYSTEM_ZLIB=1 -I. -Igen -I../../3rdparty/chromium -Igen -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/khronos -I../../3rdparty/chromium/gpu -I../../3rdparty/chromium/third_party/libyuv/include -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/ced/src -I../../3rdparty/chromium/third_party/icu/source/common -I../../3rdparty/chromium/third_party/icu/source/i18n -I../../3rdparty/chromium/third_party/protobuf/src -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/skia/config -I../../3rdparty/chromium/skia/ext -I../../3rdparty/chromium/third_party/skia/include/c -I../../3rdparty/chromium/third_party/skia/include/config -I../../3rdparty/chromium/third_party/skia/include/core -I../../3rdparty/chromium/third_party/skia/include/effects -I../../3rdparty/chromium/third_party/skia/include/encode -I../../3rdparty/chromium/third_party/skia/include/gpu -I../../3rdparty/chromium/third_party/skia/include/images -I../../3rdparty/chromium/third_party/skia/include/lazy -I../../3rdparty/chromium/third_party/skia/include/pathops -I../../3rdparty/chromium/third_party/skia/include/pdf -I../../3rdparty/chromium/third_party/skia/include/pipe -I../../3rdparty/chromium/third_party/skia/include/ports -I../../3rdparty/chromium/third_party/skia/include/utils -I../../3rdparty/chromium/third_party/skia/src/gpu -I../../3rdparty/chromium/third_party/skia/src/sksl -I../../3rdparty/chromium/third_party/angle/include -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base -Igen/angle -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/webrtc_overrides -I../../3rdparty/chromium/third_party/webrtc -I../../3rdparty/chromium/third_party/iccjpeg -I../../3rdparty/chromium/third_party/ots/include -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/libxml/src/include -I../../3rdparty/chromium/third_party/libxml/linux/include -I../../3rdparty/chromium/third_party/libxslt/src -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-dangling-else -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-unused-parameter -fno-omit-frame-pointer -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections -g0 -isystem../../../../../../../usr/include/nss -isystem../../../../../../../usr/include/nspr -isystem ../../3rdparty/chromium/third_party/abseil-cpp -isystem../../../../../../../usr/include/libpng16 -DLIBXML_STATIC= -std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c gen/third_party/blink/renderer/core/frame/frame_jumbo_7.cc -o obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_7.o [261/2543] /usr/bin/g++ -MMD -MF obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_4.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBLINK_CORE_IMPLEMENTATION=1 -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DBLINK_IMPLEMENTATION=1 -DINSIDE_BLINK -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DWTF_USE_WEBAUDIO_FFMPEG=1 -DSUPPORT_WEBGL2_COMPUTE_CONTEXT=1 -DWTF_USE_DEFAULT_RENDER_THEME=1 -DUSE_SYSTEM_LIBJPEG -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DLIBXSLT_STATIC -DUSE_SYSTEM_ZLIB=1 -I. -Igen -I../../3rdparty/chromium -Igen -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/khronos -I../../3rdparty/chromium/gpu -I../../3rdparty/chromium/third_party/libyuv/include -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/ced/src -I../../3rdparty/chromium/third_party/icu/source/common -I../../3rdparty/chromium/third_party/icu/source/i18n -I../../3rdparty/chromium/third_party/protobuf/src -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/skia/config -I../../3rdparty/chromium/skia/ext -I../../3rdparty/chromium/third_party/skia/include/c -I../../3rdparty/chromium/third_party/skia/include/config -I../../3rdparty/chromium/third_party/skia/include/core -I../../3rdparty/chromium/third_party/skia/include/effects -I../../3rdparty/chromium/third_party/skia/include/encode -I../../3rdparty/chromium/third_party/skia/include/gpu -I../../3rdparty/chromium/third_party/skia/include/images -I../../3rdparty/chromium/third_party/skia/include/lazy -I../../3rdparty/chromium/third_party/skia/include/pathops -I../../3rdparty/chromium/third_party/skia/include/pdf -I../../3rdparty/chromium/third_party/skia/include/pipe -I../../3rdparty/chromium/third_party/skia/include/ports -I../../3rdparty/chromium/third_party/skia/include/utils -I../../3rdparty/chromium/third_party/skia/src/gpu -I../../3rdparty/chromium/third_party/skia/src/sksl -I../../3rdparty/chromium/third_party/angle/include -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base -Igen/angle -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/webrtc_overrides -I../../3rdparty/chromium/third_party/webrtc -I../../3rdparty/chromium/third_party/iccjpeg -I../../3rdparty/chromium/third_party/ots/include -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/libxml/src/include -I../../3rdparty/chromium/third_party/libxml/linux/include -I../../3rdparty/chromium/third_party/libxslt/src -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-dangling-else -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-unused-parameter -fno-omit-frame-pointer -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections -g0 -isystem../../../../../../../usr/include/nss -isystem../../../../../../../usr/include/nspr -isystem ../../3rdparty/chromium/third_party/abseil-cpp -isystem../../../../../../../usr/include/libpng16 -DLIBXML_STATIC= -std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c gen/third_party/blink/renderer/core/frame/frame_jumbo_4.cc -o obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_4.o ninja: build stopped: subcommand failed. Makefile.gn_run:1237: recipe for target 'run_ninja' failed make[4]: *** [run_ninja] Error 1 make[4]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src/core' Makefile:82: recipe for target 'sub-gn_run-pro-make_first' failed make[3]: *** [sub-gn_run-pro-make_first] Error 2 make[3]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src/core' Makefile:80: recipe for target 'sub-core-make_first' failed make[2]: *** [sub-core-make_first] Error 2 make[2]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src' Makefile:48: recipe for target 'sub-src-make_first' failed make[1]: *** [sub-src-make_first] Error 2 make[1]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine' Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed make: *** [module-qtwebengine-make_first] Error 2 qt5: Would you like to continue processing the rest of the queue or would you like to abort?? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: n +++++++++++++++++++++++++++++++++++++++++++ SUMMARY LOG Using the SBo repository for Slackware 14.2 Queue Process:? Download, build, and install qt5: ? MD5SUM check for qt-everywhere-src-5.12.7.tar.xz ... OK ? Error occurred with build.? Please check the log. qt5: ? MD5SUM check for qt-everywhere-src-5.12.7.tar.xz ... OK ? Error occurred with build.? Please check the log. +++++++++++++++++++++++++++++++++++++++++++ ########################################### ????????? Queue process complete! ########################################### looking closer, it looks like I'm out of virtual memory. I don't have a swap partition on my build vm, but it has allocated 6GB ram, but that? seems insufficient for this version of qt5. I'm re-running it with 8GB ram, and will post back many hours later if it succeeds. It may be worth mentioning RAM requirements if it works with 8GB, (and if not, I'll try with 10GB). Regards, Tim --- This email has been checked for viruses by AVG. https://www.avg.com From dave at slackbuilds.org Wed Apr 8 13:22:20 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 8 Apr 2020 14:22:20 +0100 Subject: [Slackbuilds-users] qt5 build issue In-Reply-To: References: Message-ID: <20200408132220.GA26844@blackswan.r0t.uk> On 2020-04-08 11:27, Slackbuilds Users put forth the proposition: > looking closer, it looks like I'm out of virtual memory. I don't have a swap > partition on my build vm, but it has allocated 6GB ram, but that? seems > insufficient for this version of qt5. I'm re-running it with 8GB ram, and > will post back many hours later if it succeeds. It may be worth mentioning > RAM requirements if it works with 8GB, (and if not, I'll try with 10GB). > Regards, Tim If this is a space issue, try uninstalling any previous version of Qt first. -- /Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From glenn.becker at gmail.com Wed Apr 8 13:43:27 2020 From: glenn.becker at gmail.com (Glenn Becker) Date: Wed, 8 Apr 2020 09:43:27 -0400 Subject: [Slackbuilds-users] hope this isn't a stupid question Message-ID: Hi - I am thinking of buying a smallish laptop to dedicate to Slackware. I've usually done double-, triple- and occasionally more- boot machines, but my distro-hopping is (I think!) coming to an end. And I was wondering ... if I ran slack-current as my main system, but ran slack-stable in a VM, could I use the latter to work on my SlackBuilds? I'm by no means well-versed in what is possible or impossible with VMs. Thanks, Glenn Becker ------------------------------------------------------------------------------------------------------------------------ "Doctor, I have come to ask you to tell me everything you know about the night." - Djuna Barnes, *Nightwood* ------------------------------------------------------------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Wed Apr 8 13:49:13 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 8 Apr 2020 14:49:13 +0100 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: <20200408134913.GA11703@blackswan.r0t.uk> On 2020-04-08 09:43, Glenn Becker put forth the proposition: > Hi - > > I am thinking of buying a smallish laptop to dedicate to Slackware. I've > usually done double-, triple- and occasionally more- boot machines, but my > distro-hopping is (I think!) coming to an end. > > And I was wondering ... if I ran slack-current as my main system, but ran > slack-stable in a VM, could I use the latter to work on my SlackBuilds? I'm > by no means well-versed in what is possible or impossible with VMs. There shouldn't be a problem. It may likely be a bit slower than on bare metal though. -- /dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From alex at dcclost.com Wed Apr 8 13:49:30 2020 From: alex at dcclost.com (Alexander Grotewohl) Date: Wed, 8 Apr 2020 13:49:30 +0000 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: Simple answer is yes. Treat the VM as if it were another machine. That said it's possible to do the slackbuild dev/testing on slackware-current, but it takes quite a bit more effort (and library duplication, which you'd be doing in the VM anyways) I'm sure someone else can offer more information on the second option if it appeals to you. -- Alexander Grotewohl https://dcclost.com ________________________________ From: SlackBuilds-users on behalf of Glenn Becker Sent: Wednesday, April 8, 2020 9:43:27 AM To: SlackBuilds.org Users List Subject: [Slackbuilds-users] hope this isn't a stupid question Hi - I am thinking of buying a smallish laptop to dedicate to Slackware. I've usually done double-, triple- and occasionally more- boot machines, but my distro-hopping is (I think!) coming to an end. And I was wondering ... if I ran slack-current as my main system, but ran slack-stable in a VM, could I use the latter to work on my SlackBuilds? I'm by no means well-versed in what is possible or impossible with VMs. Thanks, Glenn Becker ------------------------------------------------------------------------------------------------------------------------ "Doctor, I have come to ask you to tell me everything you know about the night." - Djuna Barnes, Nightwood ------------------------------------------------------------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rellis at dp100.com Wed Apr 8 14:01:44 2020 From: rellis at dp100.com (Richard Ellis) Date: Wed, 8 Apr 2020 10:01:44 -0400 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: <20200408140144.GK27591@d820.dp100.com> On Wed, Apr 08, 2020 at 09:43:27AM -0400, Glenn Becker wrote: >And I was wondering ... if I ran slack-current as my main system, but >ran slack-stable in a VM, could I use the latter to work on my >SlackBuilds? Yes. The VM is essentially a second, independnent, machine. I do this myself when I update my Slackbuilds to verify that they work in a plain Slackware install. Whip up a VM (VirtualBox), install 14.2 with "install all", then verify that the script builds and runs. That way I can verify that they work in a plain Slackware install with nothing else added, and I can verify exactly what other dependencies they *really* need. I have enough slackbuilds installed on my regular system that it would be easy to miss a dependency because I'd already installed that package for some other reason. You can still do the main work on your regular system (where all your config and editor choices will already be available and setup to your liking) then test in the 'plain vanilla Slackware' VM at the end to verify that no problems exist. From mcmurchy1917techy at btinternet.com Wed Apr 8 14:30:56 2020 From: mcmurchy1917techy at btinternet.com (mcmurchy1917techy) Date: Wed, 8 Apr 2020 15:30:56 +0100 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: Hi Glenn If you're going to use slack-current as your main system why would you want to have slack-stable running in a VM? I would have thought you would have wanted to develop your SlackBuilds in a VM? machine running slack-current. Alex On 08/04/2020 14:43, Glenn Becker wrote: > Hi - > > I am thinking of buying a smallish laptop to dedicate to Slackware. > I've usually done double-, triple- and occasionally more- boot > machines, but my distro-hopping is (I think!) coming to an end. > > And I was wondering ... if I ran slack-current as my main system, but > ran slack-stable in a VM, could I use the latter to work on my > SlackBuilds? I'm by no means well-versed in what is possible or > impossible with VMs. > > Thanks, > > Glenn Becker > > ------------------------------------------------------------------------------------------------------------------------ > "Doctor, I have come to ask you to tell me everything you know about > the night." > - Djuna Barnes, /Nightwood/ > ------------------------------------------------------------------------------------------------------------------------ > > _______________________________________________ > 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 slackbuilds.org Wed Apr 8 14:34:16 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 8 Apr 2020 15:34:16 +0100 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: <20200408143416.GC11703@blackswan.r0t.uk> On 2020-04-08 15:30, Slackbuilds Users put forth the proposition: > Hi Glenn > > If you're going to use slack-current as your main system why would you want > to have slack-stable running in a VM? I would have thought you would have > wanted to develop your SlackBuilds in a VM? machine running slack-current. > > Alex If I might interject ;) We need to make sure things build and are usable in the latest stable release, not on -current. /dave > On 08/04/2020 14:43, Glenn Becker wrote: > > Hi - > > > > I am thinking of buying a smallish laptop to dedicate to Slackware. I've > > usually done double-, triple- and occasionally more- boot machines, but > > my distro-hopping is (I think!) coming to an end. > > > > And I was wondering ... if I ran slack-current as my main system, but > > ran slack-stable in a VM, could I use the latter to work on my > > SlackBuilds? I'm by no means well-versed in what is possible or > > impossible with VMs. > > > > Thanks, > > > > Glenn Becker > > > > ------------------------------------------------------------------------------------------------------------------------ > > "Doctor, I have come to ask you to tell me everything you know about the > > night." > > - Djuna Barnes, /Nightwood/ > > ------------------------------------------------------------------------------------------------------------------------ > > > > _______________________________________________ > > 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/ > -- /dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From glenn.becker at gmail.com Wed Apr 8 14:44:30 2020 From: glenn.becker at gmail.com (Glenn Becker) Date: Wed, 8 Apr 2020 10:44:30 -0400 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: Hi - My understanding was that SlackBuilds were 'guaranteed' to run on -stable rather than -current. Maybe that's wrong, or has changed? G ------------------------------------------------------------------------------------------------------------------------ "Doctor, I have come to ask you to tell me everything you know about the night." - Djuna Barnes, *Nightwood* ------------------------------------------------------------------------------------------------------------------------ On Wed, Apr 8, 2020 at 10:31 AM mcmurchy1917techy via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hi Glenn > > If you're going to use slack-current as your main system why would you > want to have slack-stable running in a VM? I would have thought you would > have wanted to develop your SlackBuilds in a VM machine running > slack-current. > > Alex > > On 08/04/2020 14:43, Glenn Becker wrote: > > Hi - > > I am thinking of buying a smallish laptop to dedicate to Slackware. I've > usually done double-, triple- and occasionally more- boot machines, but my > distro-hopping is (I think!) coming to an end. > > And I was wondering ... if I ran slack-current as my main system, but ran > slack-stable in a VM, could I use the latter to work on my SlackBuilds? I'm > by no means well-versed in what is possible or impossible with VMs. > > Thanks, > > Glenn Becker > > > ------------------------------------------------------------------------------------------------------------------------ > "Doctor, I have come to ask you to tell me everything you know about the > night." > - Djuna Barnes, > *Nightwood* > > ------------------------------------------------------------------------------------------------------------------------ > > _______________________________________________ > SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Wed Apr 8 14:46:40 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 8 Apr 2020 15:46:40 +0100 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: <20200408144640.GD11703@blackswan.r0t.uk> On 2020-04-08 10:44, Glenn Becker put forth the proposition: > Hi - > > My understanding was that SlackBuilds were 'guaranteed' to run on -stable > rather than -current. Maybe that's wrong, or has changed? You are correct. That hasn't changed. > G > ------------------------------------------------------------------------------------------------------------------------ > "Doctor, I have come to ask you to tell me everything you know about the > night." > - Djuna Barnes, > *Nightwood* > ------------------------------------------------------------------------------------------------------------------------ > > > On Wed, Apr 8, 2020 at 10:31 AM mcmurchy1917techy via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: > > > Hi Glenn > > > > If you're going to use slack-current as your main system why would you > > want to have slack-stable running in a VM? I would have thought you would > > have wanted to develop your SlackBuilds in a VM machine running > > slack-current. > > > > Alex > > > > On 08/04/2020 14:43, Glenn Becker wrote: > > > > Hi - > > > > I am thinking of buying a smallish laptop to dedicate to Slackware. I've > > usually done double-, triple- and occasionally more- boot machines, but my > > distro-hopping is (I think!) coming to an end. > > > > And I was wondering ... if I ran slack-current as my main system, but ran > > slack-stable in a VM, could I use the latter to work on my SlackBuilds? I'm > > by no means well-versed in what is possible or impossible with VMs. > > > > Thanks, > > > > Glenn Becker > > > > > > ------------------------------------------------------------------------------------------------------------------------ > > "Doctor, I have come to ask you to tell me everything you know about the > > night." > > - Djuna Barnes, > > *Nightwood* > > > > ------------------------------------------------------------------------------------------------------------------------ > > > > _______________________________________________ > > SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://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/ > > > > > _______________________________________________ > 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/ > -- /dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dickson.tim at googlemail.com Wed Apr 8 15:24:26 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 8 Apr 2020 16:24:26 +0100 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: <25452ff4-c756-969f-62f4-ed2293177435@googlemail.com> i use qemu 4.0 to do just that (4.1 requires stuff from current, and I didn't want to pollute my host slack stable) something like qemu-img create -f qcow2 /data/images/slack14.2_64bit_base.qcow2 100G will create a virtual disk drive 100G which you can snapshot, if you want to reverse changes, configuring the bridge in /etc/rc.d/rc.inet1.conf create /etc/qemu/bridge.conf? containing a single line allow br0 and using nohup qemu-system-x86_64 -cpu qemu64 -smp 4 -m 8G -drive file=/data/images/slack14.2_64bit_base.qcow2,format=qcow2 -cdrom /mnt/smb1/slackware/iso/slackware64-14.2-install-dvd.iso -boot c -net nic,macaddr=02:00:00:11:11:18,model=i82551 -net bridge,br=br0 -enable-kvm -k en-gb -display vnc=:1 -monitor telnet:localhost:7100,server,nowait,nodelay & runs a vm with 8GB ram (assuming you have enough real ram to give it that), a virtual dvd drive with the slack installer iso - for installing, and setting the output to vnc and telnet. this way you can telnet to see the console tty, or/and vnc (port 5901 to see it and any xwindows stuff you run, and off course if you set it up, you can telnet or ssh to the vm directly as well. obviously change the paths to suit your preferred setup. Regards, Tim On 08/04/2020 14:43, Glenn Becker wrote: > Hi - > > I am thinking of buying a smallish laptop to dedicate to Slackware. > I've usually done double-, triple- and occasionally more- boot > machines, but my distro-hopping is (I think!) coming to an end. > > And I was wondering ... if I ran slack-current as my main system, but > ran slack-stable in a VM, could I use the latter to work on my > SlackBuilds? I'm by no means well-versed in what is possible or > impossible with VMs. > > Thanks, > > Glenn Becker > > ------------------------------------------------------------------------------------------------------------------------ > "Doctor, I have come to ask you to tell me everything you know about > the night." > - Djuna Barnes, /Nightwood/ > ------------------------------------------------------------------------------------------------------------------------ > > _______________________________________________ > 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/ > --- This email has been checked for viruses by AVG. https://www.avg.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Wed Apr 8 16:11:00 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 8 Apr 2020 17:11:00 +0100 Subject: [Slackbuilds-users] qt5 build fail In-Reply-To: References: Message-ID: <4b904d90-910d-eef8-2c0f-3f9cd8f9da45@googlemail.com> build completed successfully on my vm with 8gb RAM allocated, (and 12G+ free disk space) so swap+ram should be>7GB to complete. - may be more with docs. thanks all. Tim --- This email has been checked for viruses by AVG. https://www.avg.com From dickson.tim at googlemail.com Wed Apr 8 16:26:25 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 8 Apr 2020 17:26:25 +0100 Subject: [Slackbuilds-users] Qt5 ... newer versions available In-Reply-To: <20200330234447.GA2250@jdiamond-mb.acadiau.ca> References: <20191011204532.GA30117@jdiamond-mb.acadiau.ca> <20191012020329.GE19897@blackholeuniverse.ru> <20200329153912.GA14718@jdiamond-mb.acadiau.ca> <20200329235120.GA14920@blackswan.r0t.uk> <20200330143102.GB5283@jdiamond-mb.acadiau.ca> <20200330154509.GB14920@blackswan.r0t.uk> <20200330234447.GA2250@jdiamond-mb.acadiau.ca> Message-ID: <90a41a10-aeee-3e0f-8f07-12e7b7ea0263@googlemail.com> will there be a new version of qt5-webkit in line with the new qt5 ? thanks, Tim --- This email has been checked for viruses by AVG. https://www.avg.com From dave at slackbuilds.org Wed Apr 8 16:30:36 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 8 Apr 2020 17:30:36 +0100 Subject: [Slackbuilds-users] Qt5 ... newer versions available In-Reply-To: <90a41a10-aeee-3e0f-8f07-12e7b7ea0263@googlemail.com> References: <20191011204532.GA30117@jdiamond-mb.acadiau.ca> <20191012020329.GE19897@blackholeuniverse.ru> <20200329153912.GA14718@jdiamond-mb.acadiau.ca> <20200329235120.GA14920@blackswan.r0t.uk> <20200330143102.GB5283@jdiamond-mb.acadiau.ca> <20200330154509.GB14920@blackswan.r0t.uk> <20200330234447.GA2250@jdiamond-mb.acadiau.ca> <90a41a10-aeee-3e0f-8f07-12e7b7ea0263@googlemail.com> Message-ID: <20200408163035.GG11703@blackswan.r0t.uk> On 2020-04-08 17:26, Tim Dickson put forth the proposition: > will there be a new version of qt5-webkit in line with the new qt5 ? I'll be looking at that soon. There has just been an update of Qt LTS to 5.12.8 today, so I'm currently doing a test build of that. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From stairs.flowers at gmail.com Wed Apr 8 13:58:18 2020 From: stairs.flowers at gmail.com (Andrew Payne) Date: Wed, 8 Apr 2020 09:58:18 -0400 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: <65e36012-dd5e-18be-6414-5b05de4d8fed@gmail.com> Glenn this setup is very effective.? I use it too -- I run current and I keep a partition with a stock 14.2 VM and -current VM (both Virtualbox).? When it's time to test, I clone the VM, do my testing, then destroy it. I keep the 'master' VMs up to date but stock in all other respects so the clones are clean testing environments. On 4/8/20 9:43 AM, Glenn Becker wrote: > Hi - > > I am thinking of buying a smallish laptop to dedicate to Slackware. > I've usually done double-, triple- and occasionally more- boot > machines, but my distro-hopping is (I think!) coming to an end. > > And I was wondering ... if I ran slack-current as my main system, but > ran slack-stable in a VM, could I use the latter to work on my > SlackBuilds? I'm by no means well-versed in what is possible or > impossible with VMs. > > Thanks, > > Glenn Becker > > ------------------------------------------------------------------------------------------------------------------------ > "Doctor, I have come to ask you to tell me everything you know about > the night." > - Djuna Barnes, /Nightwood/ > ------------------------------------------------------------------------------------------------------------------------ > > _______________________________________________ > 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 glenn.becker at gmail.com Wed Apr 8 17:06:23 2020 From: glenn.becker at gmail.com (Glenn Becker) Date: Wed, 8 Apr 2020 13:06:23 -0400 Subject: [Slackbuilds-users] hope this isn't a stupid question In-Reply-To: References: Message-ID: Thank you everyone for the responses! ------------------------------------------------------------------------------------------------------------------------ "Doctor, I have come to ask you to tell me everything you know about the night." - Djuna Barnes, *Nightwood* ------------------------------------------------------------------------------------------------------------------------ On Wed, Apr 8, 2020 at 9:43 AM Glenn Becker wrote: > Hi - > > I am thinking of buying a smallish laptop to dedicate to Slackware. I've > usually done double-, triple- and occasionally more- boot machines, but my > distro-hopping is (I think!) coming to an end. > > And I was wondering ... if I ran slack-current as my main system, but ran > slack-stable in a VM, could I use the latter to work on my SlackBuilds? I'm > by no means well-versed in what is possible or impossible with VMs. > > Thanks, > > Glenn Becker > > > ------------------------------------------------------------------------------------------------------------------------ > "Doctor, I have come to ask you to tell me everything you know about the > night." > - Djuna Barnes, > *Nightwood* > > ------------------------------------------------------------------------------------------------------------------------ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Apr 9 03:03:39 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 9 Apr 2020 10:03:39 +0700 Subject: [Slackbuilds-users] qt5 build fail In-Reply-To: <4b904d90-910d-eef8-2c0f-3f9cd8f9da45@googlemail.com> References: <4b904d90-910d-eef8-2c0f-3f9cd8f9da45@googlemail.com> Message-ID: <33a031e4-0601-5da3-3314-d15837a5ae83@slackbuilds.org> > build completed successfully on my vm with 8gb RAM allocated, (and 12G+ > free disk space) > so swap+ram should be>7GB to complete. - may be more with docs. I managed to build it on my low spec VM with just 2 GB of RAM with 8GB SWAP :) it just takes longer -- 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 fernando.lopezjr at gmail.com Fri Apr 10 00:46:54 2020 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 9 Apr 2020 18:46:54 -0600 Subject: [Slackbuilds-users] SLACKBUILDS: UNetbootin upgrade? Message-ID: is there any way you could push an update for this app? thank you! -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Fri Apr 10 14:43:42 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Fri, 10 Apr 2020 08:43:42 -0600 Subject: [Slackbuilds-users] BeautifulSoup4 not building Message-ID: PYTHON_3_PRE_3_2 = (sys.version_info[0] == 3 and sys.version_info < (3,2)) @@ -40,17 +40,17 @@ class TestConstructor(SoupTest): def test_short_unicode_input(self): --- py3k/bs4/tests/test_tree.py (originalWARNING: couldn't encode py3k/bs4/tests/test_tree.py's diff for your terminal RefactoringTool: Files that were modified: RefactoringTool: py3k/bs4/__init__.py RefactoringTool: py3k/bs4/dammit.py RefactoringTool: py3k/bs4/diagnose.py RefactoringTool: py3k/bs4/element.py RefactoringTool: py3k/bs4/testing.py RefactoringTool: py3k/bs4/builder/__init__.py RefactoringTool: py3k/bs4/builder/_html5lib.py RefactoringTool: py3k/bs4/builder/_htmlparser.py RefactoringTool: py3k/bs4/builder/_lxml.py RefactoringTool: py3k/bs4/tests/__init__.py RefactoringTool: py3k/bs4/tests/test_builder_registry.py RefactoringTool: py3k/bs4/tests/test_docs.py RefactoringTool: py3k/bs4/tests/test_html5lib.py RefactoringTool: py3k/bs4/tests/test_htmlparser.py RefactoringTool: py3k/bs4/tests/test_lxml.py RefactoringTool: py3k/bs4/tests/test_soup.py RefactoringTool: py3k/bs4/tests/test_tree.py ) +++ py3k/bs4/tests/test_tree.py (refactored) @@ -71,13 +71,13 @@ self.assertEqual(soup.find("b").string, "2") def test_unicode_text_find(self): OK, conversion is done. Now running the unit tests. .................................................................................................................................../tmp/SBo/beautifulsoup4-4.6.1/py3k/bs4/builder/_htmlparser.py:78: UserWarning: don't crash warnings.warn(msg) ..................................................................F...F.................................................................................................................................................................................................................................................................................. ====================================================================== FAIL: test_nested_namespaces (tests.test_lxml.LXMLXMLTreeBuilderSmokeTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/SBo/beautifulsoup4-4.6.1/py3k/bs4/testing.py", line 665, in test_nested_namespaces self.assertEqual(doc, soup.encode()) AssertionError: b'\n\n\n[56 chars]tml>' != b'\n<[55 chars]tml>' ---------------------------------------------------------------------- Ran 476 tests in 0.522s FAILED (failures=2) BeautifulSoup4: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Apr 10 18:27:35 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Apr 2020 01:27:35 +0700 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: References: Message-ID: > BeautifulSoup4: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: Works fine here BeautifulSoup4: MD5SUM check for beautifulsoup4-4.6.1.tar.gz ... OK Building package BeautifulSoup4-4.6.1-x86_64-1_SBo.tgz ... OK Installing package BeautifulSoup4-4.6.1-x86_64-1_SBo.tgz ... OK -- 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 willysr at slackbuilds.org Sat Apr 11 03:05:29 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Apr 2020 10:05:29 +0700 Subject: [Slackbuilds-users] Updates - 20200411.1 Message-ID: Hi as promised, we delivered another fixes to Qt5-related builds PLUS now qt5-webkit is also pushed to 5.212.0, matching the one we have in -current. B. Watson is currently working on an optimization effort on packages that contains a lot of symlinks (mostly icons). Hopefully we can push that on next public update. Stay safe everyone :) Sat Apr 11 02:30:39 UTC 2020 academic/gri: Update HOMEPAGE. audio/fluidsynth: Updated for version 2.1.1, new maintainer. audio/pd: Updated for version 0.50_2. audio/qsynth: Updated for version 0.6.2. desktop/boston-icon-theme: Updated for version 0.6. desktop/gkrellm-themes: Added (Themes for GKrellM). desktop/numix-icon-theme-circle: Speed up symlink creation. desktop/numix-icon-theme: Speed up symlink creation. development/Sphinx: Updated for version 2.4.4. development/bas55: Updated for version 1.18. development/byacc: Updated for version 20200330. development/codeblocks: Updated for version 20.03. development/crystal-lang: Added (a Ruby-like programming language). development/minikube: Updated for version 1.9.2. development/nim: Updated for version 1.2.0. development/octant: Added (Web Interface for Kubernetes). development/rustup: Support building newer versions. development/snappy: Fix build with gtest installed. development/uz80as: Updated for version 1.11. development/velero: Updated for version 1.3.2. development/vscode-bin: Updated for version 1.44.0. games/speed-dreams: Updated for version 2.2.2_r6553. games/starfighter: Updated for version 2.1. gis/OWSLib: Updated for version 0.19.2. gis/pyproj: Updated for version 2.6.0. graphics/vuescan: Update MD5SUMs. libraries/digimend-kernel-drivers: Added (Tablet drivers). libraries/hdf: Updated for version 4.2.15. libraries/libQuotient: Updated for version 0.5.3.2. libraries/qt5-webkit: Updated for version 5.212.0_alpha4. libraries/skalibs: Updated for version 2.9.2.1. libraries/tbb: Updated for version 2020u2. multimedia/dvdbackup: Fix build on -current. multimedia/plexmediaserver: Updated for v 1.19.1.2630_72c16a276. network/Quaternion: Updated for version 0.0.9.4e. network/axel: Updated for version 2.17.8. network/dropbox: Updated for version 94.4.384. network/insync: Updated for version 3.1.2.40785. network/netcat-openbsd: Updated for version 1.217-1. network/nordvpn: Updated for version 3.7.0. network/opera-developer: Updated for version 69.0.3653.0. network/opera: Updated for version 67.0.3575.137. network/prosody-mod-smacks: Updated for version hg3968. network/protonmail-bridge: Added (ProtonMail Bridge). network/qutebrowser-tox: Update OpenSSL version. network/signal-desktop: Updated for version 1.33.0. network/slack: Updated for version 4.4.2. network/tor-browser: Updated for version 9.0.9. network/wireguard-linux-compat: Updated for version 1.0.20200401. network/wireshark: Updated for version 3.2.3. network/zoom-linux: Updated for version 3.5.383291.0407. office/CherryTree: Updated for version 0.39.2. office/onlyoffice-desktopeditors: Updated for version 5.5.1. office/xournal: Update HOMEPAGE. perl/perl-Clone: Updated for version 0.43. perl/perl-Data-Dumper-Concise: Update HOMEPAGE. perl/perl-Data-Validate-IP: Update HOMEPAGE. perl/perl-HTML-Tidy: Update HOMEPAGE. perl/perl-IO-Socket-SSL: Updated for version 2.068. perl/perl-Moose: Updated for version 2.2012. perl/perl-Scalar-List-Utils: Updated for version 1.54. perl/perl-String-Random: Update HOMEPAGE. perl/perl-String-Scanf: Update HOMEPAGE. perl/perl-Test-HexDifferences: Update HOMEPAGE. perl/perl-namespace-autoclean: Updated for version 0.29. python/bleach: Updated for version 3.1.4. python/python-importlib_metadata: Updated for 1.6.0. python/python-soupsieve: Added (A CSS selector implementation). python/python3-ipython: Updated for version 7.13.0. python/python3-jupyter-ipykernel: Updated for version 5.2.0. python/python3-soupsieve: Added (A CSS selector implementation). python/python3-tornado: Updated for version 6.0.4. python/python3-wcwidth: Updated for version 0.1.9. python/sphinxcontrib-devhelp: Updated for version 1.0.2. python/sphinxcontrib-qthelp: Updated for version 1.0.3. python/sphinxcontrib-serializinghtml: Updated for version 1.1.4. ruby/rubygem-parser: Updated for version 2.7.1.0. ruby/sequel: Updated for version 5.31.0. system/apache-tomcat: Updated for version 7.0.103. system/bleachbit: Updated for version 3.9.0. system/kbfs: Updated for version 5.3.1_20200320154633. system/kexec-tools: Updated for version 2.0.20. system/keybase: Updated for version 5.3.1. system/libtrash: Added (trash can). system/netdata: Updated for version 1.21.0. system/nvidia-driver: added rc.nvidia-persistenced. system/nvidia-kernel: New maintainer. system/nvidia-legacy390-driver: added rc.nvidia-persistenced. system/nvidia-legacy390-kernel: New maintainer. system/psuinfo: Added (Custom system usage info). system/tbsm: Fix README. system/telegraf: Updated for version 1.14.0. +--------------------------+ -- 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 sborg63 at disroot.org Sat Apr 11 10:42:39 2020 From: sborg63 at disroot.org (sborg63) Date: Sat, 11 Apr 2020 11:42:39 +0100 Subject: [Slackbuilds-users] re BeautifulSoup4 not building Message-ID: <20200411114239.6ef49c53@knotsUL> Yes, this happens if there have been package that needs to be removed first and is still there when you want to compile Beautifulsoup. Saw this with llvm when building inkscape: https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page140.html#post6047307 Best to remove any existing packages in the tree you want to compile AFTER BeatifulSoup first before compiling Beautiful Soup... Hth Rob From falsetti at clansco.org Sat Apr 11 15:27:01 2020 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Sat, 11 Apr 2020 17:27:01 +0200 Subject: [Slackbuilds-users] python3-PyQt5-5.13.2 Message-ID: <20200411172701.35b5d2133c4cab8487acf42e@clansco.org> Hi, python3-PyQt5-5.9.2 to 5.13.2 configure.py: error: '/usr/include/python3.7' is not a directory $ ls /usr/include/python3. python3.6/ python3.7m/ where is my mistake ? thanks in advance From dave at slackbuilds.org Sat Apr 11 15:51:05 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 11 Apr 2020 16:51:05 +0100 Subject: [Slackbuilds-users] python3-PyQt5-5.13.2 In-Reply-To: <20200411172701.35b5d2133c4cab8487acf42e@clansco.org> References: <20200411172701.35b5d2133c4cab8487acf42e@clansco.org> Message-ID: <20200411155105.GD31407@blackswan.r0t.uk> On 2020-04-11 17:27, Fr?d?ric Falsetti put forth the proposition: > Hi, > python3-PyQt5-5.9.2 to 5.13.2 > configure.py: error: '/usr/include/python3.7' is not a directory > $ ls /usr/include/python3. > python3.6/ python3.7m/ > > where is my mistake ? > thanks in advance That looks like you might have an old version of python3-sip installed. I'm guessing the only contents of /usr/include/python3.6/ is sip.h? -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sat Apr 11 15:55:04 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 11 Apr 2020 16:55:04 +0100 Subject: [Slackbuilds-users] python3-PyQt5-5.13.2 In-Reply-To: <20200411155105.GD31407@blackswan.r0t.uk> References: <20200411172701.35b5d2133c4cab8487acf42e@clansco.org> <20200411155105.GD31407@blackswan.r0t.uk> Message-ID: <20200411155504.GE31407@blackswan.r0t.uk> On 2020-04-11 16:51, Dave Woodfall put forth the proposition: > On 2020-04-11 17:27, > Fr?d?ric Falsetti put forth the proposition: > > Hi, > > python3-PyQt5-5.9.2 to 5.13.2 > > configure.py: error: '/usr/include/python3.7' is not a directory > > $ ls /usr/include/python3. > > python3.6/ python3.7m/ > > > > where is my mistake ? > > thanks in advance > > That looks like you might have an old version of python3-sip > installed. > > I'm guessing the only contents of /usr/include/python3.6/ is sip.h? It looks like I didn't push my fix for REQUIRES in time. The actual dependencies should be qt5-webkit and python3-sip. The old dependencies had python2-sip, which is wrong. Sorry about that that. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sat Apr 11 16:57:20 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 11 Apr 2020 17:57:20 +0100 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: References: Message-ID: <20200411165720.GF31407@blackswan.r0t.uk> On 2020-04-10 08:43, Luveh Keraph <1.41421 at gmail.com> put forth the proposition: > PYTHON_3_PRE_3_2 = (sys.version_info[0] == 3 and sys.version_info < (3,2)) > @@ -40,17 +40,17 @@ > class TestConstructor(SoupTest): > > def test_short_unicode_input(self): > --- py3k/bs4/tests/test_tree.py (originalWARNING: couldn't encode > py3k/bs4/tests/test_tree.py's diff for your terminal > RefactoringTool: Files that were modified: > RefactoringTool: py3k/bs4/__init__.py > RefactoringTool: py3k/bs4/dammit.py > RefactoringTool: py3k/bs4/diagnose.py > RefactoringTool: py3k/bs4/element.py > RefactoringTool: py3k/bs4/testing.py > RefactoringTool: py3k/bs4/builder/__init__.py > RefactoringTool: py3k/bs4/builder/_html5lib.py > RefactoringTool: py3k/bs4/builder/_htmlparser.py > RefactoringTool: py3k/bs4/builder/_lxml.py > RefactoringTool: py3k/bs4/tests/__init__.py > RefactoringTool: py3k/bs4/tests/test_builder_registry.py > RefactoringTool: py3k/bs4/tests/test_docs.py > RefactoringTool: py3k/bs4/tests/test_html5lib.py > RefactoringTool: py3k/bs4/tests/test_htmlparser.py > RefactoringTool: py3k/bs4/tests/test_lxml.py > RefactoringTool: py3k/bs4/tests/test_soup.py > RefactoringTool: py3k/bs4/tests/test_tree.py > ) > +++ py3k/bs4/tests/test_tree.py (refactored) > @@ -71,13 +71,13 @@ > self.assertEqual(soup.find("b").string, "2") > > def test_unicode_text_find(self): > > OK, conversion is done. > Now running the unit tests. > .................................................................................................................................../tmp/SBo/beautifulsoup4-4.6.1/py3k/bs4/builder/_htmlparser.py:78: > UserWarning: don't crash > warnings.warn(msg) > ..................................................................F...F.................................................................................................................................................................................................................................................................................. > ====================================================================== > FAIL: test_nested_namespaces (tests.test_lxml.LXMLXMLTreeBuilderSmokeTest) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/tmp/SBo/beautifulsoup4-4.6.1/py3k/bs4/testing.py", line 665, in > test_nested_namespaces > self.assertEqual(doc, soup.encode()) > AssertionError: b'\n\n xmlns:="http://n[99 chars]ent>' > > ====================================================================== > FAIL: test_real_xhtml_document (tests.test_lxml.LXMLXMLTreeBuilderSmokeTest) > A real XHTML document should come out *exactly* the same as it went in. > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/tmp/SBo/beautifulsoup4-4.6.1/py3k/bs4/testing.py", line 654, in > test_real_xhtml_document > soup.encode("utf-8"), markup) > AssertionError: b' chars]xmlns:="http://www.w3.org/1999/xhtml">\n[56 > chars]tml>' != b' chars]xmlns="http://www.w3.org/1999/xhtml">\n<[55 > chars]tml>' > > ---------------------------------------------------------------------- > Ran 476 tests in 0.522s > > FAILED (failures=2) Did you find a solution to this? I get the same error when building in a chroot, but it builds fine on the host machine. It doesn't seem to matter it bs4 is already installed or not. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From lists at osh.id.au Sat Apr 11 17:27:15 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 11 Apr 2020 10:27:15 -0700 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: <20200411165720.GF31407@blackswan.r0t.uk> References: <20200411165720.GF31407@blackswan.r0t.uk> Message-ID: <4c16da97-f99a-4005-84d0-65dcfd8a9467@www.fastmail.com> On Sat, 11 Apr 2020, at 9:57 AM, Dave Woodfall wrote: > Did you find a solution to this? > > I get the same error when building in a chroot, but it builds fine on > the host machine. It doesn't seem to matter it bs4 is already > installed or not. I can't get the build to fail on -current or 14.2 (without or without BeautifulSoup4 installed). Seems to build even in a chroot (with this https://gitlab.com/oshd/sbuild/ anyway). -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sat Apr 11 17:42:01 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 11 Apr 2020 18:42:01 +0100 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: <4c16da97-f99a-4005-84d0-65dcfd8a9467@www.fastmail.com> References: <20200411165720.GF31407@blackswan.r0t.uk> <4c16da97-f99a-4005-84d0-65dcfd8a9467@www.fastmail.com> Message-ID: <20200411174201.GH31407@blackswan.r0t.uk> On 2020-04-11 10:27, David O'Shaughnessy put forth the proposition: > On Sat, 11 Apr 2020, at 9:57 AM, Dave Woodfall wrote: > > Did you find a solution to this? > > > > I get the same error when building in a chroot, but it builds fine on > > the host machine. It doesn't seem to matter it bs4 is already > > installed or not. > > I can't get the build to fail on -current or 14.2 (without or without BeautifulSoup4 installed). Seems to build even in a chroot (with this https://gitlab.com/oshd/sbuild/ anyway). It looks like it might be related to lxml. For me it fails if it's installed before building bs4. Can anyone else confirm that? -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From falsetti at clansco.org Sat Apr 11 17:56:59 2020 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Sat, 11 Apr 2020 19:56:59 +0200 Subject: [Slackbuilds-users] python3-PyQt5-5.13.2 In-Reply-To: <20200411155504.GE31407@blackswan.r0t.uk> References: <20200411172701.35b5d2133c4cab8487acf42e@clansco.org> <20200411155105.GD31407@blackswan.r0t.uk> <20200411155504.GE31407@blackswan.r0t.uk> Message-ID: <20200411195659.cf88a9a34b8458dd5703ec6f@clansco.org> many thanks Dave ! le Sat, 11 Apr 2020 16:55:04 +0100 Dave Woodfall a ?crit : > On 2020-04-11 16:51, > Dave Woodfall put forth the proposition: > > On 2020-04-11 17:27, > > Fr?d?ric Falsetti put forth the proposition: > > > Hi, > > > python3-PyQt5-5.9.2 to 5.13.2 > > > configure.py: error: '/usr/include/python3.7' is not a directory > > > $ ls /usr/include/python3. > > > python3.6/ python3.7m/ > > > > > > where is my mistake ? > > > thanks in advance > > > > That looks like you might have an old version of python3-sip > > installed. > > > > I'm guessing the only contents of /usr/include/python3.6/ is sip.h? > > It looks like I didn't push my fix for REQUIRES in time. > > The actual dependencies should be qt5-webkit and python3-sip. > > The old dependencies had python2-sip, which is wrong. Sorry about > that that. > > -- > Dave > > The antibloat squad! > For those interested in no bloat, minimal desktop Linux > gopher://tty1.uk/1/?minimal-linux > http://tty1.uk/minimal-linux > #minimallinux @ chat.freenode.net From yalhcru at gmail.com Sat Apr 11 18:08:12 2020 From: yalhcru at gmail.com (B Watson) Date: Sat, 11 Apr 2020 14:08:12 -0400 Subject: [Slackbuilds-users] Updates - 20200411.1 In-Reply-To: References: Message-ID: On 4/10/20, Willy Sudiarto Raharjo wrote: > > B. Watson is currently working on an optimization effort on packages > that contains a lot of symlinks (mostly icons). Hopefully we can push > that on next public update. I also have to apologize for the fluidsynth update, I didn't mean to push that yet. It works, but at least one build (fluidsynth-dssi) doesn't compile with the new fluidsynth, and I haven't yet tested all the builds that list fluidsynth as optional. This should be fixed in the next public update. Sorry about the mess. From matteo.bernardini at gmail.com Sat Apr 11 18:14:03 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 11 Apr 2020 20:14:03 +0200 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: <20200411174201.GH31407@blackswan.r0t.uk> References: <20200411165720.GF31407@blackswan.r0t.uk> <4c16da97-f99a-4005-84d0-65dcfd8a9467@www.fastmail.com> <20200411174201.GH31407@blackswan.r0t.uk> Message-ID: Il giorno sab 11 apr 2020 alle ore 19:42 Dave Woodfall ha scritto: > > On 2020-04-11 10:27, > David O'Shaughnessy put forth the proposition: > > On Sat, 11 Apr 2020, at 9:57 AM, Dave Woodfall wrote: > > > Did you find a solution to this? > > > > > > I get the same error when building in a chroot, but it builds fine on > > > the host machine. It doesn't seem to matter it bs4 is already > > > installed or not. > > > > I can't get the build to fail on -current or 14.2 (without or without BeautifulSoup4 installed). Seems to build even in a chroot (with this https://gitlab.com/oshd/sbuild/ anyway). > > It looks like it might be related to lxml. For me it fails if it's > installed before building bs4. Can anyone else confirm that? https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page50.html#post6090620 From yalhcru at gmail.com Sat Apr 11 18:14:10 2020 From: yalhcru at gmail.com (B Watson) Date: Sat, 11 Apr 2020 14:14:10 -0400 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: <20200411174201.GH31407@blackswan.r0t.uk> References: <20200411165720.GF31407@blackswan.r0t.uk> <4c16da97-f99a-4005-84d0-65dcfd8a9467@www.fastmail.com> <20200411174201.GH31407@blackswan.r0t.uk> Message-ID: On 4/11/20, Dave Woodfall wrote: > > It looks like it might be related to lxml. For me it fails if it's > installed before building bs4. Can anyone else confirm that? Confirmed. Nice catch! From 1.41421 at gmail.com Sat Apr 11 18:44:33 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 11 Apr 2020 12:44:33 -0600 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: References: <20200411165720.GF31407@blackswan.r0t.uk> <4c16da97-f99a-4005-84d0-65dcfd8a9467@www.fastmail.com> <20200411174201.GH31407@blackswan.r0t.uk> Message-ID: I was able to build it on a different system, and I just installed the resulting package in the target one. Other people contributed workarounds to this forum though. On Sat, Apr 11, 2020 at 12:14 PM B Watson wrote: > On 4/11/20, Dave Woodfall wrote: > > > > It looks like it might be related to lxml. For me it fails if it's > > installed before building bs4. Can anyone else confirm that? > > Confirmed. Nice catch! > _______________________________________________ > 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 slackbuilds.org Sat Apr 11 18:52:34 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 11 Apr 2020 19:52:34 +0100 Subject: [Slackbuilds-users] BeautifulSoup4 not building In-Reply-To: References: <20200411165720.GF31407@blackswan.r0t.uk> <4c16da97-f99a-4005-84d0-65dcfd8a9467@www.fastmail.com> <20200411174201.GH31407@blackswan.r0t.uk> Message-ID: <20200411185234.GI31407@blackswan.r0t.uk> On 2020-04-11 20:14, Matteo Bernardini put forth the proposition: > https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page50.html#post6090620 Ah thanks for that. I'll see if I can find a workaround. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Sun Apr 12 13:33:40 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 12 Apr 2020 06:33:40 -0700 (PDT) Subject: [Slackbuilds-users] vokoscreen (2.5.0) Message-ID: Yesterday I wrote to Harald Achitz, the listed maintainer for vokoscreen, because the link to the source file is broken. He responded this way: "It seems the author has removed the github repo and all traces of the 2.x downloads from his home page. There is not a lot I can do about it, except pointing to the fact how potential unstable slackbulids are if they do not archive the source files for their recipes one of the very many reasons I do not use Slackware anymore. "And it seems that vokoscreen has been forgotten to transfer to an new owner, after I told the slackbuilds mailing list that I cannot maintain my build scripts anymore. "I can only recommend you to a) inform the author of vokoscreen about what he did when he put down the old repos and made a new one instead. b) tell slackbuilds that vokoscreen is without maintainer Because, I was in contact with the author, and I think that it is no problem to simply switch to the new version, since it will include functionality the 2.5 did not have (wayland for example.) "sorry for not having better news for you." If vokoscreen 3.x becomes available I want to look at it but now I'm going to learn obs-studio since that's installed and working. Stay healthy, all, Rich From rshepard at appl-ecosys.com Sun Apr 12 13:34:32 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 12 Apr 2020 06:34:32 -0700 (PDT) Subject: [Slackbuilds-users] Updates - 20200411.1 In-Reply-To: References: Message-ID: On Sat, 11 Apr 2020, B Watson wrote: > I also have to apologize for the fluidsynth update, I didn't mean to push > that yet. It works, but at least one build (fluidsynth-dssi) doesn't > compile with the new fluidsynth, and I haven't yet tested all the builds > that list fluidsynth as optional. B, I've spent much of today downloading all the vlc dependencies I don't have installed (all 48 of 'em). fluidsynth is the first in line. VLC built, installs, and loads just fine. Regards, Rich From mickski56 at hotmail.com Sun Apr 12 13:44:18 2020 From: mickski56 at hotmail.com (mickski56) Date: Sun, 12 Apr 2020 14:44:18 +0100 Subject: [Slackbuilds-users] Updates - 20200411.1 In-Reply-To: References: Message-ID: > On 4/10/20, Willy Sudiarto Raharjo wrote: > > > > B. Watson is currently working on an optimization effort on packages > > that contains a lot of symlinks (mostly icons). Hopefully we can > > push that on next public update. > > I also have to apologize for the fluidsynth update, I didn't mean > to push that yet. It works, but at least one build (fluidsynth-dssi) > doesn't compile with the new fluidsynth, and I haven't yet tested all > the builds that list fluidsynth as optional. > There is a fork of fluidsynth-dssi at https://github.com/schnitzeltony/fluidsynth-dssi That builds just fine hth From fellype at gmail.com Sun Apr 12 14:47:20 2020 From: fellype at gmail.com (Fellype) Date: Sun, 12 Apr 2020 11:47:20 -0300 Subject: [Slackbuilds-users] vokoscreen (2.5.0) In-Reply-To: References: Message-ID: Hi Rich, Em dom., 12 de abr. de 2020 ?s 10:33, Rich Shepard escreveu: > > If vokoscreen 3.x becomes available I want to look at it but now I'm going > to learn obs-studio since that's installed and working. > > vokoscreen is now vokoscreenNG. And the latest version is 3.0.3. I'm using it on -current. But I think it will build fine on 14.2. The SlackBuild I'm using is attached to this email (I guess, I don't know if attachments works on lists), just in case someone wants to test it on 14.2. The deps must be checked - OK? Note: I don't want to be the maintainer for this package, at least for now. Best wishes Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: vokoscreenNG.tar.gz Type: application/gzip Size: 2595 bytes Desc: not available URL: From rshepard at appl-ecosys.com Sun Apr 12 14:56:24 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 12 Apr 2020 07:56:24 -0700 (PDT) Subject: [Slackbuilds-users] vokoscreen (2.5.0) In-Reply-To: References: Message-ID: On Sun, 12 Apr 2020, Fellype wrote: > vokoscreen is now vokoscreenNG. Fellype, Yes, I saw that on his github page. > And the latest version is 3.0.3. I downloaded the zip file; it's just 3.0. Did you clone the github repo instead? I'll build and install it when I know I'm working with the same source as you. Thanks, Rich From rshepard at appl-ecosys.com Sun Apr 12 15:04:46 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 12 Apr 2020 08:04:46 -0700 (PDT) Subject: [Slackbuilds-users] vokoscreen (2.5.0) In-Reply-To: References: Message-ID: On Sun, 12 Apr 2020, Rich Shepard wrote: > I'll build and install it when I know I'm working with the same source as > you. Ah-ha! I changed the version number in the build script to 3.0 (to match the tarball) and it built, installed, and loaded just fine. The window frame does show it's version 3.0.3. Now I'm waiting for my webcams and headset to arrive and I'll learn how to use vokoscreenNG. It certainly looks simpler to learn than obs-studio even if it doesn't have all the bells and whistles of the latter. It will likely be all I need. Thanks again and stay healthy, Rich From yalhcru at gmail.com Sun Apr 12 19:05:52 2020 From: yalhcru at gmail.com (B Watson) Date: Sun, 12 Apr 2020 15:05:52 -0400 Subject: [Slackbuilds-users] Updates - 20200411.1 In-Reply-To: References: Message-ID: On 4/12/20, mickski56 wrote: > There is a fork of fluidsynth-dssi at > https://github.com/schnitzeltony/fluidsynth-dssi > > That builds just fine Yep, that's what I used... it'll be in the next public update. Was afraid I'd have to invent a "fluidsynth-legacy" version 1 build, but it looks like everything's going to work out OK, either upgrading to a new version or a small amount of patching. From yalhcru at gmail.com Sun Apr 12 19:18:16 2020 From: yalhcru at gmail.com (B Watson) Date: Sun, 12 Apr 2020 15:18:16 -0400 Subject: [Slackbuilds-users] vokoscreen (2.5.0) In-Reply-To: References: Message-ID: On 4/12/20, Rich Shepard wrote: > > "And it seems that vokoscreen has been forgotten to transfer to an new > owner, after I told the slackbuilds mailing list that I cannot maintain my > build scripts anymore. This is a common thread... someone abandons their builds, posts to the mailing list saying so. People step up and say "I'll take over X, Y, and Z" but then they don't follow up by sending in an update with their name/email in the .info file. Months or years later, the old maintainer is still listed as the current one, and he keeps getting emails for stuff he's already publically abandoned. And the new maintainer has possibly forgotten he's supposed to be the maintainer... I'm as guilty as anyone of this, volunteering to take stuff and then forgetting I said it. So there's 2 ways to fix this: 1. As soon as you volunteer to take over a build, send in an update with your name/email in the .info file. Do this immediately (or sooner!), because if you wait a couple days, you'll forget. 2. The admins monitoring the list can change the .info files and push the changes to git. As much as I hate policy and process, I think we should decide on one or the other approach and stick to it rigorously. Thoughts? This is open to the whole list, not just admins. From kev4321 at fastmail.fm Mon Apr 13 21:48:41 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Mon, 13 Apr 2020 16:48:41 -0500 Subject: [Slackbuilds-users] libgnomeprintui-2.18.6 build fails. Message-ID: Trying to install whyteboard (0.41.1) through sbopkg. libgnomeprintui-2.18.6 build fails.? This excerpt seems to identify the problem as " libtool: link: `/tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la' is not a valid libtool archive " /usr/bin/grep: /tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la: No such file or directory /usr/bin/sed: can't read /tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la: No such file or directory libtool: link: `/tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la' is not a valid libtool archive Makefile:463: recipe for target 'libgnomeprintui-2-2.la' failed make[4]: *** [libgnomeprintui-2-2.la] Error 1 make[4]: Leaving directory '/tmp/SBo/libgnomeprintui-2.18.6/libgnomeprintui' Makefile:585: recipe for target 'all-recursive' failed sbopkg sqf file: ### whytebaord.sqf? (0.41.1) ### libgnomecups libgnomecanvas libgnomeprint libgnomeprintui libmspack wxPython | GNOMEPRINT=yes whyteboard Thanks, Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricardo at palmtx.com.ar Mon Apr 13 22:05:39 2020 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Mon, 13 Apr 2020 19:05:39 -0300 Subject: [Slackbuilds-users] vokoscreen (2.5.0) In-Reply-To: References: Message-ID: <202004131905.39215.ricardo@palmtx.com.ar> El Domingo 12/04/2020 a las 16:18, B Watson escribi?: > On 4/12/20, Rich Shepard wrote: > > "And it seems that vokoscreen has been forgotten to transfer to an new > > owner, after I told the slackbuilds mailing list that I cannot maintain > > my build scripts anymore. > > This is a common thread... someone abandons their builds, posts to the > mailing list saying so. People step up and say "I'll take over X, Y, > and Z" but then they don't follow up by sending in an update with their > name/email in the .info file. Months or years later, the old maintainer > is still listed as the current one, and he keeps getting emails for stuff > he's already publically abandoned. And the new maintainer has possibly > forgotten he's supposed to be the maintainer... > > I'm as guilty as anyone of this, volunteering to take stuff and then > forgetting I said it. So there's 2 ways to fix this: > > 1. As soon as you volunteer to take over a build, send in an update > with your name/email in the .info file. Do this immediately (or > sooner!), because if you wait a couple days, you'll forget. > > 2. The admins monitoring the list can change the .info files and > push the changes to git. > > As much as I hate policy and process, I think we should decide on one > or the other approach and stick to it rigorously. > > Thoughts? This is open to the whole list, not just admins. I was meaning to ask about this, since I'm also guilty of this :) If I send an update with only my info changed: should I bump the BUILD version or not? I mean, there's no need to upgrade the package if the only thing that changes is the maintainer's name an email but I was never sure and so never sent the updates (and some of my newly adopted packages actually need an update but life gets in the way). If the SBo admins want to do it for me, this is my only adopted slackbuild that doesn't have my info: misc/grc (orphaned - no maintainer) These other 3 I could take over: libraries/librsync (Lyle Sigurdson, mailed on 07/01/2020, no answer) network/urlgrabber (Javier Rojas, mailed on 07/01/2020, no answer) system/acpitool (Rodney Cobb, mailed on 07/01/2020, no answer) 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 lenardrspencer at gmail.com Tue Apr 14 01:35:24 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Mon, 13 Apr 2020 21:35:24 -0400 Subject: [Slackbuilds-users] libgnomeprintui-2.18.6 build fails. In-Reply-To: References: Message-ID: Which nvidia driver are you using? On Mon, Apr 13, 2020, 17:48 Kevin McCormick wrote: > Trying to install whyteboard (0.41.1) through sbopkg. > > > libgnomeprintui-2.18.6 build fails. This excerpt seems to identify the > problem as > " libtool: link: `/tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la' is > not a valid libtool archive " > > /usr/bin/grep: /tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la: No such > file or directory > /usr/bin/sed: can't read > /tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la: No such file or directory > libtool: link: `/tmp/SBo/package-nvidia-driver/usr/lib64/libGL.la' is not > a valid libtool archive > Makefile:463: recipe for target 'libgnomeprintui-2-2.la' failed > make[4]: *** [libgnomeprintui-2-2.la] Error 1 > make[4]: Leaving directory > '/tmp/SBo/libgnomeprintui-2.18.6/libgnomeprintui' > Makefile:585: recipe for target 'all-recursive' failed > > sbopkg sqf file: > ### whytebaord.sqf (0.41.1) > ### > libgnomecups > libgnomecanvas > libgnomeprint > libgnomeprintui > libmspack > wxPython | GNOMEPRINT=yes > whyteboard > > Thanks, > Kevin > _______________________________________________ > 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 Apr 14 01:37:26 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 14 Apr 2020 08:37:26 +0700 Subject: [Slackbuilds-users] vokoscreen (2.5.0) In-Reply-To: <202004131905.39215.ricardo@palmtx.com.ar> References: <202004131905.39215.ricardo@palmtx.com.ar> Message-ID: > If I send an update with only my info changed: should I bump the BUILD version > or not? > > I mean, there's no need to upgrade the package if the only thing that changes > is the maintainer's name an email but I was never sure and so never sent the > updates (and some of my newly adopted packages actually need an update but > life gets in the way). > > If the SBo admins want to do it for me, this is my only adopted slackbuild > that doesn't have my info: > > misc/grc (orphaned - no maintainer) > > > These other 3 I could take over: > > libraries/librsync (Lyle Sigurdson, mailed on 07/01/2020, no answer) > network/urlgrabber (Javier Rojas, mailed on 07/01/2020, no answer) > system/acpitool (Rodney Cobb, mailed on 07/01/2020, no answer) Sure, send them and make a note of it that you are taking over Also, no need to bump the BUILD if it's just maintainer changes -- 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 falsetti at clansco.org Tue Apr 14 09:42:39 2020 From: falsetti at clansco.org (=?UTF-8?B?RnLDqWTDqXJpYw==?= Falsetti) Date: Tue, 14 Apr 2020 11:42:39 +0200 Subject: [Slackbuilds-users] lmms-1.1.90 Message-ID: <20200414114239.99f13bd924c99aa664e3398a@clansco.org> Hi, I cant' build lmms-1.1.90, plugins/sf2_player I have fluid-soundfont-3.1_5-noarch-1_SBo fluidsynth-2.1.1-i586-1_SBo [ 77%] Building CXX object plugins/sf2_player/CMakeFiles/sf2player.dir/sf2_player.cpp.o cd /tmp/SBo/lmms-1.1.90/build/plugins/sf2_player && /usr/bin/c++ -DPLUGIN_NAME=sf2player -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_XML_LIB -Dsf2player_EXPORTS -isystem /usr/lib/qt/include -isystem /usr/lib/qt/include/QtGui -isystem /usr/lib/qt/include/QtXml -isystem /usr/lib/qt/include/QtCore -I/tmp/SBo/lmms-1.1.90/build/plugins/sf2_player -I/tmp/SBo/lmms-1.1.90/build -I/tmp/SBo/lmms-1.1.90/include -I/tmp/SBo/lmms-1.1.90/src/gui -fno-exceptions -Wall -Werror=unused-function -Wno-sign-compare -Wno-strict-overflow -Wno-array-bounds -O2 -march=i486 -mtune=i686 -Wno-error -fPIC -DPIC -O3 -DNDEBUG -fPIC -D'QT_TRANSLATIONS_DIR="/usr/lib/qt/translations"' -o CMakeFiles/sf2player.dir/sf2_player.cpp.o -c /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp: Dans le constructeur ?sf2Instrument::sf2Instrument(InstrumentTrack*)?: /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:98:20: erreur?: ?FLUID_REVERB_DEFAULT_ROOMSIZE? was not declared in this scope m_reverbRoomSize( FLUID_REVERB_DEFAULT_ROOMSIZE, 0, 1.0, 0.01f, this, tr( "Reverb Roomsize" ) ), ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:99:19: erreur?: ?FLUID_REVERB_DEFAULT_DAMP? was not declared in this scope m_reverbDamping( FLUID_REVERB_DEFAULT_DAMP, 0, 1.0, 0.01, this, tr( "Reverb Damping" ) ), ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:100:17: erreur?: ?FLUID_REVERB_DEFAULT_WIDTH? was not declared in this scope m_reverbWidth( FLUID_REVERB_DEFAULT_WIDTH, 0, 1.0, 0.01f, this, tr( "Reverb Width" ) ), ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:101:17: erreur?: ?FLUID_REVERB_DEFAULT_LEVEL? was not declared in this scope m_reverbLevel( FLUID_REVERB_DEFAULT_LEVEL, 0, 1.0, 0.01f, this, tr( "Reverb Level" ) ), ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:103:15: erreur?: ?FLUID_CHORUS_DEFAULT_N? was not declared in this scope m_chorusNum( FLUID_CHORUS_DEFAULT_N, 0, 10.0, 1.0, this, tr( "Chorus Lines" ) ), ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:104:17: erreur?: ?FLUID_CHORUS_DEFAULT_LEVEL? was not declared in this scope m_chorusLevel( FLUID_CHORUS_DEFAULT_LEVEL, 0, 10.0, 0.01, this, tr( "Chorus Level" ) ), ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:105:17: erreur?: ?FLUID_CHORUS_DEFAULT_SPEED? was not declared in this scope m_chorusSpeed( FLUID_CHORUS_DEFAULT_SPEED, 0.29, 5.0, 0.01, this, tr( "Chorus Speed" ) ), ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:106:17: erreur?: ?FLUID_CHORUS_DEFAULT_DEPTH? was not declared in this scope m_chorusDepth( FLUID_CHORUS_DEFAULT_DEPTH, 0, 46.0, 0.05, this, tr( "Chorus Depth" ) ) ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp: Dans la fonction membre ?QString sf2Instrument::getCurrentPatchName()?: /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:386:17: erreur?: aggregate ?fluid_preset_t preset? has incomplete type and cannot be defined fluid_preset_t preset; ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:399:14: erreur?: invalid use of incomplete type ?fluid_sfont_t {aka struct _fluid_sfont_t}? pSoundFont->iteration_start( pSoundFont ); ^ In file included from /usr/include/fluidsynth.h:95:0, from /tmp/SBo/lmms-1.1.90/ /sf2_player.h:38, from /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:32: /usr/include/fluidsynth/types.h:40:16: note?: forward declaration of ?fluid_sfont_t {aka struct _fluid_sfont_t}? typedef struct _fluid_sfont_t fluid_sfont_t; /**< SoundFont */ ^ /tmp/SBo/lmms-1.1.90/plugins/sf2_player/sf2_player.cpp:400:21: erreur?: invalid use of incomplete type ?fluid_sfont_t {aka struct _fluid_sfont_t}? while( pSoundFont->iteration_next( pSoundFont, From yalhcru at gmail.com Tue Apr 14 10:12:35 2020 From: yalhcru at gmail.com (B Watson) Date: Tue, 14 Apr 2020 06:12:35 -0400 Subject: [Slackbuilds-users] lmms-1.1.90 In-Reply-To: <20200414114239.99f13bd924c99aa664e3398a@clansco.org> References: <20200414114239.99f13bd924c99aa664e3398a@clansco.org> Message-ID: On 4/14/20, Fr?d?ric Falsetti wrote: > Hi, I cant' build lmms-1.1.90, plugins/sf2_player Sorry, this is a result of me pushing a fluidsynth update before I'd finished testing everything that depends on it. Should be fixed in the next public update. From falsetti at clansco.org Tue Apr 14 10:18:20 2020 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Tue, 14 Apr 2020 12:18:20 +0200 Subject: [Slackbuilds-users] lmms-1.1.90 In-Reply-To: References: <20200414114239.99f13bd924c99aa664e3398a@clansco.org> Message-ID: <20200414121820.324eac2c3366213242b8ddc7@clansco.org> thanks ! le Tue, 14 Apr 2020 06:12:35 -0400 B Watson a ?crit : > On 4/14/20, Fr?d?ric Falsetti wrote: > > Hi, I cant' build lmms-1.1.90, plugins/sf2_player > > Sorry, this is a result of me pushing a fluidsynth update before I'd > finished testing everything that depends on it. > > Should be fixed in the next public update. > _______________________________________________ > 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 jens at tuxane.com Tue Apr 14 13:25:00 2020 From: jens at tuxane.com (jens at tuxane.com) Date: Tue, 14 Apr 2020 15:25:00 +0200 Subject: [Slackbuilds-users] SLACKBUILDS: UNetbootin upgrade? In-Reply-To: Message-ID: <20200414152500.Horde.lMOcHZdrhUHwI4lOWg2vxj4@webmail.tuxane.com> Zitat von Fernando Lopez : > is there any way you could push an update for this app? > > > thank you! > > -- > > ------------ > Regards, > Fernando Lopez Jr. I'm sorry I can't at the moment as I do not even have a working Slackware Box around. If you want to do it in my place, I'll be happy to submit it, or if someone else would like to take over the Slackbuild I'm fine with it, too . Regards and all the best to everybody, Jens From dave at slackbuilds.org Tue Apr 14 15:24:46 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 14 Apr 2020 16:24:46 +0100 Subject: [Slackbuilds-users] SLACKBUILDS: UNetbootin upgrade? In-Reply-To: <20200414152500.Horde.lMOcHZdrhUHwI4lOWg2vxj4@webmail.tuxane.com> References: <20200414152500.Horde.lMOcHZdrhUHwI4lOWg2vxj4@webmail.tuxane.com> Message-ID: <20200414152446.GY31407@blackswan.r0t.uk> On 2020-04-14 15:25, jens at tuxane.com put forth the proposition: > Zitat von Fernando Lopez : > > > is there any way you could push an update for this app? > > > > > > thank you! > > > > -- > > > > ------------ > > Regards, > > Fernando Lopez Jr. > > I'm sorry I can't at the moment as I do not even have a working Slackware > Box around. > If you want to do it in my place, I'll be happy to submit it, or if someone > else would like to take over the Slackbuild I'm fine with it, too . > > Regards and all the best to everybody, > Jens Pushed version 677 to my branch. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From danc3 at cox.net Wed Apr 15 14:45:03 2020 From: danc3 at cox.net (Dan Clough) Date: Wed, 15 Apr 2020 09:45:03 -0500 Subject: [Slackbuilds-users] Can't build FPC Message-ID: <8d423359-ba0a-f1f0-77e9-2e9e78aaf541@cox.net> Hello, Trying to build the Free Pascal Compiler (FPC) package (version 3.0.4 on Slack 14.2 64-bit). When I run the Slackbuild, I get the following: danc at moria:~/temp4/fpc$ ls README? doinst.sh? fpc-3.0.4.x86_64-linux.tar? fpc.SlackBuild* fpc.info? slack-desc danc at moria:~/temp4/fpc$ su Password: root at moria:/home/danc/temp4/fpc# ./fpc.SlackBuild fpc-3.0.4.x86_64-linux/doc-pdf.tar.gz fpc-3.0.4.x86_64-linux/install.sh fpc-3.0.4.x86_64-linux/binary.x86_64-linux.tar fpc-3.0.4.x86_64-linux/demo.tar.gz tar: /home/danc/temp4/fpc/fpcbuild-3.0.4.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now root at moria:/home/danc/temp4/fpc# It appears to me that it's looking for "fpcbuild-3.0.4.tar.gz", which indeed does not exist. Any ideas what's wrong here, and how to fix it? Thanks! From matteo.bernardini at gmail.com Wed Apr 15 15:02:21 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 15 Apr 2020 17:02:21 +0200 Subject: [Slackbuilds-users] Can't build FPC In-Reply-To: <8d423359-ba0a-f1f0-77e9-2e9e78aaf541@cox.net> References: <8d423359-ba0a-f1f0-77e9-2e9e78aaf541@cox.net> Message-ID: Il giorno mer 15 apr 2020 alle ore 16:46 Dan Clough ha scritto: > > Hello, > > Trying to build the Free Pascal Compiler (FPC) package (version 3.0.4 on Slack > 14.2 64-bit). > > When I run the Slackbuild, I get the following: > > danc at moria:~/temp4/fpc$ ls > README doinst.sh fpc-3.0.4.x86_64-linux.tar fpc.SlackBuild* fpc.info slack-desc > danc at moria:~/temp4/fpc$ su > Password: > root at moria:/home/danc/temp4/fpc# ./fpc.SlackBuild > fpc-3.0.4.x86_64-linux/doc-pdf.tar.gz > fpc-3.0.4.x86_64-linux/install.sh > fpc-3.0.4.x86_64-linux/binary.x86_64-linux.tar > fpc-3.0.4.x86_64-linux/demo.tar.gz > tar: /home/danc/temp4/fpc/fpcbuild-3.0.4.tar.gz: Cannot open: No such file or > directory > tar: Error is not recoverable: exiting now > root at moria:/home/danc/temp4/fpc# > > It appears to me that it's looking for "fpcbuild-3.0.4.tar.gz", which indeed > does not exist. > Any ideas what's wrong here, and how to fix it? > > Thanks! you need to download that file too as it's needed by the SlackBuild: look at the file fpc.info, it contains in the variable DOWNLOAD_x86_64 the url to the files you need for your architecture. Matteo From thomas.bourdon at halpanet.org Wed Apr 15 15:37:28 2020 From: thomas.bourdon at halpanet.org (Thomas Bourdon) Date: Wed, 15 Apr 2020 17:37:28 +0200 Subject: [Slackbuilds-users] new coturn slackbuild Message-ID: <57fea41f-b2be-187c-d52a-6b77d2d934df@halpanet.org> Hi, SBo coturn doesn't exist so I'd like to submit it. But I never submit any SB before. I think I follow guidelines correctly but I prefer to show you before submiting. Maybe uid/gid must be changed. It works for slackware 14.2 and is also ready for current. Thanks for your advices. -- Thomas Bourdon -------------- next part -------------- A non-text attachment was scrubbed... Name: coturn.tar.gz Type: application/gzip Size: 3633 bytes Desc: not available URL: From ricardo at palmtx.com.ar Wed Apr 15 16:29:40 2020 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Wed, 15 Apr 2020 13:29:40 -0300 Subject: [Slackbuilds-users] [Policy] Taking over maintainership In-Reply-To: References: <202004131905.39215.ricardo@palmtx.com.ar> Message-ID: <202004151329.40227.ricardo@palmtx.com.ar> El Lunes 13/04/2020 a las 22:37, Willy Sudiarto Raharjo escribi?: > > If I send an update with only my info changed: should I bump the BUILD > > version or not? > > > > I mean, there's no need to upgrade the package if the only thing that > > changes is the maintainer's name an email but I was never sure and so > > never sent the updates (and some of my newly adopted packages actually > > need an update but life gets in the way). > > > > If the SBo admins want to do it for me, this is my only adopted > > slackbuild that doesn't have my info: > > > > misc/grc (orphaned - no maintainer) > > > > > > These other 3 I could take over: > > > > libraries/librsync (Lyle Sigurdson, mailed on 07/01/2020, no answer) > > network/urlgrabber (Javier Rojas, mailed on 07/01/2020, no answer) > > system/acpitool (Rodney Cobb, mailed on 07/01/2020, no answer) > > Sure, send them and make a note of it that you are taking over > Also, no need to bump the BUILD if it's just maintainer changes Done for the 4 slackbuilds. Thanks! -- 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 dave at slackbuilds.org Wed Apr 15 18:04:18 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 15 Apr 2020 19:04:18 +0100 Subject: [Slackbuilds-users] new coturn slackbuild In-Reply-To: <57fea41f-b2be-187c-d52a-6b77d2d934df@halpanet.org> References: <57fea41f-b2be-187c-d52a-6b77d2d934df@halpanet.org> Message-ID: <20200415180418.GC31407@blackswan.r0t.uk> On 2020-04-15 17:37, Thomas Bourdon put forth the proposition: > Hi, > > SBo coturn doesn't exist so I'd like to submit it. But I never submit any SB > before. > I think I follow guidelines correctly but I prefer to show you before > submiting. Maybe uid/gid must be changed. > > It works for slackware 14.2 and is also ready for current. > > Thanks for your advices. > > -- > Thomas Bourdon Hi Thomas, I've found a few issues, but otherwise it's good: The .info file: We can't use variables in the .info file like this: https://github.com/coturn/coturn/archive/${VERSION}/${PRGNAM}-${VERSION}.tar.gz This one works: DOWNLOAD="https://github.com/coturn/coturn/archive/4.5.1.1/coturn-4.5.1.1.tar.gz" The SlackBuild: I notice that you've used 900 for UID and GID, and we are only at 365 in https://slackbuilds.org/uid_gid.txt It's best to ask for a UID and GID here or in IRC so we can keep track of new numbers added in that list. I've added a note above the copyright notice to say that it's now maintained by you. It's not usually necessary to out the INSTALL file with the documents for /usr/doc (although I'm guilty of that too sometimes.) README: No need to put the homepage in the README, although it may go in the slack-desc. I've also fixed a typo. slack-desc: The same typo here. There shouldn't be any spaces after the : on blank lines. It's useful if you have a way of checking for trailing whitespace in your editor. Those are the only issues I could see. Cheers. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From danc3 at cox.net Wed Apr 15 18:20:21 2020 From: danc3 at cox.net (Dan Clough) Date: Wed, 15 Apr 2020 13:20:21 -0500 Subject: [Slackbuilds-users] Can't build FPC In-Reply-To: References: Message-ID: <53952422-b15b-459c-104b-389f7d75abf5@cox.net> >/Hello, />//>/Trying to build the Free Pascal Compiler (FPC) package (version 3.0.4 on Slack />/14.2 64-bit). />//>/When I run the Slackbuild, I get the following: />//>/danc at moria :~/temp4/fpc$ ls />/README doinst.sh fpc-3.0.4.x86_64-linux.tar fpc.SlackBuild* fpc.info slack-desc />/danc at moria :~/temp4/fpc$ su />/Password: />/root at moria :/home/danc/temp4/fpc# ./fpc.SlackBuild />/fpc-3.0.4.x86_64-linux/doc-pdf.tar.gz />/fpc-3.0.4.x86_64-linux/install.sh />/fpc-3.0.4.x86_64-linux/binary.x86_64-linux.tar />/fpc-3.0.4.x86_64-linux/demo.tar.gz />/tar: /home/danc/temp4/fpc/fpcbuild-3.0.4.tar.gz: Cannot open: No such file or />/directory />/tar: Error is not recoverable: exiting now />/root at moria :/home/danc/temp4/fpc# />//>/It appears to me that it's looking for "fpcbuild-3.0.4.tar.gz", which indeed />/does not exist. />/Any ideas what's wrong here, and how to fix it? />//>/Thanks! / you need to download that file too as it's needed by the SlackBuild: look at the file fpc.info, it contains in the variable DOWNLOAD_x86_64 the url to the files you need for your architecture. Matteo Doh! I missed that file shown right there on the SBo page... I did download it and now everything built fine, of course. Sorry about the gaff, and thanks Matteo! From thomas.bourdon at halpanet.org Thu Apr 16 05:35:51 2020 From: thomas.bourdon at halpanet.org (Thomas Bourdon) Date: Thu, 16 Apr 2020 07:35:51 +0200 Subject: [Slackbuilds-users] new coturn slackbuild In-Reply-To: <20200415180418.GC31407@blackswan.r0t.uk> References: <57fea41f-b2be-187c-d52a-6b77d2d934df@halpanet.org> <20200415180418.GC31407@blackswan.r0t.uk> Message-ID: Hi, Thanks Dave! You said you fixed these issues but I can't find the SB fixed. It doesn't matter, I also fixed exactly as you say, and I suggest 366 for uid/gid. I just wait to be sure 366 is a good choice, then I'll submit it. Have a nice day! Le 15/04/2020 ? 20:04, Dave Woodfall a ?crit?: > Hi Thomas, > > I've found a few issues, but otherwise it's good: > > > The .info file: > > We can't use variables in the .info file like this: > > https://github.com/coturn/coturn/archive/${VERSION}/${PRGNAM}-${VERSION}.tar.gz > > This one works: > > DOWNLOAD="https://github.com/coturn/coturn/archive/4.5.1.1/coturn-4.5.1.1.tar.gz" > > > The SlackBuild: > > I notice that you've used 900 for UID and GID, and we are only at 365 > in https://slackbuilds.org/uid_gid.txt > > It's best to ask for a UID and GID here or in IRC so we can keep > track of new numbers added in that list. > > I've added a note above the copyright notice to say that it's now > maintained by you. > > It's not usually necessary to out the INSTALL file with the documents > for /usr/doc (although I'm guilty of that too sometimes.) > > > README: > > No need to put the homepage in the README, although it may go in the > slack-desc. I've also fixed a typo. > > slack-desc: > > The same typo here. > > There shouldn't be any spaces after the : on blank lines. It's > useful if you have a way of checking for trailing whitespace in your > editor. > > Those are the only issues I could see. > > Cheers. > > -- > Dave > > The antibloat squad! > For those interested in no bloat, minimal desktop Linux > gopher://tty1.uk/1/?minimal-linux > http://tty1.uk/minimal-linux > #minimallinux @ chat.freenode.net > > _______________________________________________ > 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/ > -- Thomas Bourdon -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Thu Apr 16 06:06:37 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 16 Apr 2020 07:06:37 +0100 Subject: [Slackbuilds-users] new coturn slackbuild In-Reply-To: References: <57fea41f-b2be-187c-d52a-6b77d2d934df@halpanet.org> <20200415180418.GC31407@blackswan.r0t.uk> Message-ID: <20200416060637.GA19460@blackswan.r0t.uk> On 2020-04-16 07:35, Thomas Bourdon put forth the proposition: > Hi, > > Thanks Dave! You said you fixed these issues but I can't find the SB fixed. > It doesn't matter, I also fixed exactly as you say, and I suggest 366 for > uid/gid. > > I just wait to be sure 366 is a good choice, then I'll submit it. > > Have a nice day! I've attached it for you. > Le 15/04/2020 ? 20:04, Dave Woodfall a ?crit?: > > Hi Thomas, > > > > I've found a few issues, but otherwise it's good: > > > > > > The .info file: > > > > We can't use variables in the .info file like this: > > > > https://github.com/coturn/coturn/archive/${VERSION}/${PRGNAM}-${VERSION}.tar.gz > > > > This one works: > > > > DOWNLOAD="https://github.com/coturn/coturn/archive/4.5.1.1/coturn-4.5.1.1.tar.gz" > > > > > > The SlackBuild: > > > > I notice that you've used 900 for UID and GID, and we are only at 365 > > in https://slackbuilds.org/uid_gid.txt > > > > It's best to ask for a UID and GID here or in IRC so we can keep > > track of new numbers added in that list. > > > > I've added a note above the copyright notice to say that it's now > > maintained by you. > > > > It's not usually necessary to out the INSTALL file with the documents > > for /usr/doc (although I'm guilty of that too sometimes.) > > > > > > README: > > > > No need to put the homepage in the README, although it may go in the > > slack-desc. I've also fixed a typo. > > > > slack-desc: > > > > The same typo here. > > > > There shouldn't be any spaces after the : on blank lines. It's > > useful if you have a way of checking for trailing whitespace in your > > editor. > > > > Those are the only issues I could see. > > > > Cheers. -------------- next part -------------- A non-text attachment was scrubbed... Name: coturn.tar.gz Type: application/x-gzip Size: 3651 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From thomas.bourdon at halpanet.org Thu Apr 16 06:17:32 2020 From: thomas.bourdon at halpanet.org (Thomas Bourdon) Date: Thu, 16 Apr 2020 08:17:32 +0200 Subject: [Slackbuilds-users] new coturn slackbuild In-Reply-To: <20200416060637.GA19460@blackswan.r0t.uk> References: <57fea41f-b2be-187c-d52a-6b77d2d934df@halpanet.org> <20200415180418.GC31407@blackswan.r0t.uk> <20200416060637.GA19460@blackswan.r0t.uk> Message-ID: <02107775-beb0-6d81-77da-ca1a9f34485f@halpanet.org> Thanks! 2 things I see in coturn.SlackBuild: * You added the new maintainer correctly, but the others never maintained/supported (the SB is based on another) it, so I can delete these lines. * You forgot to remove INSTALL file so it's fixed now. :D Thank you again, I can submit it now. Le 16/04/2020 ? 08:06, Dave Woodfall a ?crit?: > On 2020-04-16 07:35, > Thomas Bourdon put forth the proposition: >> Hi, >> >> Thanks Dave! You said you fixed these issues but I can't find the SB fixed. >> It doesn't matter, I also fixed exactly as you say, and I suggest 366 for >> uid/gid. >> >> I just wait to be sure 366 is a good choice, then I'll submit it. >> >> Have a nice day! > I've attached it for you. > >> Le 15/04/2020 ? 20:04, Dave Woodfall a ?crit?: >>> Hi Thomas, >>> >>> I've found a few issues, but otherwise it's good: >>> >>> >>> The .info file: >>> >>> We can't use variables in the .info file like this: >>> >>> https://github.com/coturn/coturn/archive/${VERSION}/${PRGNAM}-${VERSION}.tar.gz >>> >>> This one works: >>> >>> DOWNLOAD="https://github.com/coturn/coturn/archive/4.5.1.1/coturn-4.5.1.1.tar.gz" >>> >>> >>> The SlackBuild: >>> >>> I notice that you've used 900 for UID and GID, and we are only at 365 >>> in https://slackbuilds.org/uid_gid.txt >>> >>> It's best to ask for a UID and GID here or in IRC so we can keep >>> track of new numbers added in that list. >>> >>> I've added a note above the copyright notice to say that it's now >>> maintained by you. >>> >>> It's not usually necessary to out the INSTALL file with the documents >>> for /usr/doc (although I'm guilty of that too sometimes.) >>> >>> >>> README: >>> >>> No need to put the homepage in the README, although it may go in the >>> slack-desc. I've also fixed a typo. >>> >>> slack-desc: >>> >>> The same typo here. >>> >>> There shouldn't be any spaces after the : on blank lines. It's >>> useful if you have a way of checking for trailing whitespace in your >>> editor. >>> >>> Those are the only issues I could see. >>> >>> 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/ > -- Thomas Bourdon -------------- next part -------------- An HTML attachment was scrubbed... URL: From phalange at komputermatrix.com Thu Apr 16 16:12:42 2020 From: phalange at komputermatrix.com (Andrew Payne) Date: Thu, 16 Apr 2020 12:12:42 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit programs, required to maintain? Message-ID: Is it expected of maintainers to provide 32-bit versions of software when they are available? Thanks, Andrew From alex at dcclost.com Thu Apr 16 16:16:13 2020 From: alex at dcclost.com (Alexander Grotewohl) Date: Thu, 16 Apr 2020 16:16:13 +0000 Subject: [Slackbuilds-users] 32-bit programs, required to maintain? In-Reply-To: References: Message-ID: i had assumed this type of thing would be fairly automatic. are you talking about something pre-compiled? (huge and difficult to build usually) -- Alexander Grotewohl https://dcclost.com ________________________________ From: SlackBuilds-users on behalf of Andrew Payne Sent: Thursday, April 16, 2020 12:12:42 PM To: slackbuilds-users at slackbuilds.org Subject: [Slackbuilds-users] 32-bit programs, required to maintain? Is it expected of maintainers to provide 32-bit versions of software when they are available? Thanks, Andrew _______________________________________________ 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 fernando.lopezjr at gmail.com Thu Apr 16 16:16:31 2020 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 16 Apr 2020 10:16:31 -0600 Subject: [Slackbuilds-users] 32-bit programs, required to maintain? In-Reply-To: References: Message-ID: it is autodetected... if you have a 32bit system it compiles a 32 bit one... if you have 64 bit... you get a 64 bit one... On Thu, Apr 16, 2020 at 10:13 AM Andrew Payne wrote: > Is it expected of maintainers to provide 32-bit versions of software when > they are available? > > Thanks, > Andrew > _______________________________________________ > 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/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Thu Apr 16 16:21:26 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 16 Apr 2020 17:21:26 +0100 Subject: [Slackbuilds-users] 32-bit programs, required to maintain? In-Reply-To: References: Message-ID: <20200416162126.GB2539@blackswan.r0t.uk> On 2020-04-16 12:12, Andrew Payne put forth the proposition: > Is it expected of maintainers to provide 32-bit versions of software when > they are available? > > Thanks, > Andrew Hi Andrew, It depends. Is it pre-compiled software? If so, and there are both separate 32 and 64 bit versions, then it's normal to include both versions if possible. You would use the options with the _x86_64 suffix in the .info for the 64 bit version, and plain DOWNLOAD and MD5SUM for the 32 bit. However, if only a 64 bit version is available, then in the .info file we would use DOWNLOAD="UNSUPPORTED" for 32 bit. Hope that helps. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From phalange at komputermatrix.com Thu Apr 16 16:23:47 2020 From: phalange at komputermatrix.com (Andrew Payne) Date: Thu, 16 Apr 2020 12:23:47 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit programs, required to maintain? In-Reply-To: References: Message-ID: Poor wording on my part, rephrase: When I create a slackbuild for an app that has both 64-bit and 32-bit versions, is it required that I provide links to the 32-bit version in the .info file, and include the code to install it in the .SlackBuild? I ask because I have't run 32-bit for years and it's difficult to meaningfully test it. On Thu, 16 Apr 2020, Fernando Lopez wrote: > it is autodetected... if you have a 32bit system it compiles a 32 bit one... if you have 64 bit... you get a 64 bit one... > > On Thu, Apr 16, 2020 at 10:13 AM Andrew Payne wrote: > Is it expected of maintainers to provide 32-bit versions of software when > they are available? > > Thanks, > Andrew > _______________________________________________ > 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/ > > > > -- > > ------------ > Regards, > ? ? Fernando Lopez Jr. > > From yalhcru at gmail.com Thu Apr 16 18:47:14 2020 From: yalhcru at gmail.com (B Watson) Date: Thu, 16 Apr 2020 14:47:14 -0400 Subject: [Slackbuilds-users] 32-bit programs, required to maintain? In-Reply-To: References: Message-ID: On 4/16/20, Andrew Payne wrote: > Poor wording on my part, rephrase: > > When I create a slackbuild for an app that has both 64-bit and 32-bit > versions, is it required that I provide links to the 32-bit version in the > .info file, and include the code to install it in the .SlackBuild? "Has both 64-bit and 32-bit versions" means the download site has separate downloads? In that case, yes, you should include both in the .info file, and the script should handle either (examine the ARCH variable as needed, etc). I don't know that I'd go so far as to say it's *required*, but it's polite at least. > I ask because I have't run 32-bit for years and it's difficult to > meaningfully test it. If you really want to test it, you could use VM software like qemu or virtualbox, install 32-bit Slackware in a virtual machine. If you don't have the time/energy/etc to do the testing, you might find someone on the mailing list who does run 32-bit, and is interested in using your application, who wouldn't mind testing it on 32-bit for you. Or, you might punt: in your README put something like "The author has not tested the 32-bit version of this software. Please send mail if you run into problems on 32-bit". Then be willing to work with whoever does send you mail about it (if it ever happens). From phalange at komputermatrix.com Thu Apr 16 19:18:36 2020 From: phalange at komputermatrix.com (Andrew Payne) Date: Thu, 16 Apr 2020 15:18:36 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit programs, required to maintain? In-Reply-To: References: Message-ID: Ok thanks, that clears it up. On Thu, 16 Apr 2020, B Watson wrote: > On 4/16/20, Andrew Payne wrote: >> Poor wording on my part, rephrase: >> >> When I create a slackbuild for an app that has both 64-bit and 32-bit >> versions, is it required that I provide links to the 32-bit version in the >> .info file, and include the code to install it in the .SlackBuild? > > "Has both 64-bit and 32-bit versions" means the download site has > separate downloads? In that case, yes, you should include both in the > .info file, and the script should handle either (examine the ARCH variable > as needed, etc). > > I don't know that I'd go so far as to say it's *required*, but it's > polite at least. > >> I ask because I have't run 32-bit for years and it's difficult to >> meaningfully test it. > > If you really want to test it, you could use VM software like qemu or > virtualbox, install 32-bit Slackware in a virtual machine. > > If you don't have the time/energy/etc to do the testing, you might find > someone on the mailing list who does run 32-bit, and is interested in > using your application, who wouldn't mind testing it on 32-bit for you. > > Or, you might punt: in your README put something like "The author has > not tested the 32-bit version of this software. Please send mail if you > run into problems on 32-bit". Then be willing to work with whoever does > send you mail about it (if it ever happens). > _______________________________________________ > 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 yalhcru at gmail.com Thu Apr 16 19:39:51 2020 From: yalhcru at gmail.com (B Watson) Date: Thu, 16 Apr 2020 15:39:51 -0400 Subject: [Slackbuilds-users] Builds in search of a maintainer Message-ID: In August 2019, Dugan Chen orphaned all his builds... some of them have been picked up by other maintainers (including me), but there are still quite a few left: audio/rubyripper desktop/compiz-boxmenu development/gnome-inform7 graphics/vulkan-sdk-bin libraries/gtkglextmm multimedia/munt python/pycdio python/pygpgme ruby/rubygem-atk ruby/rubygem-cairo ruby/rubygem-gdk_pixbuf2 ruby/rubygem-glib2 ruby/rubygem-gtk2 ruby/rubygem-pango ruby/rubygem-pkg-config system/GentiumPlus system/ds4drv system/xnp2 I'd say whoever takes rubyripper should also take the rubygem-* builds, since they're (optional) dependencies of it. Anyone want any of these? From alik at ejik.org Thu Apr 16 19:53:40 2020 From: alik at ejik.org (Alexander Verbovetsky) Date: Thu, 16 Apr 2020 22:53:40 +0300 (MSK) Subject: [Slackbuilds-users] Builds in search of a maintainer In-Reply-To: References: Message-ID: Hello, > In August 2019, Dugan Chen orphaned all his builds... some of them > have been picked up by other maintainers (including me), but there are > still quite a few left: > python/pycdio I could take this because it's a dependency of whipper. Best regards, Alexander From yalhcru at gmail.com Thu Apr 16 20:04:09 2020 From: yalhcru at gmail.com (B Watson) Date: Thu, 16 Apr 2020 16:04:09 -0400 Subject: [Slackbuilds-users] Builds in search of a maintainer In-Reply-To: References: Message-ID: On 4/16/20, Alexander Verbovetsky wrote: >> python/pycdio > > I could take this because it's a dependency of whipper. Thanks. I went ahead and changed the .info file in my git branch, so you don't have to do anything right now. From poprocks at gmail.com Thu Apr 16 21:51:19 2020 From: poprocks at gmail.com (Logan Rathbone) Date: Thu, 16 Apr 2020 17:51:19 -0400 Subject: [Slackbuilds-users] 'wayland-egl' can be removed from SBO Message-ID: <20200416215119.GA25978@darkstar.example.net> Hello all, Now that Diniz Bortlotto has updated wayland to 1.18.0, wayland-egl can be removed from SBo, as this is now part of wayland and is no longer a separate project. Thanks, Logan "Poprocks" From alik at ejik.org Thu Apr 16 23:57:40 2020 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 17 Apr 2020 02:57:40 +0300 (MSK) Subject: [Slackbuilds-users] Builds in search of a maintainer In-Reply-To: References: Message-ID: On Thu, 16 Apr 2020, B Watson wrote: > On 4/16/20, Alexander Verbovetsky wrote: > >> python/pycdio > > > > I could take this because it's a dependency of whipper. > I went ahead and changed the .info file in my git branch, so you don't > have to do anything right now. Thank you! I already submitted an update to the pending queue. Best regards, Alexander From lenardrspencer at gmail.com Fri Apr 17 00:23:22 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Thu, 16 Apr 2020 20:23:22 -0400 Subject: [Slackbuilds-users] Request to Matteo Message-ID: Matteo, can you please remove dvdbackup from your slackware-current repo? With Pat upgrading libdvdread to 6.1.1 it is now completely broken. I have been working to try to get the old versions in as static libs, but so far no luck. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Fri Apr 17 04:21:17 2020 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 17 Apr 2020 14:21:17 +1000 Subject: [Slackbuilds-users] 'wayland-egl' can be removed from SBO In-Reply-To: <20200416215119.GA25978@darkstar.example.net> References: <20200416215119.GA25978@darkstar.example.net> Message-ID: <20200417042117.GK13869@dimstar.local.net> On Thu, Apr 16, 2020 at 05:51:19PM -0400, Logan Rathbone wrote: > Hello all, > > Now that Diniz Bortlotto has updated wayland to 1.18.0, wayland-egl can > be removed from SBo, as this is now part of wayland and is no longer a > separate project. > > Thanks, > Logan "Poprocks" Fine with me. Cheers ... Duncan. From matteo.bernardini at gmail.com Fri Apr 17 06:08:59 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 17 Apr 2020 08:08:59 +0200 Subject: [Slackbuilds-users] Request to Matteo In-Reply-To: References: Message-ID: Il giorno ven 17 apr 2020 alle ore 02:23 Lenard Spencer ha scritto: > > Matteo, can you please remove dvdbackup from your slackware-current repo? With Pat upgrading libdvdread to 6.1.1 it is now completely broken. I have been working to try to get the old versions in as static libs, but so far no luck. Thanks. Hi Lenard, does this help? https://git.archlinux.org/svntogit/community.git/tree/trunk?h=packages/dvdbackup From lenardrspencer at gmail.com Fri Apr 17 16:02:19 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Fri, 17 Apr 2020 12:02:19 -0400 Subject: [Slackbuilds-users] Request to Matteo In-Reply-To: References: Message-ID: Thanks for the link. This is basically the same patch I had seen before, with a couple of changes. To finally make it work, I had to scrap the PATH MAX limitation patch as the two conflicted with each other. Thanks again! On Fri, Apr 17, 2020, 02:09 Matteo Bernardini wrote: > Il giorno ven 17 apr 2020 alle ore 02:23 Lenard Spencer > ha scritto: > > > > Matteo, can you please remove dvdbackup from your slackware-current > repo? With Pat upgrading libdvdread to 6.1.1 it is now completely broken. > I have been working to try to get the old versions in as static libs, but > so far no luck. Thanks. > > Hi Lenard, > > does this help? > > > https://git.archlinux.org/svntogit/community.git/tree/trunk?h=packages/dvdbackup > _______________________________________________ > 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 Sun Apr 19 06:41:10 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Apr 2020 13:41:10 +0700 Subject: [Slackbuilds-users] Updates - 20200419.1 Message-ID: <8140bda4-3df8-8810-356b-6c6bf32de549@slackbuilds.org> Sun Apr 19 03:58:19 UTC 2020 academic/fet: Updated for version 5.44.1. academic/rpy2: Added (R in Python). audio/audacity: Use correct github URL. audio/carla: Updated for version 2.1. audio/deadbeef: New maintainer. audio/faac: Use correct github URL. audio/faad2: Use correct github URL. audio/fluidsynth-dssi: Updated for version 1.0.0+20190112_c9b4107. audio/lmms: Updated for version 1.2.1. audio/mpd: Updated for version 0.21.22. audio/muse: Patched. audio/muse: Updated for version 3.1. audio/swami: Updated for version 2.2.1. desktop/Qogir-icon-theme: Speed up build. desktop/Surfn: Simplify & speed up build. desktop/Zafiro-icons: Speed up build. desktop/arc-icon-theme: Speed up build. desktop/areao43-icon-theme: Speed up build. desktop/awoken-icon-theme: Speed up build. desktop/faba-mono-icons: Speed up build. desktop/faenza-icon-theme: Speed up build. desktop/faience-icon-theme: Speed up build. desktop/find-cursor: Updated for version 1.5. desktop/flatwoken-icon-theme: Speed up build. desktop/kfaenza-icon-theme: Speed up build. desktop/meliae-icon-theme: Speed up build. desktop/numix-icon-theme-square: Speed up build. desktop/numix-icon-theme-square: Updated for version 20191227. desktop/numix-icon-theme: Fix VERSION, speed up build. desktop/oranchelo-icon-theme: Speed up build. desktop/papirus-icon-theme: Speed up build. desktop/ssr: Updated for version 0.4.0. desktop/vivacious-colors-gtk-icon-theme: Speed up build. desktop/weston: Update DEP. development/cf-cli: Updated for version 6.51.0. development/codelite: Updated for version 14.0. development/google-webdesigner: Updated for version 8.0.1.0401. development/kotlin: Updated for version 1.3.72. development/love: Updated for version 11.3, new maintainer. development/tea: new maintainer development/tig: Updated for version 2.5.1. development/tiled: Updated for version 1.3.4. development/tiled: updated for version 1.3.3 development/uz80as: Update MD5SUM. development/vscode-bin: Updated for version 1.44.1. development/vscode-bin: Updated for version 1.44.2. games/7kaa: Updated for version 2.15.3. games/FlightGear-data: Updated for version 2018.3.5. games/FlightGear: Updated for version 2018.3.5. games/SLADE: Updated for version 3.1.11, new maintainer. games/ags: updated for version 3.5.0.24 games/doomretro: Updated for version 3.5.4, new maintainer. games/eureka: Updated for version 1.24, new maintainer. games/innoextract: New maintainer. games/jfsw: Fix fluidsynth 2.x build. games/lgogdownloader: updated for version 3.7 games/lmpc: Updated for version 1b70022. games/mangband: Updated for version 1.5.3. games/mgba: Updated for version 0.8.1. games/mrrescue: Updated for version 1.02e+20180818_a5be73c. games/nestopia: Updated for version 1.50. games/ppsspp: Add missing file. games/ppsspp: Fix missing dep. games/ppsspp: Updated for version 1.9.4. games/prboom-plus: Updated for version 2.5.1.7um, new maintainer. games/qzdl: New maintainer. games/scummvm: Updated for version 2.1.2, fix build. games/yamagi-quake2: New maintainer. gis/gpxsee: Updated for version 7.28. graphics/brlcad: updated for version 7.30.2 graphics/wayland-egl: Removed (included in wayland). ham/CubicSDR: Updated for version d2f9333. ham/liquid-dsp: Updated for version 1.3.2. libraries/Botan: Updated for version 2.14.0. libraries/SDL2: Updated for version 2.0.12, new maintainer. libraries/SDL2_image: Updated for version 2.0.5, new maintainer. libraries/SDL2_mixer: new maintainer. libraries/SDL2_net: new maintainer. libraries/SDL2_ttf: Updated for version 2.0.15, new maintainer. libraries/SimGear: Add missing patch. libraries/SimGear: Updated for version 2018.3.5. libraries/efl: Fix build. libraries/hoel: updated for version 1.4.15 libraries/libcbor: updated for version 0.6.1 libraries/libinput: Updated for version 1.15.5. libraries/libinstpatch: Updated for version 1.1.2. libraries/librsync: New maintainer. libraries/liburcu: Updated for version 0.12.0. libraries/live555: Updated for version 2020.04.12 libraries/lua-readline: Updated for version 2.6. libraries/lua-std.normalize: Updated for version 2.0.3. libraries/python3-PyQt5: Update REQUIRES. libraries/qt5-legacy: Remove README.benchmarks. libraries/qt5-webkit-annulen: Removed. libraries/qt5-webkit: Add -reduce-relocations. libraries/qt5-webkit: Use correct github URL. libraries/qt5: Updated for version 5.12.8. libraries/tolua++: Use correct github URL. libraries/ulfius: updated for version 2.6.6 libraries/yder: updated for version 1.4.10 misc/grc: New maintainer. misc/qtkeychain: Updated for version 0.10.0. multimedia/dvdbackup: Remove instructions for current. multimedia/k9copy-reloaded: Use internal dvdnav. multimedia/obs-studio: Note latest buildable version multimedia/vlc: Updated for version 3.0.9.2 network/coturn: Added (open source TURN and STUN Server). network/freerdp: Updated for version 2.0.0. network/insync: Updated for version 3.1.3.40790. network/krb5: Updated for version 1.18.1. network/netcat-openbsd: Removed unused patches. network/palemoon: Updated for version 28.9.1. network/qutebrowser-tox: Updated for version 1.10.2. network/qutebrowser: Update README. network/qutebrowser: Updated for version 1.10.2. network/shorewall-core: Updated for version 5.2.4.1. network/shorewall6: Updated for version 5.2.4.1. network/shorewall: Updated for version 5.2.4.1. network/signal-desktop: Updated for version 1.33.1. network/skypeforlinux: Updated for version 8.59.0.77. network/translate-shell: Updated for version 0.9.6.11. network/uTox: Updated for version 0.17.2 network/urlgrabber: New maintainer. network/wireguard-linux-compat: Updated for version 1.0.20200413. network/zoom-linux: Updated for version 3.5.385850.0413. office/hunspell-de: Fix script. office/keepassxc: Updated for version 2.5.4. office/plover: Added (Open source stenotype engine). office/xlsx2csv: Added (xlsx to csv converter). office/xournal: Updated for version 0.4.8.2016. perl/perl-CPANPLUS: Updated for version 0.9908. perl/perl-List-AllUtils: Added (All List utilities). perl/perl-Moo: Updated for version 2.004000. perl/perl-MooX-StrictConstructor: Updated for version 0.011. python/asttokens: Updated for version 2.0.4. python/pybind11: Updated for version 2.5.0 python/pycdio: Updated for version 0.21. python/python-configargparse: Updated for version 1.2.1. python/python-jsonrpclib: Updated for version 0.4.1. python/python-soupsieve: Update README. python/python3-pyrsistent: Updated for version 0.16.0. python/python3-soupsieve: Updated for version 1.9.5. python/sphinxcontrib-plantuml: Updated for version 0.18. python/sphinxcontrib-websupport: Updated for version 1.2.1. system/acpitool: New maintainer. system/bleachbit: Updated for version 3.9.2. system/chronograf: Updated for version 1.8.2. system/ciopfs: New maintainer. system/containerd: Updated for version 1.2.13. system/docker-proxy: Updated for version 20200102_9fd385b. system/docker: Updated for version 19.03.8. system/dosbox-dev: updated for version 0.74.3.r4335 system/fd: Updated for version 8.0.0. system/kbfs: Updated for version 5.4.0_20200416162659. system/keybase: Updated for version 5.4.0. system/lnav: Updated for version 0.8.5. system/netdata: Updated for version 1.21.1. system/nvidia-driver: Updated for version 440.82. system/nvidia-kernel: Updated for version 440.82. system/nvidia-legacy390-driver: Fix nvidia-switch. system/ossec-agent: Update copyright year and credits. system/ossec-local: Update copyright year and credits. system/ossec-server: Update copyright year and credits. system/runc: Updated for version 1.0.0_rc10. system/skim: Updated for version 0.8.1. system/sysbench: Added (benchmark suite). system/telegraf: Updated for version 1.14.1. system/thinkfan: Updated for version 1.1. system/unetbootin: Updated for version 677. system/xen: Updated for version 4.13.0. system/xldconfig: Updated for version 0.7. +--------------------------+ -- 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 lenardrspencer at gmail.com Sun Apr 19 13:40:56 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 19 Apr 2020 09:40:56 -0400 Subject: [Slackbuilds-users] Request to Matteo In-Reply-To: References: Message-ID: On another note, in SimGear, with the options I have put in for building on current those config file moves are no longer necessary. Thanks. On Fri, Apr 17, 2020, 12:02 Lenard Spencer wrote: > Thanks for the link. This is basically the same patch I had seen before, > with a couple of changes. To finally make it work, I had to scrap the PATH > MAX limitation patch as the two conflicted with each other. > Thanks again! > > > On Fri, Apr 17, 2020, 02:09 Matteo Bernardini > wrote: > >> Il giorno ven 17 apr 2020 alle ore 02:23 Lenard Spencer >> ha scritto: >> > >> > Matteo, can you please remove dvdbackup from your slackware-current >> repo? With Pat upgrading libdvdread to 6.1.1 it is now completely broken. >> I have been working to try to get the old versions in as static libs, but >> so far no luck. Thanks. >> >> Hi Lenard, >> >> does this help? >> >> >> https://git.archlinux.org/svntogit/community.git/tree/trunk?h=packages/dvdbackup >> _______________________________________________ >> 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 Sun Apr 19 16:15:19 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 19 Apr 2020 10:15:19 -0600 Subject: [Slackbuilds-users] ffmpeg4 not building Message-ID: I am using the following ffmpeg4.sqf file in a freshly installed (and up-to-date) 14.2 system: libass chromaprint frei0r ladspa_sdk libaom libbluray libbs2b celt libdc1394 libfdk-aac flite libgme gsm libiec61883 libavc1394 libilbc libmodplug lame opencore-amr opencv opus rtmpdump rubberband snappy speex tesseract twolame vid.stab libwebp x264 x265 xvidcore zeromq zvbi ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes LIBXVID=yes LIBZMQ=yes LIBZVBI=yes I encountered the following issues: 1. var-plugin-sdk is required for rubberband. 2. leptonica is required for tesseract (I think). 3. ffmpeg4 seems to be looking for opencv, while the script above installs opencv4: ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c ffmpeg-4.1/tests/checkasm/synth_filter.c ffmpeg-4.1/tests/checkasm/vf_nlmeans.c ffmpeg-4.1/tests/tiny_psnr.c ffmpeg-4.1/COPYING.LGPLv2.1 ffmpeg-4.1/README.md ffmpeg-4.1/CONTRIBUTING.md ERROR: opencv not found using pkg-config # pkg-config --list-all|grep opencv opencv4 OpenCV - Open Source Computer Vision Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Sun Apr 19 17:17:58 2020 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 19 Apr 2020 11:17:58 -0600 Subject: [Slackbuilds-users] codeblocks not finding source... Message-ID: Processing codeblocks codeblocks: codeblocks not found in /var/cache/sbopkg. URL transformed to HTTPS due to an HSTS policy --2020-04-19 11:15:08-- https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz Resolving sourceforge.net (sourceforge.net)... 216.105.38.13 Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/ [following] --2020-04-19 11:15:11-- https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/ Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/download [following] --2020-04-19 11:15:12-- https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/download Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://downloads.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz?r=&ts=1587316512&use_mirror=svwh [following] --2020-04-19 11:15:12-- https://downloads.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz?r=&ts=1587316512&use_mirror=svwh Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.105.38.13 Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://svwh.dl.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz [following] --2020-04-19 11:15:14-- https://svwh.dl.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz Resolving svwh.dl.sourceforge.net (svwh.dl.sourceforge.net)... 72.5.72.15, 2606:c680:0:b:3830:34ff:fe66:6663 Connecting to svwh.dl.sourceforge.net (svwh.dl.sourceforge.net)|72.5.72.15|:443... failed: Connection timed out. Connecting to svwh.dl.sourceforge.net (svwh.dl.sourceforge.net)|2606:c680:0:b:3830:34ff:fe66:6663|:443... failed: Network is unreachable. codeblocks: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Apr 19 17:52:33 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Apr 2020 00:52:33 +0700 Subject: [Slackbuilds-users] codeblocks not finding source... In-Reply-To: References: Message-ID: > codeblocks: > codeblocks not found in /var/cache/sbopkg. > URL transformed to HTTPS due to an HSTS policy > --2020-04-19 11:15:08-- > https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz > Resolving sourceforge.net (sourceforge.net)... 216.105.38.13 > Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... > connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: > https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/ > [following] > --2020-04-19 11:15:11-- > https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/ > Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... > connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/download > [following] > --2020-04-19 11:15:12-- > https://sourceforge.net/projects/codeblocks/files/Sources/20.03/codeblocks-20.03.tar.xz/download > Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... > connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://downloads.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz?r=&ts=1587316512&use_mirror=svwh > [following] > --2020-04-19 11:15:12-- > https://downloads.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz?r=&ts=1587316512&use_mirror=svwh > Resolving downloads.sourceforge.net (downloads.sourceforge.net)... > 216.105.38.13 > Connecting to downloads.sourceforge.net > (downloads.sourceforge.net)|216.105.38.13|:443... > connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://svwh.dl.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz > [following] > --2020-04-19 11:15:14-- > https://svwh.dl.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz > Resolving svwh.dl.sourceforge.net (svwh.dl.sourceforge.net)... 72.5.72.15, > 2606:c680:0:b:3830:34ff:fe66:6663 > Connecting to svwh.dl.sourceforge.net > (svwh.dl.sourceforge.net)|72.5.72.15|:443... > failed: Connection timed out. > Connecting to svwh.dl.sourceforge.net > (svwh.dl.sourceforge.net)|2606:c680:0:b:3830:34ff:fe66:6663|:443... > failed: Network is unreachable. > > codeblocks: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. try download from https://nchc.dl.sourceforge.net/project/codeblocks/Sources/20.03/codeblocks-20.03.tar.xz -- 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 Sun Apr 19 18:38:38 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 11:38:38 -0700 (PDT) Subject: [Slackbuilds-users] Problem building Qt5 Message-ID: Yesterday I tried to upgrade qt5-webkit-5.9.0 but the build script failed. I thought it might be because I have qt5-5.12.7_nowebengine-x86_64-1_SBo installed and it needs qt5 with the web engine. Today sbopkg indicated that qt5 needed upgrading (along with several other packages) so I set it running. For some reason the qt5 build halts here: g++ @/tmp/SBo/qt-everywhere-src-5.12.8/qtwebengine/src/core/release/QtWebEngineCore_o.rsp -Wl,--start-group @/tmp/SBo/qt-everywhere-src-5.12.8/qtwebengine/src/core/release/QtWebEngineCore_a.rsp -Wl,--end-group -Wl,-z,noexecstack -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -m64 -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-O1 -L/usr/lib64 -Wl,--enable-new-dtags -Wl,-whole-archive -lqtwebenginecoreapi -Wl,-no-whole-archive -Wl,--no-undefined -Wl,--version-script,QtWebEngineCore.version -Wl,-O1 -L/usr/lib64 -Wl,--enable-new-dtags -shared -Wl,-Bsymbolic-functions -Wl,-soname,libQt5WebEngineCore.so.5 -o libQt5WebEngineCore.so.5.12.8 /tmp/SBo/qt-everywhere-src-5.12.8/qtdeclarative/lib/libQt5Quick.so /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/lib/libQt5Gui.so /tmp/SBo/qt-everywhere-src-5.12.8/qtwebchannel/lib/libQt5WebChannel.so /tmp/SBo/qt-everywhere-src-5.12.8/qtdeclarative/lib/libQt5Qml.so /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/lib/libQt5Network.so /tmp/SBo/qt-everywhere-src-5.12.8/qtlocation/lib/libQt5Positioning.so /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/lib/libQt5Core.so -lpthread -lpthread -ldl -lrt -lnss3 -lsmime3 -lsoftokn3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lsqlite3 -lexpat -levent -lresolv -lz -lpng16 -lwebpmux -lwebpdemux -lwebp -lfreetype -ljpeg -lfontconfig -lX11 -lX11-xcb -lxcb -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lXss -lpci -lasound -lm -lopus -ldbus-1 -lminizip -llcms2 -L/tmp/SBo/qt-everywhere-src-5.12.8/qtwebengine/src/core/api/release /usr/lib64/libGL.so I let it sit for well over an hour with nothing happening, then killed sbopkg. In /tmp/SBo/qt-everywhere-src-5.12.8/ I don't see any error log. I'm asking for advice on how to proceed upgrading qt5 and its webkit. TIA, Rich From dave at slackbuilds.org Sun Apr 19 18:42:30 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 19 Apr 2020 19:42:30 +0100 Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: References: Message-ID: <20200419184230.GA8690@blackswan.r0t.uk> On 2020-04-19 11:38, Rich Shepard put forth the proposition: > Yesterday I tried to upgrade qt5-webkit-5.9.0 but the build script failed. I > thought it might be because I have qt5-5.12.7_nowebengine-x86_64-1_SBo > installed and it needs qt5 with the web engine. Hi Rich There was a change in the source download link which unfortunately broke the qt5-webkit slackbuild. I'm just fixing it as we speak. > Today sbopkg indicated that qt5 needed upgrading (along with several other > packages) so I set it running. For some reason the qt5 build halts here: > > g++ @/tmp/SBo/qt-everywhere-src-5.12.8/qtwebengine/src/core/release/QtWebEngineCore_o.rsp > -Wl,--start-group @/tmp/SBo/qt-everywhere-src-5.12.8/qtwebengine/src/core/release/QtWebEngineCore_a.rsp > -Wl,--end-group -Wl,-z,noexecstack -Wl,--fatal-warnings -Wl,--build-id=sha1 > -fPIC -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -m64 -Wl,-O2 -Wl,--gc-sections > -rdynamic -Wl,-O1 -L/usr/lib64 -Wl,--enable-new-dtags -Wl,-whole-archive > -lqtwebenginecoreapi -Wl,-no-whole-archive -Wl,--no-undefined > -Wl,--version-script,QtWebEngineCore.version -Wl,-O1 -L/usr/lib64 > -Wl,--enable-new-dtags -shared -Wl,-Bsymbolic-functions > -Wl,-soname,libQt5WebEngineCore.so.5 -o libQt5WebEngineCore.so.5.12.8 > /tmp/SBo/qt-everywhere-src-5.12.8/qtdeclarative/lib/libQt5Quick.so > /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/lib/libQt5Gui.so > /tmp/SBo/qt-everywhere-src-5.12.8/qtwebchannel/lib/libQt5WebChannel.so > /tmp/SBo/qt-everywhere-src-5.12.8/qtdeclarative/lib/libQt5Qml.so > /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/lib/libQt5Network.so > /tmp/SBo/qt-everywhere-src-5.12.8/qtlocation/lib/libQt5Positioning.so > /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/lib/libQt5Core.so -lpthread > -lpthread -ldl -lrt -lnss3 -lsmime3 -lsoftokn3 -lnssutil3 -lplds4 -lplc4 > -lnspr4 -lsqlite3 -lexpat -levent -lresolv -lz -lpng16 -lwebpmux -lwebpdemux > -lwebp -lfreetype -ljpeg -lfontconfig -lX11 -lX11-xcb -lxcb -lXcomposite > -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lXss -lpci > -lasound -lm -lopus -ldbus-1 -lminizip -llcms2 > -L/tmp/SBo/qt-everywhere-src-5.12.8/qtwebengine/src/core/api/release > /usr/lib64/libGL.so > > I let it sit for well over an hour with nothing happening, then killed > sbopkg. > > In /tmp/SBo/qt-everywhere-src-5.12.8/ I don't see any error log. > > I'm asking for advice on how to proceed upgrading qt5 and its webkit. > > TIA, > > Rich Not sure about this one. I'll take a look. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From yalhcru at gmail.com Sun Apr 19 18:48:37 2020 From: yalhcru at gmail.com (B Watson) Date: Sun, 19 Apr 2020 14:48:37 -0400 Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: References: Message-ID: On 4/19/20, Rich Shepard wrote: > > I let it sit for well over an hour with nothing happening, then killed > sbopkg. That looks like it was a huge link. Taking more than an hour is normal, especially if it's having to use swap. Before you killed it, did you check CPU usage (e.g. with "top")? It should have been pegging one core at 100%. > I'm asking for advice on how to proceed upgrading qt5 and its webkit. More patience. And/or more RAM, if you can. Also, you could try exporting LDGOLD=yes in the environment. This might speed up the linking drastically... or possibly cause it to fail, as it requires more memory than the regular linker. Worth trying, anyway. From rshepard at appl-ecosys.com Sun Apr 19 19:16:14 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 12:16:14 -0700 (PDT) Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: References: Message-ID: On Sun, 19 Apr 2020, B Watson wrote: > That looks like it was a huge link. Taking more than an hour is normal, > especially if it's having to use swap. B. I've 32G memory here and little else running. > Before you killed it, did you check CPU usage (e.g. with "top")? It > should have been pegging one core at 100%. Yes, I looked at top and didn't see sbopkg or any process that looked relevant in the half-minute or so I watched; didn't specifically look for memory use. > More patience. And/or more RAM, if you can. Okay. I've put off replacing the 32G RAM with 64G because I'm focused on developing more business (despite the pandemic and economic shutdown). 32G should be enough. So, I'll start it again and spend time reading while the pizza dough rises. Many thanks. Stay healthy, Rich From alleytrotter at gmail.com Sun Apr 19 19:17:22 2020 From: alleytrotter at gmail.com (John Yost) Date: Sun, 19 Apr 2020 15:17:22 -0400 Subject: [Slackbuilds-users] qt5-webkit Message-ID: <548555ef-dc7b-c622-021a-b83a827ea924@gmail.com> slackBuild cannot find qtwebkit-v5.212.0-alpha4.tar.gz /usr/local/src/build/libraries/qt5-webkit/build # ./qt5-webkit.SlackBuild tar: /usr/local/src/build/libraries/qt5-webkit/build/qtwebkit-v5.212.0-alpha4.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now the "v" seems to be the culprit in the version HELP Please -- John David Yost AlleyTrotter pub 2048D/F3BDEB55 2014-05-23 [expires: Never] From rshepard at appl-ecosys.com Sun Apr 19 19:18:38 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 12:18:38 -0700 (PDT) Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: <20200419184230.GA8690@blackswan.r0t.uk> References: <20200419184230.GA8690@blackswan.r0t.uk> Message-ID: On Sun, 19 Apr 2020, Dave Woodfall wrote: > There was a change in the source download link which unfortunately broke > the qt5-webkit slackbuild. I'm just fixing it as we speak. Dave, Thanks. > Not sure about this one. I'll take a look. B. Watson wrote that it's a lo-o-ong link. So I'll rebuild it and let 'er run. Then I'll re-do the qt5-webkit upgrade. Thanks and stay safe, Rich From dave at slackbuilds.org Sun Apr 19 19:25:20 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 19 Apr 2020 20:25:20 +0100 Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: References: Message-ID: <20200419192520.GA1142@blackswan.r0t.uk> On 2020-04-19 12:16, Rich Shepard put forth the proposition: > On Sun, 19 Apr 2020, B Watson wrote: > > > That looks like it was a huge link. Taking more than an hour is normal, > > especially if it's having to use swap. > > B. > > I've 32G memory here and little else running. > > > Before you killed it, did you check CPU usage (e.g. with "top")? It > > should have been pegging one core at 100%. > > Yes, I looked at top and didn't see sbopkg or any process that looked > relevant in the half-minute or so I watched; didn't specifically look for > memory use. > > > More patience. And/or more RAM, if you can. > > Okay. > > I've put off replacing the 32G RAM with 64G because I'm focused on > developing more business (despite the pandemic and economic shutdown). 32G > should be enough. 32G is more than enough for Qt5. With that much you could make a tmpfs of perhaps 8G for /tmp, and that may help a bit with speed, especially when large tarballs are being extracted. You must remember to move anything out that you want to keep before rebooting or shutting down though. Added to that, have you read my README.ccache and tried setting it up in the system? You will save a *lot* of time on rebuilds with ccache working. Hope this helps. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sun Apr 19 19:27:58 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 19 Apr 2020 20:27:58 +0100 Subject: [Slackbuilds-users] qt5-webkit In-Reply-To: <548555ef-dc7b-c622-021a-b83a827ea924@gmail.com> References: <548555ef-dc7b-c622-021a-b83a827ea924@gmail.com> Message-ID: <20200419192758.GB1142@blackswan.r0t.uk> On 2020-04-19 15:17, John Yost put forth the proposition: > slackBuild cannot find > qtwebkit-v5.212.0-alpha4.tar.gz > > /usr/local/src/build/libraries/qt5-webkit/build > > # ./qt5-webkit.SlackBuild > tar: > /usr/local/src/build/libraries/qt5-webkit/build/qtwebkit-v5.212.0-alpha4.tar.gz: > > Cannot open: No such file or directory > > tar: Error is not recoverable: exiting now > > the "v" seems to be the culprit in the version > HELP Please Hi John, There was a change in the source download which broke the slackbuild. I have fixed it, but I need to build qt5 to be able to test it all works. As soon as that's done I'll push the update to my git updates branch. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Sun Apr 19 19:32:31 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 12:32:31 -0700 (PDT) Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: <20200419192520.GA1142@blackswan.r0t.uk> References: <20200419192520.GA1142@blackswan.r0t.uk> Message-ID: On Sun, 19 Apr 2020, Dave Woodfall wrote: > 32G is more than enough for Qt5. Dave, I assumed so. > With that much you could make a tmpfs of perhaps 8G for /tmp, Here it's only 8M by default. > Added to that, have you read my README.ccache and tried setting it up in > the system? You will save a *lot* of time on rebuilds with ccache working. I read it but didn't implement. Will do so now. Thanks, Rich From dave at slackbuilds.org Sun Apr 19 19:41:04 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 19 Apr 2020 20:41:04 +0100 Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: References: <20200419192520.GA1142@blackswan.r0t.uk> Message-ID: <20200419194104.GA4602@blackswan.r0t.uk> On 2020-04-19 12:32, Rich Shepard put forth the proposition: > Here it's only 8M by default. Where do you see that? If you're looking at the output of the df command you may already see some named tmpfs, but can have more than one, and you can make them any size you like, within resource limits. df --human-readable --print-type Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 32M 1016K 32M 4% /run devtmpfs devtmpfs 8.0M 0 8.0M 0% /dev /dev/sda2 ext4 50G 30G 17G 64% / tmpfs tmpfs 5.9G 80M 5.8G 2% /dev/shm cgroup_root tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup /dev/sda3 ext4 864G 387G 434G 48% /home cgmfs tmpfs 100K 0 100K 0% /run/cgmanager/fs tmpfs tmpfs 2.0G 0 2.0G 0% /mnt/tmpfs tmpfs tmpfs 8.0G 3.5G 4.5G 44% /home/chroot/mnt/memory The bottom two are the ones that I added, but you can see there are others that the system uses, and those are mounted on boot. /dev/shm is often used by applications for temporary files (shm = shared memory.) -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From Jim.Diamond at acadiau.ca Sun Apr 19 20:13:22 2020 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sun, 19 Apr 2020 17:13:22 -0300 Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: References: Message-ID: <20200419201322.GB28735@jdiamond-mb.acadiau.ca> On Sun, Apr 19, 2020 at 12:16 (-0700), Rich Shepard wrote: > On Sun, 19 Apr 2020, B Watson wrote: >> That looks like it was a huge link. Taking more than an hour is normal, >> especially if it's having to use swap. > B. > I've 32G memory here and little else running. >> Before you killed it, did you check CPU usage (e.g. with "top")? It >> should have been pegging one core at 100%. > Yes, I looked at top and didn't see sbopkg or any process that looked > relevant in the half-minute or so I watched; didn't specifically look for > memory use. >> More patience. And/or more RAM, if you can. > Okay. > I've put off replacing the 32G RAM with 64G because I'm focused on > developing more business (despite the pandemic and economic shutdown). 32G > should be enough. For what it's worth... I'm compiling it right now on an Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz system (4 hyperthreaded cores) with 16 GB of RAM. It has finally gotten to the ld stage, and so far it has used 25 minutes of CPU time, and has a RRS of 1701376 (so less than 2 GB). So I doubt you really need more than 32 GB of RAM, unless you have some major memory hogs on your system. [[ It is taking me a long time to get this email out, and in the interim ld finished. At the end it used 35:20 of CPU time and its RSS was 1830832. ]] Dave (assuming you are reading this!), in the past I have edited the qt5 slackbuild to allow multiple jobs and there were no problems. Some slackbuilds have code like NUMJOBS=${NUMJOBS:--j7} ... make $NUMJOBS Even if you want to make the default to be '-j1', would you consider adding something along these lines? Or as below... While I see varying reports on the success of using MAKEFLAGS, and maybe I should have tried that, I use sbotools to build slackbuilds, and have JOBS=8 in my /etc/sbotools/sbotools.conf, but that had no effect with the building of qt5 (all the individual files were compiled separately). I am not sure what is considered to be the One True Way of setting make flags for slackbuilds, but one might boldly assume whatever sbotools does is a likely candidate. Cheers. Jim From rshepard at appl-ecosys.com Sun Apr 19 20:18:27 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 13:18:27 -0700 (PDT) Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: <20200419194104.GA4602@blackswan.r0t.uk> References: <20200419192520.GA1142@blackswan.r0t.uk> <20200419194104.GA4602@blackswan.r0t.uk> Message-ID: On Sun, 19 Apr 2020, Dave Woodfall wrote: > Where do you see that? If you're looking at the output of the df > command you may already see some named tmpfs, but can have more than > one, and you can make them any size you like, within resource limits. Dave, >From df output. > The bottom two are the ones that I added, but you can see there are others > that the system uses, and those are mounted on boot. /dev/shm is often > used by applications for temporary files (shm = shared memory.) This is really good to know. I know that Google-Earth wants to use /dev/shm (at least before the 'pro' version) and I'll make a second tmpfs. Thanks, Rich From rshepard at appl-ecosys.com Sun Apr 19 20:22:28 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 13:22:28 -0700 (PDT) Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: <20200419201322.GB28735@jdiamond-mb.acadiau.ca> References: <20200419201322.GB28735@jdiamond-mb.acadiau.ca> Message-ID: On Sun, 19 Apr 2020, Jim Diamond via SlackBuilds-users wrote: > For what it's worth... I'm compiling it right now on an Intel(R) Xeon(R) > CPU E3-1270 v5 @ 3.60GHz system (4 hyperthreaded cores) with 16 GB of RAM. > It has finally gotten to the ld stage, and so far it has used 25 minutes > of CPU time, and has a RRS of 1701376 (so less than 2 GB). So I doubt you > really need more than 32 GB of RAM, unless you have some major memory hogs > on your system. Jim, I decided to max out the memory on the Asus motherboard because I run large statistical and spatial models and the Ryzen7 2700 has 8 cores and 16 threads so I'll have sufficient capacity for everything. Thanks, Rich From dave at slackbuilds.org Sun Apr 19 20:31:46 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 19 Apr 2020 21:31:46 +0100 Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: <20200419201322.GB28735@jdiamond-mb.acadiau.ca> References: <20200419201322.GB28735@jdiamond-mb.acadiau.ca> Message-ID: <20200419203146.GB4602@blackswan.r0t.uk> On 2020-04-19 17:13, Jim Diamond via SlackBuilds-users > While I see varying reports on the success of using MAKEFLAGS, and > maybe I should have tried that, I use sbotools to build slackbuilds, > and have JOBS=8 in my /etc/sbotools/sbotools.conf, but that had no > effect with the building of qt5 (all the individual files were > compiled separately). I am not sure what is considered to be the One > True Way of setting make flags for slackbuilds, but one might boldly > assume whatever sbotools does is a likely candidate. I've always exported MAKEFLAGS in my shell, and I've not had a problem with it yet. The qt5 make command is: make || make -j1 So if MAKEFLAGS=-j4 it will use that, and fallback to -j1 if it fails. export MAKEFLAGS=-j$(($(nproc)+1)) or a similar construct can be used in the shell, so that shell startup scripts can be reused on different machines. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From Jim.Diamond at acadiau.ca Sun Apr 19 20:54:13 2020 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sun, 19 Apr 2020 17:54:13 -0300 Subject: [Slackbuilds-users] Problem building Qt5 In-Reply-To: References: <20200419201322.GB28735@jdiamond-mb.acadiau.ca> Message-ID: <20200419205413.GA8263@jdiamond-mb.acadiau.ca> On Sun, Apr 19, 2020 at 13:22 (-0700), Rich Shepard wrote: > CAUTION: This email comes from outside Acadia. Verify the sender and use caution with any requests, links or attachments. > On Sun, 19 Apr 2020, Jim Diamond via SlackBuilds-users wrote: >> For what it's worth... I'm compiling it right now on an Intel(R) Xeon(R) >> CPU E3-1270 v5 @ 3.60GHz system (4 hyperthreaded cores) with 16 GB of RAM. >> It has finally gotten to the ld stage, and so far it has used 25 minutes >> of CPU time, and has a RRS of 1701376 (so less than 2 GB). So I doubt you >> really need more than 32 GB of RAM, unless you have some major memory hogs >> on your system. > Jim, > I decided to max out the memory on the Asus motherboard because I run large > statistical and spatial models and the Ryzen7 2700 has 8 cores and 16 > threads so I'll have sufficient capacity for everything. Hi Rich, when I said I doubt you need more than 32 GB, I was talking about compiling Qt, not about your general usage of the machine. Following this exchange: On Sun, Apr 19, 2020 at 12:16 (-0700), Rich Shepard wrote: > On Sun, 19 Apr 2020, B Watson wrote: >> That looks like it was a huge link. Taking more than an hour is normal, >> especially if it's having to use swap. > B. > I've 32G memory here and little else running. >> Before you killed it, did you check CPU usage (e.g. with "top")? It >> should have been pegging one core at 100%. > Yes, I looked at top and didn't see sbopkg or any process that looked > relevant in the half-minute or so I watched; didn't specifically look for > memory use. >> More patience. And/or more RAM, if you can. Cheers. Jim From yalhcru at gmail.com Sun Apr 19 21:00:55 2020 From: yalhcru at gmail.com (B Watson) Date: Sun, 19 Apr 2020 17:00:55 -0400 Subject: [Slackbuilds-users] qt5-webkit In-Reply-To: <20200419192758.GB1142@blackswan.r0t.uk> References: <548555ef-dc7b-c622-021a-b83a827ea924@gmail.com> <20200419192758.GB1142@blackswan.r0t.uk> Message-ID: On 4/19/20, Dave Woodfall wrote: > > As soon as that's done I'll push the update to my git updates branch. Actually, I kinda already pushed a fix for the download URL... it was indeed the "v" in the filename. From dave at slackbuilds.org Sun Apr 19 21:06:08 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 19 Apr 2020 22:06:08 +0100 Subject: [Slackbuilds-users] qt5-webkit In-Reply-To: References: <548555ef-dc7b-c622-021a-b83a827ea924@gmail.com> <20200419192758.GB1142@blackswan.r0t.uk> Message-ID: <20200419210608.GC4602@blackswan.r0t.uk> On 2020-04-19 17:00, B Watson put forth the proposition: > On 4/19/20, Dave Woodfall wrote: > > > > > As soon as that's done I'll push the update to my git updates branch. > > Actually, I kinda already pushed a fix for the download URL... it > was indeed the "v" in the filename. It created a problem is the slackbuild. I had put in some vars for the source directory etc. that failed with the new tarball because the output directory was named differently. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sun Apr 19 21:09:18 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 19 Apr 2020 22:09:18 +0100 Subject: [Slackbuilds-users] qt5-webkit In-Reply-To: <20200419210608.GC4602@blackswan.r0t.uk> References: <548555ef-dc7b-c622-021a-b83a827ea924@gmail.com> <20200419192758.GB1142@blackswan.r0t.uk> <20200419210608.GC4602@blackswan.r0t.uk> Message-ID: <20200419210918.GD4602@blackswan.r0t.uk> On 2020-04-19 22:06, Dave Woodfall put forth the proposition: > On 2020-04-19 17:00, > B Watson put forth the proposition: > > On 4/19/20, Dave Woodfall wrote: > > > > > > > > As soon as that's done I'll push the update to my git updates branch. > > > > Actually, I kinda already pushed a fix for the download URL... it > > was indeed the "v" in the filename. > > It created a problem is the slackbuild. I had put in some vars for > the source directory etc. that failed with the new tarball because > the output directory was named differently. is = in. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Sun Apr 19 22:00:48 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 15:00:48 -0700 (PDT) Subject: [Slackbuilds-users] Numpy3 Message-ID: N.B.: I sent this to Chris' email address but it was rejected for an SPF issue. My postfix SPF passes port25.com's tests and has not before been questioned or rejected by anyone, including prior messages to him. Also, the IP address shown in the bounced message is not mine. So, I'm posting the message here. Chris, The SBo repo has numpy3-1.14.3 while -1.18.2 is available. Is there a reason the new version is not available for 14.2? Regards, Rich From jebrhansen+SBo at gmail.com Sun Apr 19 22:13:50 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 19 Apr 2020 16:13:50 -0600 Subject: [Slackbuilds-users] Numpy3 In-Reply-To: References: Message-ID: On Sun, Apr 19, 2020, 4:00 PM Rich Shepard wrote: > N.B.: I sent this to Chris' email address but it was rejected for an SPF > issue. My postfix SPF passes port25.com's tests and has not before been > questioned or rejected by anyone, including prior messages to him. Also, > the > IP address shown in the bounced message is not mine. So, I'm posting the > message here. > > > Chris, > > The SBo repo has numpy3-1.14.3 while -1.18.2 is available. Is there a > reason > the new version is not available for 14.2? > > Regards, > > Rich > I try to keep all my python3 package versions in sync with their python2 counterparts, and this may be the case here. You may want to check with the numpy maintainer to see if they've not upgraded it for a specific reason. But some maintainers choose to not upgrade to minimize the chances of breakage, so you may want to provide a specific reason why you want it upgraded (to install X software, it requires at least version x.xx). Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Sun Apr 19 22:44:22 2020 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 20 Apr 2020 08:44:22 +1000 Subject: [Slackbuilds-users] Numpy3 In-Reply-To: References: Message-ID: <0b4710ec-e9e3-18dc-ec81-d33279c64d8c@linux.com> On 20/4/20 8:13 am, Jeremy Hansen wrote: > On Sun, Apr 19, 2020, 4:00 PM Rich Shepard > wrote: > > N.B.: I sent this to Chris' email address but it was rejected for an SPF > issue. My postfix SPF passes port25.com 's tests > and has not before been > questioned or rejected by anyone, including prior messages to him. > Also, the > IP address shown in the bounced message is not mine. So, I'm posting the > message here. > > > Chris, > > The SBo repo has numpy3-1.14.3 while -1.18.2 is available. Is there > a reason > the new version is not available for 14.2? > > Regards, > > Rich > > > I try to keep all my python3 package versions in sync with their python2 > counterparts, and this may be the case here. You may want to check with > the numpy maintainer to see if they've not upgraded it for a specific > reason. > > But some maintainers choose to not upgrade to minimize the chances of > breakage, so you may want to provide a specific reason why you want it > upgraded (to install X software, it requires at least version x.xx). > Hi Rich, Your other email arrived OK - I just replied separately to it. About numpy3, the reason for not upgrading is (as Jeremy suggested) to maintain version sync with numpy. Numpy is maintained by someone who prefers stability over updates for no reason other than their availability. If you have a particular reason for wanting/needing a newer version, I'm sure the maintainer would be amenable to an update; then I could update numpy3. chris From rshepard at appl-ecosys.com Sun Apr 19 23:02:28 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 19 Apr 2020 16:02:28 -0700 (PDT) Subject: [Slackbuilds-users] Numpy3 Message-ID: Well, the U. of Oregon again failed your ISP's SPF test so my message to your linux.com address was again rejected. Sheesh. ---------- Forwarded message ---------- Date: Sun, 19 Apr 2020 15:59:19 -0700 (PDT) From: Rich Shepard To: Christoph Willing Subject: Re: Numpy3 (fwd) On Mon, 20 Apr 2020, Christoph Willing wrote: > Yes, the email arrived OK. Chris, Interesting. Wonder why the original message didn't make it there. > About numpy3, the reason for not upgrading is to maintain version sync > with numpy. Numpy is maintained by someone who prefers stability over > updates for no reason other than its availability. If you have a > particular reason for wanting/needing a newer version, I'm sure the > maintainer would be amenable to an update; then I could update numpy3. I keep python2 itself updated when a new version comes out because some applications, such as grass, still have not migrated to python3. My use is now all python3 so I don't bother upgrading python2 libraries. I've now no specific need for numpy3 and scipy3, but being 4 minor versions behind current seems a bit too much. Regards, Rich From flinchx at protonmail.com Sun Apr 19 23:05:14 2020 From: flinchx at protonmail.com (flinchx) Date: Sun, 19 Apr 2020 23:05:14 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 Message-ID: A couple of weeks ago qt5 on SBo got bumped from 5.9 to 5.12. Since I'm following the SBo mailing list, I saw there were some rough edges and decided to wait for a while before things stabilize. After this week update, I checked the mailing list again. There is a thread about qt5-webkit - not relevant for qt5 (?). There is a thread about building qt5 taking lots of time. Well, that's a known fact that qt5 is big. My qt5 built and installed fine with sbopkg: [code] $ ls /var/log/packages | grep qt5-5 qt5-5.12.8-x86_64-1_SBo [/code] I didn't dig up the whole giant build log, I wouldn't understand there anything anyway. But listing the output directory of sbopkg: [code] $ ls -l qt5-5* -rw-r--r-- 1 root root 120490737 Apr 20 01:06 qt5-5.12.8-x86_64-1_SBo.tgz -rw-r--r-- 1 root root 104838125 Dec 22 10:28 qt5-5.9.9-x86_64-1_SBo.tgz [/code] at least shows that a package of comparable size was produced and installed. Next thing I did was to rebuilt qt5ct, since the qt5 README advertises it shall work. It built and installed fine. But it fails to run: [code] $ qt5ct QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' Cannot mix incompatible Qt library (version 0x50909) with this library (version 0x50c08) Aborted [/code] I've got exactly the same startup error message after rebuilding and installing qbittorrent-qt5 which is advertised to work as well in qt5 README. I have also tried to rebuild RetroShare, it produces a crippled package with no "retroshare" executable at all. The log shows there was some compile error and for this one, the suggestion from the qt5 README should be followed: [code] Please report any problems about applications that don't work correctly to the Qt5 maintainer or to the mailing list. [/code] but I believe it's a bit premature to bug the RS maintainer at this point, since other software (see above) doesn't work either, even if it compiles. What am I doing wrong and what did I miss? From dave at slackbuilds.org Sun Apr 19 23:22:15 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 20 Apr 2020 00:22:15 +0100 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: References: Message-ID: <20200419232215.GE4602@blackswan.r0t.uk> On 2020-04-19 23:05, Slackbuilds Users put forth the proposition: > [code] > $ qt5ct > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' > Cannot mix incompatible Qt library (version 0x50909) with this library (version 0x50c08) > Aborted > [/code] > > I've got exactly the same startup error message after rebuilding and installing qbittorrent-qt5 which is advertised to work as well in qt5 README. > > I have also tried to rebuild RetroShare, it produces a crippled package with no "retroshare" executable at all. The log shows there was some compile error and for this one, the suggestion from the qt5 README should be followed: > > [code] > Please report any problems about applications that don't > work correctly to the Qt5 maintainer or to the mailing list. > [/code] > > That means the slackbuild maintainer (me), not the upstream Qt5 devs. I will test these as soon as qt5 has finished building. In the meantime, it would help if you can provide build logs from building qt5ct, qbittorrent, and RetroShare. Since you are using sbopkg you can email us /var/log/sbopkg/sbopkg-build.log but please *delete* the old one before running sbopkg, so that a new one is created. The logs can grow to > 1GB. Thanks -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From jebrhansen+SBo at gmail.com Sun Apr 19 23:25:36 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 19 Apr 2020 17:25:36 -0600 Subject: [Slackbuilds-users] Numpy3 In-Reply-To: References: Message-ID: On Sun, Apr 19, 2020, 5:02 PM Rich Shepard wrote: > Well, the U. of Oregon again failed your ISP's SPF test so my message to > your linux.com address was again rejected. Sheesh. > > ---------- Forwarded message ---------- > Date: Sun, 19 Apr 2020 15:59:19 -0700 (PDT) > From: Rich Shepard > To: Christoph Willing > Subject: Re: Numpy3 (fwd) > > On Mon, 20 Apr 2020, Christoph Willing wrote: > > Yes, the email arrived OK. > > Chris, > > Interesting. Wonder why the original message didn't make it there. > > > About numpy3, the reason for not upgrading is to maintain version sync > > with numpy. Numpy is maintained by someone who prefers stability over > > updates for no reason other than its availability. If you have a > > particular reason for wanting/needing a newer version, I'm sure the > > maintainer would be amenable to an update; then I could update numpy3. > > I keep python2 itself updated when a new version comes out because some > applications, such as grass, still have not migrated to python3. My use is > now all python3 so I don't bother upgrading python2 libraries. > > I've now no specific need for numpy3 and scipy3, but being 4 minor versions > behind current seems a bit too much. > SBo has no official policy on how maintainers should upgrade their packages. If there's no major bugs and no requirements by other software for newer versions, some maintainers prefer to ride out there current version until some bug is found or other software requires newer versions. This is a similar stance taken by Pat in stable releases of Slackware. He doesn't upgrade libraries in 14.2 just because newer versions are out. This is why I said you may want to provide some reason on why the maintainer should upgrade other than "there's a newer version". Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From flinchx at protonmail.com Sun Apr 19 23:58:57 2020 From: flinchx at protonmail.com (flinchx) Date: Sun, 19 Apr 2020 23:58:57 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <20200419232215.GE4602@blackswan.r0t.uk> References: <20200419232215.GE4602@blackswan.r0t.uk> Message-ID: ??????? Original Message ??????? On Monday, April 20, 2020 2:22 AM, Dave Woodfall wrote: All the logs are a bit too big and exceed the 100kb message limit, so I'll have to make it two emails. -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-build-log-retroshare.gz Type: application/gzip Size: 47313 bytes Desc: not available URL: From flinchx at protonmail.com Mon Apr 20 00:00:02 2020 From: flinchx at protonmail.com (flinchx) Date: Mon, 20 Apr 2020 00:00:02 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <20200419232215.GE4602@blackswan.r0t.uk> References: <20200419232215.GE4602@blackswan.r0t.uk> Message-ID: I have attached the required build logs. I have also included the build log for qt5-styleplugins, because I use it together with qt5ct to achieve uniform look of Qt and GTK software - with these two packages installed for qt5-5.9, everything worked. For qt5-5.12, qt5-styleplugins fails to build as well. Note: I have built qt5 with default options. retroshare is built with RETROTOR=yes option as the log shows. -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-build-log-qbittorrent-qt5.gz Type: application/gzip Size: 17040 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-build-log-qt5-styleplugins.gz Type: application/gzip Size: 7296 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-build-log-qt5ct.gz Type: application/gzip Size: 4409 bytes Desc: not available URL: From dave at slackbuilds.org Mon Apr 20 00:03:56 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 20 Apr 2020 01:03:56 +0100 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: References: <20200419232215.GE4602@blackswan.r0t.uk> Message-ID: <20200420000356.GF4602@blackswan.r0t.uk> On 2020-04-20 00:00, Slackbuilds Users put forth the proposition: > I have attached the required build logs. I have also included the build log for qt5-styleplugins, because I use it together with qt5ct to achieve uniform look of Qt and GTK software - with these two packages installed for qt5-5.9, everything worked. For qt5-5.12, qt5-styleplugins fails to build as well. > > Note: I have built qt5 with default options. retroshare is built with RETROTOR=yes option as the log shows. Thanks. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Mon Apr 20 05:59:05 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 20 Apr 2020 06:59:05 +0100 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: References: <20200419232215.GE4602@blackswan.r0t.uk> Message-ID: <20200420055905.GA25665@blackswan.r0t.uk> On 2020-04-20 00:00, Slackbuilds Users put forth the proposition: > I have attached the required build logs. I have also included the build log for qt5-styleplugins, because I use it together with qt5ct to achieve uniform look of Qt and GTK software - with these two packages installed for qt5-5.9, everything worked. For qt5-5.12, qt5-styleplugins fails to build as well. I have some results. qt5-styleplugins This is now relegated to qt5-legacy I'm afraid. They only made one release in 2014, plus one commit since then in 2017. qbittorrent-qt5 I had no errors testing this. qt5ct There was one warning when I tested this, but on a second run it didn't reoccur. retroshare Did you set the RETROTOR option with this? -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Mon Apr 20 06:17:44 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 20 Apr 2020 07:17:44 +0100 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <20200420055905.GA25665@blackswan.r0t.uk> References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> Message-ID: <20200420061744.GB25665@blackswan.r0t.uk> On 2020-04-20 06:59, Dave Woodfall put forth the proposition: > On 2020-04-20 00:00, > Slackbuilds Users put forth the proposition: > > I have attached the required build logs. I have also included the build log for qt5-styleplugins, because I use it together with qt5ct to achieve uniform look of Qt and GTK software - with these two packages installed for qt5-5.9, everything worked. For qt5-5.12, qt5-styleplugins fails to build as well. > > I have some results. > > qt5-styleplugins > > This is now relegated to qt5-legacy I'm afraid. They only made one > release in 2014, plus one commit since then in 2017. > > qbittorrent-qt5 > > I had no errors testing this. > > qt5ct > > There was one warning when I tested this, but on a second run it > didn't reoccur. > > retroshare > > Did you set the RETROTOR option with this? Ok, I can see it in the log. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Mon Apr 20 07:50:31 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 20 Apr 2020 08:50:31 +0100 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <20200420061744.GB25665@blackswan.r0t.uk> References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> <20200420061744.GB25665@blackswan.r0t.uk> Message-ID: <20200420075031.GC25665@blackswan.r0t.uk> On 2020-04-20 07:17, Dave Woodfall put forth the proposition: > On 2020-04-20 06:59, > Dave Woodfall put forth the proposition: > > On 2020-04-20 00:00, > > Slackbuilds Users put forth the proposition: > > > I have attached the required build logs. I have also included the build log for qt5-styleplugins, because I use it together with qt5ct to achieve uniform look of Qt and GTK software - with these two packages installed for qt5-5.9, everything worked. For qt5-5.12, qt5-styleplugins fails to build as well. > > > > I have some results. > > > > qt5-styleplugins > > > > This is now relegated to qt5-legacy I'm afraid. They only made one > > release in 2014, plus one commit since then in 2017. > > > > qbittorrent-qt5 > > > > I had no errors testing this. > > > > qt5ct > > > > There was one warning when I tested this, but on a second run it > > didn't reoccur. > > > > retroshare > > > > Did you set the RETROTOR option with this? > > Ok, I can see it in the log. Can you try the attached slackbuild. I've made a few changes to it, and I also bumped the version. The attached info has the download link. It starts up as far a username window but that's as far as I tested it. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: retroshare.SlackBuild.gz Type: application/x-gzip Size: 1405 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: retroshare.info.gz Type: application/x-gzip Size: 303 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Mon Apr 20 08:01:22 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 20 Apr 2020 09:01:22 +0100 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <20200420075031.GC25665@blackswan.r0t.uk> References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> <20200420061744.GB25665@blackswan.r0t.uk> <20200420075031.GC25665@blackswan.r0t.uk> Message-ID: <20200420080122.GD25665@blackswan.r0t.uk> On 2020-04-20 08:50, Dave Woodfall put forth the proposition: > On 2020-04-20 07:17, > Dave Woodfall put forth the proposition: > > On 2020-04-20 06:59, > > Dave Woodfall put forth the proposition: > > > On 2020-04-20 00:00, > > > Slackbuilds Users put forth the proposition: > > > > I have attached the required build logs. I have also included the build log for qt5-styleplugins, because I use it together with qt5ct to achieve uniform look of Qt and GTK software - with these two packages installed for qt5-5.9, everything worked. For qt5-5.12, qt5-styleplugins fails to build as well. > > > > > > I have some results. > > > > > > qt5-styleplugins > > > > > > This is now relegated to qt5-legacy I'm afraid. They only made one > > > release in 2014, plus one commit since then in 2017. Ponce has saved the day with a patch, so this also builds now. > > > qbittorrent-qt5 > > > > > > I had no errors testing this. > > > > > > qt5ct > > > > > > There was one warning when I tested this, but on a second run it > > > didn't reoccur. > > > > > > retroshare > > > > > > Did you set the RETROTOR option with this? > > > > Ok, I can see it in the log. > > Can you try the attached slackbuild. I've made a few changes to it, > and I also bumped the version. The attached info has the download > link. It starts up as far a username window but that's as far as I > tested it. > > -- > Dave > > The antibloat squad! > For those interested in no bloat, minimal desktop Linux > gopher://tty1.uk/1/?minimal-linux > http://tty1.uk/minimal-linux > #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From flinchx at protonmail.com Mon Apr 20 09:04:46 2020 From: flinchx at protonmail.com (flinchx) Date: Mon, 20 Apr 2020 09:04:46 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <20200420055905.GA25665@blackswan.r0t.uk> References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> Message-ID: ??????? Original Message ??????? On Monday, April 20, 2020 8:59 AM, Dave Woodfall wrote: > I have some results. > > qt5-styleplugins > > This is now relegated to qt5-legacy I'm afraid. They only made one > release in 2014, plus one commit since then in 2017. I saw the other email, but I'll reply in this one for consistency > > qbittorrent-qt5 > > I had no errors testing this. > > qt5ct > > There was one warning when I tested this, but on a second run it > didn't reoccur. > > retroshare > > Did you set the RETROTOR option with this? > Yes, as I wrote above. I also saw you figured it out from the log. But back to qt5 first - I'll have to do it one thing at a time, othwerwise I feel overwhelmed. As I understand, in context of mentioned packages, the dependency chain works like this: / qt5ct -----------\ qt5 qbittorrent-qt5 \ qt5-styleplugins / and / qt5ct -----------\ qt5 retroshare \ qt5-styleplugins / qt5 is the basic library, qt5ct + qt5-styleplugins are additional helpers (optional dependencies) to achieve consistent theming, as I wrote above, qbittorrent-qt5 and retroshare are end-user qt5 apps. As I understand, we both upgraded qt5 to 5.12.8 from qt5-5.9.9 (this one became qt5-legacy). qt5ct works fine for you, but doesn't work for me. Full stop. Just to clear the things up - it builds fine for me with the new qt5 version. The error I'm getting: $ qt5ct QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' Cannot mix incompatible Qt library (version 0x50909) with this library (version 0x50c08) Aborted is a runtime error. What am I supposed to do next, to get a working qt5ct? I'm willing to fiddle a bit more with this before I give up. From flinchx at protonmail.com Mon Apr 20 09:19:39 2020 From: flinchx at protonmail.com (flinchx) Date: Mon, 20 Apr 2020 09:19:39 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> Message-ID: ??????? Original Message ??????? On Monday, April 20, 2020 12:04 PM, flinchx via SlackBuilds-users wrote: > ??????? Original Message ??????? > On Monday, April 20, 2020 8:59 AM, Dave Woodfall dave at slackbuilds.org wrote: > > > I have some results. > > qt5-styleplugins > > This is now relegated to qt5-legacy I'm afraid. They only made one > > release in 2014, plus one commit since then in 2017. > > I saw the other email, but I'll reply in this one for consistency > > > qbittorrent-qt5 > > I had no errors testing this. > > qt5ct > > There was one warning when I tested this, but on a second run it > > didn't reoccur. > > > retroshare > > Did you set the RETROTOR option with this? > > Yes, as I wrote above. I also saw you figured it out from the log. > > But back to qt5 first - I'll have to do it one thing at a time, othwerwise I feel overwhelmed. > > As I understand, in context of mentioned packages, the dependency chain works like this: > > / qt5ct -----------\ > qt5 qbittorrent-qt5 > \ qt5-styleplugins / > > and > > / qt5ct -----------\ > qt5 retroshare > \ qt5-styleplugins / > > qt5 is the basic library, qt5ct + qt5-styleplugins are additional helpers (optional dependencies) to achieve consistent theming, as I wrote above, qbittorrent-qt5 and retroshare are end-user qt5 apps. > > As I understand, we both upgraded qt5 to 5.12.8 from qt5-5.9.9 (this one became qt5-legacy). > > qt5ct works fine for you, but doesn't work for me. Full stop. Just to clear the things up - it builds fine for me with the new qt5 version. The error I'm getting: > > $ qt5ct > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' > Cannot mix incompatible Qt library (version 0x50909) with this library (version 0x50c08) > Aborted > > is a runtime error. > > What am I supposed to do next, to get a working qt5ct? I'm willing to fiddle a bit more with this before I give up. > > 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 have also tried to run qt5ct like this: $ QT_DEBUG_PLUGINS=1 qt5ct the runtime log is attached -------------- next part -------------- A non-text attachment was scrubbed... Name: log.gz Type: application/gzip Size: 1870 bytes Desc: not available URL: From matteo.bernardini at gmail.com Mon Apr 20 09:39:56 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 20 Apr 2020 11:39:56 +0200 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> Message-ID: can you please post the output of this command? ls -1 /var/log/packages/qt* From flinchx at protonmail.com Mon Apr 20 09:42:52 2020 From: flinchx at protonmail.com (flinchx) Date: Mon, 20 Apr 2020 09:42:52 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> Message-ID: -?????? Original Message ??????? On Monday, April 20, 2020 12:19 PM, flinchx wrote: > I have also tried to run qt5ct like this: > > $ QT_DEBUG_PLUGINS=1 qt5ct > > the runtime log is attached I think I'm getting some progress. I went and removed both qt5ct and qt5-styleplugins. Rebuilt qbittorrent-qt5. It built and started fine, but without custom theme. Fine, since I've removed those packages. I installed qt5ct only. It started. So it looks like the problem was that qt5ct did not play nice with the old version of qt5-styleplugins (which failed to build earlier). Now I need to try rebuilding qt5-styleplugins with the patch. I am doing the weekly update of packages by rsyncing the repo rather than working directly with the git repository. Should I just grab the updated SlackBuild file from https://git.slackbuilds.org/slackbuilds/log/?h=user/dive/updates and just tell sbopkg to use it as locally modified copy if I want to keep my update workflow rsync based? I suppose that next week this change will be merged into the 14.2 branch and arrive the normal way via rsync. From dave at slackbuilds.org Mon Apr 20 09:48:06 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 20 Apr 2020 10:48:06 +0100 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> Message-ID: <20200420094806.GE25665@blackswan.r0t.uk> On 2020-04-20 09:04, Slackbuilds Users put forth the proposition: > ??????? Original Message ??????? > On Monday, April 20, 2020 8:59 AM, Dave Woodfall wrote: > > > I have some results. > > > > qt5-styleplugins > > > > This is now relegated to qt5-legacy I'm afraid. They only made one > > release in 2014, plus one commit since then in 2017. > > I saw the other email, but I'll reply in this one for consistency > > > > > qbittorrent-qt5 > > > > I had no errors testing this. > > > > qt5ct > > > > There was one warning when I tested this, but on a second run it > > didn't reoccur. > > > > > retroshare > > > > Did you set the RETROTOR option with this? > > > > Yes, as I wrote above. I also saw you figured it out from the log. > > > But back to qt5 first - I'll have to do it one thing at a time, othwerwise I feel overwhelmed. > > As I understand, in context of mentioned packages, the dependency chain works like this: > > / qt5ct -----------\ > qt5 qbittorrent-qt5 > \ qt5-styleplugins / > > and > > / qt5ct -----------\ > qt5 retroshare > \ qt5-styleplugins / > > qt5 is the basic library, qt5ct + qt5-styleplugins are additional helpers (optional dependencies) to achieve consistent theming, as I wrote above, qbittorrent-qt5 and retroshare are end-user qt5 apps. > > As I understand, we both upgraded qt5 to 5.12.8 from qt5-5.9.9 (this one became qt5-legacy). > > qt5ct works fine for you, but doesn't work for me. Full stop. Just to clear the things up - it builds fine for me with the new qt5 version. The error I'm getting: > > $ qt5ct > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-shadow' > Cannot mix incompatible Qt library (version 0x50909) with this library (version 0x50c08) > Aborted > > is a runtime error. > > What am I supposed to do next, to get a working qt5ct? I'm willing to fiddle a bit more with this before I give up. This is what I've found is a good order to upgrade Qt5 for large version jumps, like 5.7 to 5.9, or 5.9 to 5.12: 1 Uninstall the old Qt5 package 2 Log out of root 3 Log back in as root 4 Build and install the new package 5 Log out of root 6 Log back in as root 7 Upgrade all other packages that depend on Qt5 The reasoning behind all the log outs/ins, is because Qt5 installs /etc/profile.d/qt5.sh that sets QT5DIR and adds QT5DIR/bin to your $PATH when you log in (there's a similar file for csh.) Even though the old Qt5 is removepkg'd, those settings are *still there* until you log out. You can see with a test (assuming bash or a zsh type shell): env | grep -i qt5 If that command is used before step 4, you shouldn't see anything qt5 related in PATH and QT5DIR shouldn't exist. Hope that helps. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From flinchx at protonmail.com Mon Apr 20 09:58:58 2020 From: flinchx at protonmail.com (flinchx) Date: Mon, 20 Apr 2020 09:58:58 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <20200420094806.GE25665@blackswan.r0t.uk> References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> <20200420094806.GE25665@blackswan.r0t.uk> Message-ID: <0zVlvtfuIAGPy05m6EAfiej7ro4SVo1ijuwAnbS0hdqOAcCTF_qLbeaLcyXVKPXLYg9F6B7mhNosewKKj5Y7J4e_3cej5ZIWUj9TF0mSpAg=@protonmail.com> ??????? Original Message ??????? On Monday, April 20, 2020 12:48 PM, Dave Woodfall wrote: > This is what I've found is a good order to upgrade Qt5 for large > version jumps, like 5.7 to 5.9, or 5.9 to 5.12: > > 1 Uninstall the old Qt5 package > 2 Log out of root > 3 Log back in as root > 4 Build and install the new package > 5 Log out of root > 6 Log back in as root > 7 Upgrade all other packages that depend on Qt5 > Clearly valuable info for a less qualified end user like me who is used to only hitting Enter a couple of times in sbopkg, because most of the times things just work. I can certainly benefit from this list of steps in the future if you add it to the qt5 README, as long as you consider it appropriate. Meanwhile qt5-styleplugins has successfully built with the patch from your branch and I've got a working and properly GTK-style themed working qbittorrent-qt5. I will try the patch for retroshare now and will report back. Thanks for the hints. From flinchx at protonmail.com Mon Apr 20 10:41:19 2020 From: flinchx at protonmail.com (flinchx) Date: Mon, 20 Apr 2020 10:41:19 +0000 Subject: [Slackbuilds-users] Multiple SBo packages broken after upgrading qt5 In-Reply-To: <0zVlvtfuIAGPy05m6EAfiej7ro4SVo1ijuwAnbS0hdqOAcCTF_qLbeaLcyXVKPXLYg9F6B7mhNosewKKj5Y7J4e_3cej5ZIWUj9TF0mSpAg=@protonmail.com> References: <20200419232215.GE4602@blackswan.r0t.uk> <20200420055905.GA25665@blackswan.r0t.uk> <20200420094806.GE25665@blackswan.r0t.uk> <0zVlvtfuIAGPy05m6EAfiej7ro4SVo1ijuwAnbS0hdqOAcCTF_qLbeaLcyXVKPXLYg9F6B7mhNosewKKj5Y7J4e_3cej5ZIWUj9TF0mSpAg=@protonmail.com> Message-ID: ??????? Original Message ??????? On Monday, April 20, 2020 12:58 PM, flinchx via SlackBuilds-users wrote: > I will try the patch for retroshare now and will report back. Retroshare works too now. Since all issues addresed in this thread seem fixed, I will provide a brief summary so it gets archived - qt5 was updated from 5.9.9 to 5.12.8 - goal was to update qt5ct, qt5-styleplugins and retroshare by rebuilding them against the new qt5 - qt5-styleplugins failed to build, the old (the one that was built against the old qt version) leftover that was not removed from the system - my mistake - was causing all qt software that was making use of custom theming to fail - retroshare failed to build against the new qt5 version - a patch was provided for qt5-styleplugins [1], which I assume will be available with the next weekly public update - removing the old qt5-styleplugins, rebuilding it against the new qt5 and installing the package made qt5ct and qbittorrent-at5 work again (after rebuilding them too against the new qt5 of course) - a patch was provided for retroshare (it's attached somewhere above in this thread) that also bumps retroshare from 0.6.4 to 0.6.5. I suppose this will come as part of next weekly public update as well - retroshare 0.6.5 compiles and runs fine with the new qt5 version Feel free to rectify whatever I've got wrong in this summary and thanks again for the help. Now I can proceed to update the rest of qt5 software I'm using. Cheers. 1. https://git.slackbuilds.org/slackbuilds/commit/?h=user/dive/updates&id=05eb3509312de23dbc9651ab9d7207cb09d14fa0 From z.coldplayer at gmail.com Mon Apr 20 14:50:35 2020 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Mon, 20 Apr 2020 18:50:35 +0400 Subject: [Slackbuilds-users] ffmpeg4 not building In-Reply-To: References: Message-ID: Hi, I have not tried the latest version but can you confirm if the legacy opencv is needed instead. On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41421 at gmail.com> wrote: > I am using the following ffmpeg4.sqf file in a freshly installed (and > up-to-date) 14.2 system: > > libass > chromaprint > frei0r > ladspa_sdk > libaom > libbluray > libbs2b > celt > libdc1394 > libfdk-aac > flite > libgme > gsm > libiec61883 > libavc1394 > libilbc > libmodplug > lame > opencore-amr > opencv > opus > rtmpdump > rubberband > snappy > speex > tesseract > twolame > vid.stab > libwebp > x264 > x265 > xvidcore > zeromq > zvbi > ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes > LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes > LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes > LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes > LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes > LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes > LIBXVID=yes LIBZMQ=yes LIBZVBI=yes > > I encountered the following issues: > > 1. var-plugin-sdk is required for rubberband. > 2. leptonica is required for tesseract (I think). > 3. ffmpeg4 seems to be looking for opencv, while the script above installs > opencv4: > > ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c > ffmpeg-4.1/tests/checkasm/synth_filter.c > ffmpeg-4.1/tests/checkasm/vf_nlmeans.c > ffmpeg-4.1/tests/tiny_psnr.c > ffmpeg-4.1/COPYING.LGPLv2.1 > ffmpeg-4.1/README.md > ffmpeg-4.1/CONTRIBUTING.md > ERROR: opencv not found using pkg-config > > # pkg-config --list-all|grep opencv > opencv4 OpenCV - Open Source Computer Vision > Library > _______________________________________________ > 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 rshepard at appl-ecosys.com Mon Apr 20 15:51:28 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 20 Apr 2020 08:51:28 -0700 (PDT) Subject: [Slackbuilds-users] Problem building Qt5 [RESOLVED] In-Reply-To: References: Message-ID: On Sun, 19 Apr 2020, B Watson wrote: > More patience. And/or more RAM, if you can. I set up ccache and let Qt5 build. It took 4h 55min on my Ryzen7 2700 desktop with 32G RAM. That's a lot of time for a UI widget library, but it tries to do everything, everywhere, for everybody. Reading the ccache man page I think I understand that it provided no speed-up because it needed a full build to cache for future upgrades. My thanks to all who commented and increases my understanding. Stay well, all, Rich From 1.41421 at gmail.com Mon Apr 20 17:36:26 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 20 Apr 2020 11:36:26 -0600 Subject: [Slackbuilds-users] ffmpeg4 not building In-Reply-To: References: Message-ID: It is building all right, in that it did not choke on opencv as I reported here before. However, I could not get opencv-legacy to build with tesseract already installed. I had to remove tesseract, build and install opencv-legacy, build and install tesseract, and then launch the build of ffmpeg4. The build job for ffmpeg4 is still ongoing; I'll report on the outcome. On Mon, Apr 20, 2020 at 8:49 AM Jheengut Pritvi wrote: > Hi, > I have not tried the latest version but can you confirm if the legacy > opencv is needed instead. > > > On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41421 at gmail.com> wrote: > >> I am using the following ffmpeg4.sqf file in a freshly installed (and >> up-to-date) 14.2 system: >> >> libass >> chromaprint >> frei0r >> ladspa_sdk >> libaom >> libbluray >> libbs2b >> celt >> libdc1394 >> libfdk-aac >> flite >> libgme >> gsm >> libiec61883 >> libavc1394 >> libilbc >> libmodplug >> lame >> opencore-amr >> opencv >> opus >> rtmpdump >> rubberband >> snappy >> speex >> tesseract >> twolame >> vid.stab >> libwebp >> x264 >> x265 >> xvidcore >> zeromq >> zvbi >> ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes >> LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes >> LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes >> LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes >> LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes >> LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes >> LIBXVID=yes LIBZMQ=yes LIBZVBI=yes >> >> I encountered the following issues: >> >> 1. var-plugin-sdk is required for rubberband. >> 2. leptonica is required for tesseract (I think). >> 3. ffmpeg4 seems to be looking for opencv, while the script above >> installs opencv4: >> >> ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c >> ffmpeg-4.1/tests/checkasm/synth_filter.c >> ffmpeg-4.1/tests/checkasm/vf_nlmeans.c >> ffmpeg-4.1/tests/tiny_psnr.c >> ffmpeg-4.1/COPYING.LGPLv2.1 >> ffmpeg-4.1/README.md >> ffmpeg-4.1/CONTRIBUTING.md >> ERROR: opencv not found using pkg-config >> >> # pkg-config --list-all|grep opencv >> opencv4 OpenCV - Open Source Computer Vision >> Library >> _______________________________________________ >> 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Mon Apr 20 18:13:39 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 20 Apr 2020 12:13:39 -0600 Subject: [Slackbuilds-users] ffmpeg4 not building In-Reply-To: References: Message-ID: With the provisos mentioned in my previous communication, I was able to build ffmpeg4. On Mon, Apr 20, 2020 at 11:36 AM Luveh Keraph <1.41421 at gmail.com> wrote: > It is building all right, in that it did not choke on opencv as I reported > here before. However, I could not get opencv-legacy to build with tesseract > already installed. I had to remove tesseract, build and install > opencv-legacy, build and install tesseract, and then launch the build of > ffmpeg4. The build job for ffmpeg4 is still ongoing; I'll report on the > outcome. > > On Mon, Apr 20, 2020 at 8:49 AM Jheengut Pritvi > wrote: > >> Hi, >> I have not tried the latest version but can you confirm if the legacy >> opencv is needed instead. >> >> >> On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41421 at gmail.com> wrote: >> >>> I am using the following ffmpeg4.sqf file in a freshly installed (and >>> up-to-date) 14.2 system: >>> >>> libass >>> chromaprint >>> frei0r >>> ladspa_sdk >>> libaom >>> libbluray >>> libbs2b >>> celt >>> libdc1394 >>> libfdk-aac >>> flite >>> libgme >>> gsm >>> libiec61883 >>> libavc1394 >>> libilbc >>> libmodplug >>> lame >>> opencore-amr >>> opencv >>> opus >>> rtmpdump >>> rubberband >>> snappy >>> speex >>> tesseract >>> twolame >>> vid.stab >>> libwebp >>> x264 >>> x265 >>> xvidcore >>> zeromq >>> zvbi >>> ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes >>> LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes >>> LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes >>> LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes >>> LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes >>> LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes >>> LIBXVID=yes LIBZMQ=yes LIBZVBI=yes >>> >>> I encountered the following issues: >>> >>> 1. var-plugin-sdk is required for rubberband. >>> 2. leptonica is required for tesseract (I think). >>> 3. ffmpeg4 seems to be looking for opencv, while the script above >>> installs opencv4: >>> >>> ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c >>> ffmpeg-4.1/tests/checkasm/synth_filter.c >>> ffmpeg-4.1/tests/checkasm/vf_nlmeans.c >>> ffmpeg-4.1/tests/tiny_psnr.c >>> ffmpeg-4.1/COPYING.LGPLv2.1 >>> ffmpeg-4.1/README.md >>> ffmpeg-4.1/CONTRIBUTING.md >>> ERROR: opencv not found using pkg-config >>> >>> # pkg-config --list-all|grep opencv >>> opencv4 OpenCV - Open Source Computer Vision >>> Library >>> _______________________________________________ >>> 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/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Mon Apr 20 22:24:16 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 20 Apr 2020 23:24:16 +0100 Subject: [Slackbuilds-users] qt5-webkit In-Reply-To: <20200419210918.GD4602@blackswan.r0t.uk> References: <548555ef-dc7b-c622-021a-b83a827ea924@gmail.com> <20200419192758.GB1142@blackswan.r0t.uk> <20200419210608.GC4602@blackswan.r0t.uk> <20200419210918.GD4602@blackswan.r0t.uk> Message-ID: the md5 sum seems to be different for qt5-webkit. I'm getting 22e442063e7d0362439934442e269ed2 but am expecting? cd77f90cbf312f88d23699a65cd76ee4 have downloaded a couple of times just in case, but still different. (I got qt5 built ok (8gb ram is enough).) On 19/04/2020 22:09, Dave Woodfall wrote: > On 2020-04-19 22:06, > Dave Woodfall put forth the proposition: >> On 2020-04-19 17:00, >> B Watson put forth the proposition: >>> On 4/19/20, Dave Woodfall wrote: >>> >>>> As soon as that's done I'll push the update to my git updates branch. >>> Actually, I kinda already pushed a fix for the download URL... it >>> was indeed the "v" in the filename. >> It created a problem is the slackbuild. I had put in some vars for >> the source directory etc. that failed with the new tarball because >> the output directory was named differently. > is = in. > > -- > Dave > > The antibloat squad! > For those interested in no bloat, minimal desktop Linux > gopher://tty1.uk/1/?minimal-linux > http://tty1.uk/minimal-linux > #minimallinux @ chat.freenode.net > > _______________________________________________ > 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/ > --- This email has been checked for viruses by AVG. https://www.avg.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackware at server.ky Tue Apr 21 11:46:31 2020 From: slackware at server.ky (John) Date: Tue, 21 Apr 2020 13:46:31 +0200 Subject: [Slackbuilds-users] Nix build requires newer library Message-ID: <18aae9c3-3b5b-c983-d5d2-929c4e0bbc08@server.ky> Hi all, It looks like the latest version of the Nix package manager requires a newer version of lib-boost (or some other library) than what the latest stable has.? What's the best way to deal with this?? Is there documentation on it? Thanks in advance, John From kev4321 at fastmail.fm Tue Apr 21 14:26:41 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Tue, 21 Apr 2020 09:26:41 -0500 Subject: [Slackbuilds-users] libffado on current UNSUPPORTED SBo git repository Message-ID: <0519389f-837d-c179-374e-b447ec468042@fastmail.fm> I am trying to rebuild ffmpeg 4.2.2 with new dependencies.? Honestly, I really don't know much about ffmpeg except that it probably should have x264, aac, and other common libraries.? So, I try to enable everything, based on the --current ffmpeg-4.2.2 slackbuild, with source from --current. Using a sbopkg file, ? libffado seems to fail.? Also, I thought it was a dependency for jack, but it looks for jack at the beginning. libffado-2.4.1 ? MD5SUM check for libffado-2.4.1.tgz ... OK ? Error occurred with build.? Please check the log. * Usage of additional flags is not supported by the ffado-devs. ?* Use at own risk! ?* ?* Flags in use: ?*?? CC = gcc ?*?? CXX = g++ ?*?? CFLAGS = -O2 -fPIC ?*?? CXXFLAGS = -O2 -fPIC -std=gnu++11 -Wno-deprecated-declarations ?*?? LDFLAGS = Checking for a working C-compiler yes Checking for a working C++-compiler yes Checking for pkg-config (at least version 0.0.0)... yes Checking for libxml++-3.0... no Checking for jack... no Checking jackd version...not installed No Jack Audio Connection Kit (JACK) installed: assuming a FFADO setbuffersize-compatible version will be used. Checking for libraw1394 (2.0.5 or higher)...??? yes Checking for libiec61883 (1.1.0 or higher)...?? yes Checking for libconfig++ (0 or higher)...?????? yes Checking for libxml++-2.6 (2.13.0 or higher)...???????? yes Checking for libxml++-2.6 >= 2.39.1... yes Checking for libxml++-3.0 >= 3.0.0... no Checking for lrint(3.2) in C library m... yes Checking for lrintf(3.2) in C library m... yes Checking whether 'which pyuic4' executes yes Checking for the python module 'PyQt4' yes Checking for the python module 'dbus.mainloop.qt' yes Checking whether 'xdg-desktop-menu --help' executes yes Checking whether 'xdg-icon-resource --help' executes yes Checking for alsa (0 or higher)...????? yes Checking for dbus-1 (1.0 or higher)...? yes Checking for dbus-c++-1 (0 or higher)...??????? yes Checking whether 'which dbusxx-xml2cpp' executes yes Checking for variable session_bus_services_dir in package dbus-1...???? yes Trying to find the system triple: (cached) yes TypeError: must be str or None, not bytes: ? File "/tmp/SBo/libffado-2.4.1/SConstruct", line 822: ??? m32 = is_userspace_32bit(cpuinfo) ? File "/tmp/SBo/libffado-2.4.1/SConstruct", line 722: ??? for line in x.split(b'\n'): libffado: Would you like to continue processing the rest of the queue or would you like to abort?? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: N +++++++++++++++++++++++++++++++++++++++++++ SUMMARY LOG Using the UNSUPPORTED SBo git repository for -current Queue Process:? Download, build, and install Thanks, Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue Apr 21 14:37:21 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 21 Apr 2020 16:37:21 +0200 Subject: [Slackbuilds-users] libffado on current UNSUPPORTED SBo git repository In-Reply-To: <0519389f-837d-c179-374e-b447ec468042@fastmail.fm> References: <0519389f-837d-c179-374e-b447ec468042@fastmail.fm> Message-ID: Il giorno mar 21 apr 2020 alle ore 16:26 Kevin McCormick ha scritto: > > I am trying to rebuild ffmpeg 4.2.2 with new dependencies. Honestly, I really don't know much about ffmpeg except that it probably should have x264, aac, and other common libraries. So, I try to enable everything, based on the --current ffmpeg-4.2.2 slackbuild, with source from --current. > > Using a sbopkg file, libffado seems to fail. Also, I thought it was a dependency for jack, but it looks for jack at the beginning. > > libffado-2.4.1 > MD5SUM check for libffado-2.4.1.tgz ... OK > Error occurred with build. Please check the log. > > * Usage of additional flags is not supported by the ffado-devs. > * Use at own risk! > * > * Flags in use: > * CC = gcc > * CXX = g++ > * CFLAGS = -O2 -fPIC > * CXXFLAGS = -O2 -fPIC -std=gnu++11 -Wno-deprecated-declarations > * LDFLAGS = > > Checking for a working C-compiler yes > Checking for a working C++-compiler yes > Checking for pkg-config (at least version 0.0.0)... yes > Checking for libxml++-3.0... no > Checking for jack... no > Checking jackd version...not installed > > No Jack Audio Connection Kit (JACK) installed: assuming a FFADO > setbuffersize-compatible version will be used. > > Checking for libraw1394 (2.0.5 or higher)... yes > Checking for libiec61883 (1.1.0 or higher)... yes > Checking for libconfig++ (0 or higher)... yes > Checking for libxml++-2.6 (2.13.0 or higher)... yes > Checking for libxml++-2.6 >= 2.39.1... yes > Checking for libxml++-3.0 >= 3.0.0... no > Checking for lrint(3.2) in C library m... yes > Checking for lrintf(3.2) in C library m... yes > Checking whether 'which pyuic4' executes yes > Checking for the python module 'PyQt4' yes > Checking for the python module 'dbus.mainloop.qt' yes > Checking whether 'xdg-desktop-menu --help' executes yes > Checking whether 'xdg-icon-resource --help' executes yes > Checking for alsa (0 or higher)... yes > Checking for dbus-1 (1.0 or higher)... yes > Checking for dbus-c++-1 (0 or higher)... yes > Checking whether 'which dbusxx-xml2cpp' executes yes > Checking for variable session_bus_services_dir in package dbus-1... yes > Trying to find the system triple: (cached) yes > TypeError: must be str or None, not bytes: > File "/tmp/SBo/libffado-2.4.1/SConstruct", line 822: > m32 = is_userspace_32bit(cpuinfo) > File "/tmp/SBo/libffado-2.4.1/SConstruct", line 722: > for line in x.split(b'\n'): > > libffado: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: N > > +++++++++++++++++++++++++++++++++++++++++++ > SUMMARY LOG > Using the UNSUPPORTED SBo git repository for -current > Queue Process: Download, build, and install > > Thanks, > Kevin Hi Kevin, you are using an older version of the unofficial repository for current, the last one already has a fix for that (and builds libffado-2.4.2). http://cgit.ponce.cc/slackbuilds/commit/?h=libffado also , this is not the place to discuss issues building stuff from another repository and/or on current (SBo supports only the latest stable version of Slackware), please use the dedicated LQ topic (be sure to read very carefully its first post) https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ Matteo From klaatu at member.fsf.org Tue Apr 21 17:02:31 2020 From: klaatu at member.fsf.org (Klaatu) Date: Wed, 22 Apr 2020 05:02:31 +1200 Subject: [Slackbuilds-users] libffado on current UNSUPPORTED SBo git repository In-Reply-To: <0519389f-837d-c179-374e-b447ec468042@fastmail.fm> References: <0519389f-837d-c179-374e-b447ec468042@fastmail.fm> Message-ID: <2777535.xKHAU9opM8@beast> On Tuesday, April 21, 2020 09:26:41 AM Kevin McCormick wrote: > I am trying to rebuild ffmpeg 4.2.2 with new dependencies. Honestly, I > really don't know much about ffmpeg except that it probably should have > x264, aac, and other common libraries. So, I try to enable everything, > based on the --current ffmpeg-4.2.2 slackbuild, with source from --current. > > Using a sbopkg file, libffado seems to fail. Also, I thought it was a > dependency for jack, but it looks for jack at the beginning. > > libffado-2.4.1 > MD5SUM check for libffado-2.4.1.tgz ... OK > Error occurred with build. Please check the log. > > * Usage of additional flags is not supported by the ffado-devs. > * Use at own risk! > * > * Flags in use: > * CC = gcc > * CXX = g++ > * CFLAGS = -O2 -fPIC > * CXXFLAGS = -O2 -fPIC -std=gnu++11 -Wno-deprecated-declarations > * LDFLAGS = > > Checking for a working C-compiler yes > Checking for a working C++-compiler yes > Checking for pkg-config (at least version 0.0.0)... yes > Checking for libxml++-3.0... no > Checking for jack... no > Checking jackd version...not installed > > No Jack Audio Connection Kit (JACK) installed: assuming a FFADO > setbuffersize-compatible version will be used. > > Checking for libraw1394 (2.0.5 or higher)... yes > Checking for libiec61883 (1.1.0 or higher)... yes > Checking for libconfig++ (0 or higher)... yes > Checking for libxml++-2.6 (2.13.0 or higher)... yes > Checking for libxml++-2.6 >= 2.39.1... yes > Checking for libxml++-3.0 >= 3.0.0... no > Checking for lrint(3.2) in C library m... yes > Checking for lrintf(3.2) in C library m... yes > Checking whether 'which pyuic4' executes yes > Checking for the python module 'PyQt4' yes > Checking for the python module 'dbus.mainloop.qt' yes > Checking whether 'xdg-desktop-menu --help' executes yes > Checking whether 'xdg-icon-resource --help' executes yes > Checking for alsa (0 or higher)... yes > Checking for dbus-1 (1.0 or higher)... yes > Checking for dbus-c++-1 (0 or higher)... yes > Checking whether 'which dbusxx-xml2cpp' executes yes > Checking for variable session_bus_services_dir in package dbus-1... yes > Trying to find the system triple: (cached) yes > TypeError: must be str or None, not bytes: > File "/tmp/SBo/libffado-2.4.1/SConstruct", line 822: > m32 = is_userspace_32bit(cpuinfo) > File "/tmp/SBo/libffado-2.4.1/SConstruct", line 722: > for line in x.split(b'\n'): > > libffado: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: N > > +++++++++++++++++++++++++++++++++++++++++++ > SUMMARY LOG > Using the UNSUPPORTED SBo git repository for -current > Queue Process: Download, build, and install > > Thanks, > Kevin Kevin, do you require IEEE1394 (Firewire) drivers in FFmpeg? That's what libffado provides. Maybe you're actually using Firewire devices and have a need for this, but if not, then it's probably safe to just disable libffado in your build configurations. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: This is a digitally signed message part. URL: From nalumc at googlemail.com Tue Apr 21 14:43:58 2020 From: nalumc at googlemail.com (Andrew Conway) Date: Tue, 21 Apr 2020 15:43:58 +0100 Subject: [Slackbuilds-users] Voxelands Message-ID: I've been alerted to the fact that my slackbuild for voxelands uses the old website voxelands.com which is now infested by malware. Can this slackbuild be removed for now please? Hopefully I will find time to examine the new website voxelands.net and code base and submit a new slackbuild before too long. Thank you Andrew aka mcnalu -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Apr 21 19:29:44 2020 From: yalhcru at gmail.com (B Watson) Date: Tue, 21 Apr 2020 15:29:44 -0400 Subject: [Slackbuilds-users] Voxelands In-Reply-To: References: Message-ID: On 4/21/20, Andrew Conway via SlackBuilds-users wrote: > I've been alerted to the fact that my slackbuild for voxelands uses the old > website voxelands.com which is now infested by malware. > > Can this slackbuild be removed for now please? How about, instead of removing it, we use archive.org URLs for the homepage and download file? I've just checked, and they're available: HOMEPAGE="http://web.archive.org/web/20150829052034/http://www.voxelands.com/" DOWNLOAD="http://web.archive.org/web/20160323141651/http://www.voxelands.com/downloads/old/voxelands-1501.00-src.tar.bz2" The md5sum matches for the download file. From mflacy at verizon.net Wed Apr 22 03:51:50 2020 From: mflacy at verizon.net (Mark A. Flacy) Date: Tue, 21 Apr 2020 22:51:50 -0500 Subject: [Slackbuilds-users] faac and faad2 build errors. References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> Message-ID: <2127080.NthiaO5ijY@sonicmaster.home.flacy> Greetings, Both of these Slackbuilds appear to believe that the artifact downloaded from GitHub contains underscores. In my as-close-as-possible-to-pristine Slackware build servers, that is NOT the case. Both Slackbuilds fail due to the insistence that underscores are in the downloaded file name. -- Mark A. Flacy mflacy at verizon.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Apr 22 05:33:03 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 22 Apr 2020 07:33:03 +0200 Subject: [Slackbuilds-users] faac and faad2 build errors. In-Reply-To: <2127080.NthiaO5ijY@sonicmaster.home.flacy> References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> <2127080.NthiaO5ijY@sonicmaster.home.flacy> Message-ID: Il giorno mer 22 apr 2020 alle ore 05:52 Mark A. Flacy via SlackBuilds-users ha scritto: > > Greetings, > > > > Both of these Slackbuilds appear to believe that the artifact downloaded from GitHub contains underscores. > > > > In my as-close-as-possible-to-pristine Slackware build servers, that is NOT the case. Both Slackbuilds fail due to the insistence that underscores are in the downloaded file name. hi Mark, that happens because you are using the browser to download the tarballs so github serves you a different named one: you should use wget to download them and they will be fetched with the correct name. Matteo From Jim.Diamond at acadiau.ca Wed Apr 22 13:33:11 2020 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Wed, 22 Apr 2020 10:33:11 -0300 Subject: [Slackbuilds-users] xawtv looking for love in all the wrong places Message-ID: <20200422133311.GA20382@jdiamond-mb.acadiau.ca> On Slackware64 14.2 I installed xawtv-3.106 using sboinstall. When I try to run it, it says This is xawtv-3.106, running on Linux/x86_64 (5.5.12) WARNING: no plugins found [/tmp/SBo/package-xawtv/usr/lib64/xawtv] ... Apparently, it is looking for some files where they were during the build, but not where they are after the installation. Is there anyone there who will tell me whether they see the same thing, or whether their xawtv cheerfully works (after the build-time files are deleted or moved)? Thanks. Jim From mflacy at verizon.net Wed Apr 22 23:10:48 2020 From: mflacy at verizon.net (Mark A. Flacy) Date: Wed, 22 Apr 2020 18:10:48 -0500 Subject: [Slackbuilds-users] faac and faad2 build errors. In-Reply-To: References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> <2127080.NthiaO5ijY@sonicmaster.home.flacy> Message-ID: <2253811.s5Z28PMx4A@sonicmaster.home.flacy> Greetings, As it so happens, I am NOT using a browser to download those artifacts. I'm running a slackrepo instance in a virtual machine to do these builds. That instance has no customization other than the installation of the slackrepo and slackrepo-hints packages. (And, of course, the user that I use to log into that instance.) -- Mark A. Flacy mflacy at verizon.net > Il giorno mer 22 apr 2020 alle ore 05:52 Mark A. Flacy via > > SlackBuilds-users ha scritto: > > Greetings, > > > > > > > > Both of these Slackbuilds appear to believe that the artifact downloaded > > from GitHub contains underscores. > > > > > > > > In my as-close-as-possible-to-pristine Slackware build servers, that is > > NOT the case. Both Slackbuilds fail due to the insistence that > > underscores are in the downloaded file name. > hi Mark, > > that happens because you are using the browser to download the > tarballs so github serves you a different named one: you should use > wget to download them and they will be fetched with the correct name. > > 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mflacy at verizon.net Wed Apr 22 23:16:08 2020 From: mflacy at verizon.net (Mark A. Flacy) Date: Wed, 22 Apr 2020 18:16:08 -0500 Subject: [Slackbuilds-users] faac and faad2 build errors. In-Reply-To: <2253811.s5Z28PMx4A@sonicmaster.home.flacy> References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> <2253811.s5Z28PMx4A@sonicmaster.home.flacy> Message-ID: <2250622.5k1WQjuOH3@sonicmaster.home.flacy> Greetings, I'll add here that I haven't kept up with the slackrepo git image; I took a look after I wrote the below (of course) and I see that I'm not up to date. I'm doing the updates now and will be sure to grovel here if that turned out to be my problem. -- Mark A. Flacy mflacy at verizon.net Greetings, As it so happens, I am NOT using a browser to download those artifacts. I'm running a slackrepo instance in a virtual machine to do these builds. That instance has no customization other than the installation of the slackrepo and slackrepo-hints packages. (And, of course, the user that I use to log into that instance.) -- Mark A. Flacy mflacy at verizon.net > Il giorno mer 22 apr 2020 alle ore 05:52 Mark A. Flacy via > > SlackBuilds-users ha scritto: > > Greetings, > > > > > > > > Both of these Slackbuilds appear to believe that the artifact downloaded > > from GitHub contains underscores. > > > > > > > > In my as-close-as-possible-to-pristine Slackware build servers, that is > > NOT the case. Both Slackbuilds fail due to the insistence that > > underscores are in the downloaded file name. > hi Mark, > > that happens because you are using the browser to download the > tarballs so github serves you a different named one: you should use > wget to download them and they will be fetched with the correct name. > > 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mflacy at verizon.net Wed Apr 22 23:24:25 2020 From: mflacy at verizon.net (Mark A. Flacy) Date: Wed, 22 Apr 2020 18:24:25 -0500 Subject: [Slackbuilds-users] faac and faad2 build errors. In-Reply-To: <2250622.5k1WQjuOH3@sonicmaster.home.flacy> References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> <2253811.s5Z28PMx4A@sonicmaster.home.flacy> <2250622.5k1WQjuOH3@sonicmaster.home.flacy> Message-ID: <3275298.lsTvKMC4hU@sonicmaster.home.flacy> Greetings, That wasn't the problem. AFAICT, slackrepo uses either curl or wget. -- Mark A. Flacy mflacy at verizon.net Greetings, I'll add here that I haven't kept up with the slackrepo git image; I took a look after I wrote the below (of course) and I see that I'm not up to date. I'm doing the updates now and will be sure to grovel here if that turned out to be my problem. -- Mark A. Flacy mflacy at verizon.net Greetings, As it so happens, I am NOT using a browser to download those artifacts. I'm running a slackrepo instance in a virtual machine to do these builds. That instance has no customization other than the installation of the slackrepo and slackrepo-hints packages. (And, of course, the user that I use to log into that instance.) -- Mark A. Flacy mflacy at verizon.net > Il giorno mer 22 apr 2020 alle ore 05:52 Mark A. Flacy via > > SlackBuilds-users ha scritto: > > Greetings, > > > > > > > > Both of these Slackbuilds appear to believe that the artifact downloaded > > from GitHub contains underscores. > > > > > > > > In my as-close-as-possible-to-pristine Slackware build servers, that is > > NOT the case. Both Slackbuilds fail due to the insistence that > > underscores are in the downloaded file name. > hi Mark, > > that happens because you are using the browser to download the > tarballs so github serves you a different named one: you should use > wget to download them and they will be fetched with the correct name. > > 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at jaxartes.net Thu Apr 23 00:54:29 2020 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Wed, 22 Apr 2020 17:54:29 -0700 Subject: [Slackbuilds-users] xawtv looking for love in all the wrong places In-Reply-To: <20200422133311.GA20382@jdiamond-mb.acadiau.ca> References: <20200422133311.GA20382@jdiamond-mb.acadiau.ca> Message-ID: <8920800.WRUhD0WqqN@wintermute.sprawl.net> On Wednesday, 22 April 2020 06:33:11 PDT Jim Diamond wrote: > On Slackware64 14.2 I installed xawtv-3.106 using sboinstall. > > When I try to run it, it says > > This is xawtv-3.106, running on Linux/x86_64 (5.5.12) > WARNING: no plugins found [/tmp/SBo/package-xawtv/usr/lib64/xawtv] > ... > > Apparently, it is looking for some files where they were during the > build, but not where they are after the installation. > > Is there anyone there who will tell me whether they see the same > thing, or whether their xawtv cheerfully works (after the build-time > files are deleted or moved)? > > Thanks. > > Jim Fixed here: https://git.slackbuilds.org/slackbuilds/commit/?h=user/bosth/ updates&id=50e91c80dfc5d42da68ffeb60c7b19a8dbe95289 Thanks, Ben From jebrhansen+SBo at gmail.com Thu Apr 23 01:07:22 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 22 Apr 2020 19:07:22 -0600 Subject: [Slackbuilds-users] faac and faad2 build errors. In-Reply-To: <3275298.lsTvKMC4hU@sonicmaster.home.flacy> References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> <2253811.s5Z28PMx4A@sonicmaster.home.flacy> <2250622.5k1WQjuOH3@sonicmaster.home.flacy> <3275298.lsTvKMC4hU@sonicmaster.home.flacy> Message-ID: On Wed, Apr 22, 2020, 5:24 PM Mark A. Flacy via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Greetings, > > > > That wasn't the problem. AFAICT, slackrepo uses either curl or wget. > > -- > > Mark A. Flacy > > mflacy at verizon.net > > > On Wednesday, April 22, 2020 06:16:08 PM Mark A. Flacy via > SlackBuilds-users wrote: > > Greetings, > > > > I'll add here that I haven't kept up with the slackrepo git image; I took > a look after I wrote the below (of course) and I see that I'm not up to > date. > > > > I'm doing the updates now and will be sure to grovel here if that turned > out to be my problem. > > -- > > Mark A. Flacy > > mflacy at verizon.net > > > On Wednesday, April 22, 2020 06:10:48 PM Mark A. Flacy via > SlackBuilds-users wrote: > > Greetings, > > > > As it so happens, I am NOT using a browser to download those artifacts. > I'm running a slackrepo instance in a virtual machine to do these builds. > That instance has no customization other than the installation of the > slackrepo and slackrepo-hints packages. (And, of course, the user that I > use to log into that instance.) > > -- > > Mark A. Flacy > > mflacy at verizon.net > > > On Wednesday, April 22, 2020 07:33:03 AM Matteo Bernardini wrote: > > > Il giorno mer 22 apr 2020 alle ore 05:52 Mark A. Flacy via > > > > > > SlackBuilds-users ha scritto: > > > > Greetings, > > > > > > > > > > > > > > > > Both of these Slackbuilds appear to believe that the artifact > downloaded > > > > from GitHub contains underscores. > > > > > > > > > > > > > > > > In my as-close-as-possible-to-pristine Slackware build servers, that is > > > > NOT the case. Both Slackbuilds fail due to the insistence that > > > > underscores are in the downloaded file name. > > > hi Mark, > > > > > > that happens because you are using the browser to download the > > > tarballs so github serves you a different named one: you should use > > > wget to download them and they will be fetched with the correct name. > > > > > > Matteo > This is because slackrepo uses --with-content-disposition when downloading via wget. Can you try updating the hintfile to contain the following? PRAGMA="download_basename" Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mflacy at verizon.net Thu Apr 23 03:16:04 2020 From: mflacy at verizon.net (Mark A. Flacy) Date: Wed, 22 Apr 2020 22:16:04 -0500 Subject: [Slackbuilds-users] faac and faad2 build errors. In-Reply-To: References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> <3275298.lsTvKMC4hU@sonicmaster.home.flacy> Message-ID: <1781734.HETpsWchNj@sonicmaster.home.flacy> Greetings, I most certain can and will! [...time passes...] That solved my issue. (I tested against ponce's branch for -current, but I'll do the same for 14.2 very shortly.) Both faac and faad2 easily built with that pragma. Thank you _very_ much. Mark A. Flacy mflacy at verizon.net On Wed, Apr 22, 2020, 5:24 PM Mark A. Flacy via SlackBuilds-users wrote: Greetings, That wasn't the problem. AFAICT, slackrepo uses either curl or wget. -- Mark A. Flacy mflacy at verizon.net[2] Greetings, I'll add here that I haven't kept up with the slackrepo git image; I took a look after I wrote the below (of course) and I see that I'm not up to date. I'm doing the updates now and will be sure to grovel here if that turned out to be my problem. -- Mark A. Flacy _mflacy at verizon.net_ Greetings, As it so happens, I am NOT using a browser to download those artifacts. I'm running a slackrepo instance in a virtual machine to do these builds. That instance has no customization other than the installation of the slackrepo and slackrepo-hints packages. (And, of course, the user that I use to log into that instance.) -- Mark A. Flacy _mflacy at verizon.net_ > Il giorno mer 22 apr 2020 alle ore 05:52 Mark A. Flacy via > > SlackBuilds-users ha scritto: > > Greetings, > > > > > > > > Both of these Slackbuilds appear to believe that the artifact downloaded > > from GitHub contains underscores. > > > > > > > > In my as-close-as-possible-to-pristine Slackware build servers, that is > > NOT the case. Both Slackbuilds fail due to the insistence that > > underscores are in the downloaded file name. > hi Mark, > > that happens because you are using the browser to download the > tarballs so github serves you a different named one: you should use > wget to download them and they will be fetched with the correct name. > > Matteo This is because slackrepo uses --with-content-disposition when downloading via wget. Can you try updating the hintfile to contain the following? PRAGMA="download_basename" Jeremy -------- [1] mailto:slackbuilds-users at slackbuilds.org [2] mailto:mflacy at verizon.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Thu Apr 23 05:18:05 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 23 Apr 2020 06:18:05 +0100 Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 Message-ID: <20200423051149.GE2780@blackswan.r0t.uk> Hi all, This is a heads-up for anyone using python3-PyQt5. The version we have now has had support for QtWebEngine python bindings split into a separate package - python3-PyQtWebEngine. Here is a list of SlackBuilds that currently depend on python3-PyQt5 and that may /possibly/ need python3-PyQtWebEngine. Since python3-PyQt5 is a dependency of python3-PyQtWebEngine, it's a matter of swapping one for the other in REQUIRES. academic/Mnemosyne academic/veusz audio/carla desktop/anki desktop/kolorcontrol development/jupyter-qtconsole games/pybik libraries/QScintilla-qt5 multimedia/openshot network/Electrum network/onionshare network/persepolis office/ReText python/pyqode.qt system/fs-uae-arcade system/fs-uae-launcher system/laptop-mode-tools So far, `anki' is the only one that I know that needs it and I've adjusted it in my branch. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dickson.tim at googlemail.com Thu Apr 23 10:57:58 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 23 Apr 2020 11:57:58 +0100 Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 In-Reply-To: <20200423051149.GE2780@blackswan.r0t.uk> References: <20200423051149.GE2780@blackswan.r0t.uk> Message-ID: I also spotted that qt5-webkit is marked as a dependency of python3-PyQt5 if it has been split into python3-PyQt5 and python3-PyQtWebEngine does that change the qt5-webkit dependency of python3-PyQt5 to just qt5 , or is the webengine different from webkit? Regards, Tim On 23/04/2020 06:18, Dave Woodfall wrote: > Hi all, > > This is a heads-up for anyone using python3-PyQt5. The version we > have now has had support for QtWebEngine python bindings split into > a separate package - python3-PyQtWebEngine. > > Here is a list of SlackBuilds that currently depend on python3-PyQt5 > and that may /possibly/ need python3-PyQtWebEngine. > > Since python3-PyQt5 is a dependency of python3-PyQtWebEngine, it's a > matter of swapping one for the other in REQUIRES. > > academic/Mnemosyne > academic/veusz > audio/carla > desktop/anki > desktop/kolorcontrol > development/jupyter-qtconsole > games/pybik > libraries/QScintilla-qt5 > multimedia/openshot > network/Electrum > network/onionshare > network/persepolis > office/ReText > python/pyqode.qt > system/fs-uae-arcade > system/fs-uae-launcher > system/laptop-mode-tools > > So far, `anki' is the only one that I know that needs it and I've > adjusted it in my branch. > > > > _______________________________________________ > 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/ > --- This email has been checked for viruses by AVG. https://www.avg.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.coldplayer at gmail.com Thu Apr 23 11:53:12 2020 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Thu, 23 Apr 2020 15:53:12 +0400 Subject: [Slackbuilds-users] ffmpeg4 not building In-Reply-To: References: Message-ID: Hi Luveh, I checked ffmpeg, ffmpeg3 builds with opencv-legacy. The readme of ffmpeg4 does not mention this detail BTW. The ffmpeg4 of slackware64-current builds without the need of openvc though. On Mon, 20 Apr 2020 at 22:13, Luveh Keraph <1.41421 at gmail.com> wrote: > With the provisos mentioned in my previous communication, I was able to > build ffmpeg4. > > On Mon, Apr 20, 2020 at 11:36 AM Luveh Keraph <1.41421 at gmail.com> wrote: > >> It is building all right, in that it did not choke on opencv as I >> reported here before. However, I could not get opencv-legacy to build with >> tesseract already installed. I had to remove tesseract, build and install >> opencv-legacy, build and install tesseract, and then launch the build of >> ffmpeg4. The build job for ffmpeg4 is still ongoing; I'll report on the >> outcome. >> >> On Mon, Apr 20, 2020 at 8:49 AM Jheengut Pritvi >> wrote: >> >>> Hi, >>> I have not tried the latest version but can you confirm if the legacy >>> opencv is needed instead. >>> >>> >>> On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41421 at gmail.com> wrote: >>> >>>> I am using the following ffmpeg4.sqf file in a freshly installed (and >>>> up-to-date) 14.2 system: >>>> >>>> libass >>>> chromaprint >>>> frei0r >>>> ladspa_sdk >>>> libaom >>>> libbluray >>>> libbs2b >>>> celt >>>> libdc1394 >>>> libfdk-aac >>>> flite >>>> libgme >>>> gsm >>>> libiec61883 >>>> libavc1394 >>>> libilbc >>>> libmodplug >>>> lame >>>> opencore-amr >>>> opencv >>>> opus >>>> rtmpdump >>>> rubberband >>>> snappy >>>> speex >>>> tesseract >>>> twolame >>>> vid.stab >>>> libwebp >>>> x264 >>>> x265 >>>> xvidcore >>>> zeromq >>>> zvbi >>>> ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes >>>> LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes >>>> LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes >>>> LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes >>>> LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes >>>> LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes >>>> LIBXVID=yes LIBZMQ=yes LIBZVBI=yes >>>> >>>> I encountered the following issues: >>>> >>>> 1. var-plugin-sdk is required for rubberband. >>>> 2. leptonica is required for tesseract (I think). >>>> 3. ffmpeg4 seems to be looking for opencv, while the script above >>>> installs opencv4: >>>> >>>> ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c >>>> ffmpeg-4.1/tests/checkasm/synth_filter.c >>>> ffmpeg-4.1/tests/checkasm/vf_nlmeans.c >>>> ffmpeg-4.1/tests/tiny_psnr.c >>>> ffmpeg-4.1/COPYING.LGPLv2.1 >>>> ffmpeg-4.1/README.md >>>> ffmpeg-4.1/CONTRIBUTING.md >>>> ERROR: opencv not found using pkg-config >>>> >>>> # pkg-config --list-all|grep opencv >>>> opencv4 OpenCV - Open Source Computer >>>> Vision Library >>>> _______________________________________________ >>>> 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/ >>> >>> _______________________________________________ > 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 slackbuilds.org Thu Apr 23 12:02:21 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 23 Apr 2020 13:02:21 +0100 Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 In-Reply-To: References: <20200423051149.GE2780@blackswan.r0t.uk> Message-ID: <20200423120221.GD22086@blackswan.r0t.uk> On 2020-04-23 11:57, Tim Dickson put forth the proposition: > I also spotted that qt5-webkit is marked as a dependency of python3-PyQt5 > if it has been split into python3-PyQt5 and python3-PyQtWebEngine does that > change the qt5-webkit dependency of python3-PyQt5 to just qt5 , or is the > webengine different from webkit? > Regards, Tim I've just had a test build - python3-PyQt5 and python3-PyQtWebEngine will build without qt5-webkit, but I think it will take some testing to see if each application at the end of the chain would run or not. So at the moment it looks like qt5-webkit could be optional for python3-PyQt5. > On 23/04/2020 06:18, Dave Woodfall wrote: > > Hi all, > > > > This is a heads-up for anyone using python3-PyQt5. The version we > > have now has had support for QtWebEngine python bindings split into > > a separate package - python3-PyQtWebEngine. > > > > Here is a list of SlackBuilds that currently depend on python3-PyQt5 > > and that may /possibly/ need python3-PyQtWebEngine. > > > > Since python3-PyQt5 is a dependency of python3-PyQtWebEngine, it's a > > matter of swapping one for the other in REQUIRES. > > > > academic/Mnemosyne > > academic/veusz > > audio/carla > > desktop/anki > > desktop/kolorcontrol > > development/jupyter-qtconsole > > games/pybik > > libraries/QScintilla-qt5 > > multimedia/openshot > > network/Electrum > > network/onionshare > > network/persepolis > > office/ReText > > python/pyqode.qt > > system/fs-uae-arcade > > system/fs-uae-launcher > > system/laptop-mode-tools > > > > So far, `anki' is the only one that I know that needs it and I've > > adjusted it in my branch. > > > > > > > > _______________________________________________ > > 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/ > > > > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From 1.41421 at gmail.com Thu Apr 23 13:23:16 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Thu, 23 Apr 2020 07:23:16 -0600 Subject: [Slackbuilds-users] ffmpeg4 not building In-Reply-To: References: Message-ID: Like I reported, 14.2 ffmpeg4 will not build with opencv, but it will with opencv-legacy - provided that opencv-legacy is built before tesseract. opencv (or opencv-legacy) is anyway optional for ffmpeg (both 3 and 4). On Thu, Apr 23, 2020 at 5:51 AM Jheengut Pritvi wrote: > Hi Luveh, > > I checked ffmpeg, ffmpeg3 builds with opencv-legacy. > The readme of ffmpeg4 does not mention this detail BTW. > > The ffmpeg4 of slackware64-current builds without the need of openvc > though. > > On Mon, 20 Apr 2020 at 22:13, Luveh Keraph <1.41421 at gmail.com> wrote: > >> With the provisos mentioned in my previous communication, I was able to >> build ffmpeg4. >> >> On Mon, Apr 20, 2020 at 11:36 AM Luveh Keraph <1.41421 at gmail.com> wrote: >> >>> It is building all right, in that it did not choke on opencv as I >>> reported here before. However, I could not get opencv-legacy to build with >>> tesseract already installed. I had to remove tesseract, build and install >>> opencv-legacy, build and install tesseract, and then launch the build of >>> ffmpeg4. The build job for ffmpeg4 is still ongoing; I'll report on the >>> outcome. >>> >>> On Mon, Apr 20, 2020 at 8:49 AM Jheengut Pritvi >>> wrote: >>> >>>> Hi, >>>> I have not tried the latest version but can you confirm if the legacy >>>> opencv is needed instead. >>>> >>>> >>>> On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41421 at gmail.com> wrote: >>>> >>>>> I am using the following ffmpeg4.sqf file in a freshly installed (and >>>>> up-to-date) 14.2 system: >>>>> >>>>> libass >>>>> chromaprint >>>>> frei0r >>>>> ladspa_sdk >>>>> libaom >>>>> libbluray >>>>> libbs2b >>>>> celt >>>>> libdc1394 >>>>> libfdk-aac >>>>> flite >>>>> libgme >>>>> gsm >>>>> libiec61883 >>>>> libavc1394 >>>>> libilbc >>>>> libmodplug >>>>> lame >>>>> opencore-amr >>>>> opencv >>>>> opus >>>>> rtmpdump >>>>> rubberband >>>>> snappy >>>>> speex >>>>> tesseract >>>>> twolame >>>>> vid.stab >>>>> libwebp >>>>> x264 >>>>> x265 >>>>> xvidcore >>>>> zeromq >>>>> zvbi >>>>> ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes >>>>> LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes >>>>> LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes >>>>> LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes >>>>> LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes >>>>> LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes >>>>> LIBXVID=yes LIBZMQ=yes LIBZVBI=yes >>>>> >>>>> I encountered the following issues: >>>>> >>>>> 1. var-plugin-sdk is required for rubberband. >>>>> 2. leptonica is required for tesseract (I think). >>>>> 3. ffmpeg4 seems to be looking for opencv, while the script above >>>>> installs opencv4: >>>>> >>>>> ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c >>>>> ffmpeg-4.1/tests/checkasm/synth_filter.c >>>>> ffmpeg-4.1/tests/checkasm/vf_nlmeans.c >>>>> ffmpeg-4.1/tests/tiny_psnr.c >>>>> ffmpeg-4.1/COPYING.LGPLv2.1 >>>>> ffmpeg-4.1/README.md >>>>> ffmpeg-4.1/CONTRIBUTING.md >>>>> ERROR: opencv not found using pkg-config >>>>> >>>>> # pkg-config --list-all|grep opencv >>>>> opencv4 OpenCV - Open Source Computer >>>>> Vision Library >>>>> _______________________________________________ >>>>> 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/ >>>> >>>> _______________________________________________ >> 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Thu Apr 23 16:40:34 2020 From: yalhcru at gmail.com (B Watson) Date: Thu, 23 Apr 2020 12:40:34 -0400 Subject: [Slackbuilds-users] faac and faad2 build errors. In-Reply-To: <2127080.NthiaO5ijY@sonicmaster.home.flacy> References: <2127080.NthiaO5ijY.ref@sonicmaster.home.flacy> <2127080.NthiaO5ijY@sonicmaster.home.flacy> Message-ID: On 4/21/20, Mark A. Flacy via SlackBuilds-users wrote: > Greetings, > > Both of these Slackbuilds appear to believe that the artifact downloaded > from GitHub contains underscores. > > In my as-close-as-possible-to-pristine Slackware build servers, that is > NOT the case. Both Slackbuilds fail due to the insistence that > underscores are in the downloaded file name. I've been going through and fixing up issues with github URLs like these, faac and faad2 have both gotten the treatment and the fixed versions will appear in this week's update. The problem is that github will allow *anything* as the filename portion of the URL. Whether or not your downloading tool (wget, curl, browser, whatever) saves the file with the "anything" or the server-provided filename, depends on whether your tool uses the Content-disposition HTTP header. From yalhcru at gmail.com Thu Apr 23 16:43:42 2020 From: yalhcru at gmail.com (B Watson) Date: Thu, 23 Apr 2020 12:43:42 -0400 Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 In-Reply-To: <20200423051149.GE2780@blackswan.r0t.uk> References: <20200423051149.GE2780@blackswan.r0t.uk> Message-ID: On 4/23/20, Dave Woodfall wrote: > audio/carla I just built carla and did some minimal testing, it didn't need python3-PyQtWebEngine. From dave at slackbuilds.org Thu Apr 23 16:47:42 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 23 Apr 2020 17:47:42 +0100 Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 In-Reply-To: References: <20200423051149.GE2780@blackswan.r0t.uk> Message-ID: <20200423164742.GB9901@blackswan.r0t.uk> On 2020-04-23 12:43, B Watson put forth the proposition: > On 4/23/20, Dave Woodfall wrote: > > > audio/carla > > I just built carla and did some minimal testing, it didn't need > python3-PyQtWebEngine. Thanks. That leaves: academic/Mnemosyne academic/veusz desktop/kolorcontrol development/jupyter-qtconsole games/pybik libraries/QScintilla-qt5 multimedia/openshot network/Electrum network/onionshare network/persepolis office/ReText python/pyqode.qt system/fs-uae-arcade system/fs-uae-launcher system/laptop-mode-tools -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From fellype at gmail.com Thu Apr 23 17:30:29 2020 From: fellype at gmail.com (Fellype) Date: Thu, 23 Apr 2020 14:30:29 -0300 Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 In-Reply-To: <20200423164742.GB9901@blackswan.r0t.uk> References: <20200423051149.GE2780@blackswan.r0t.uk> <20200423164742.GB9901@blackswan.r0t.uk> Message-ID: Hi all, academic/veusz builds fine *without* python3-PyQtWebEngine Regards, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Thu Apr 23 17:34:14 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 23 Apr 2020 18:34:14 +0100 Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 In-Reply-To: References: <20200423051149.GE2780@blackswan.r0t.uk> <20200423164742.GB9901@blackswan.r0t.uk> Message-ID: <20200423173414.GC9901@blackswan.r0t.uk> On 2020-04-23 14:30, Fellype put forth the proposition: > Hi all, > > academic/veusz builds fine *without* python3-PyQtWebEngine > > Regards, > > Fellype academic/Mnemosyne desktop/kolorcontrol development/jupyter-qtconsole games/pybik libraries/QScintilla-qt5 multimedia/openshot network/Electrum network/onionshare network/persepolis office/ReText python/pyqode.qt system/fs-uae-arcade system/fs-uae-launcher system/laptop-mode-tools -------------- 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 Fri Apr 24 00:58:08 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 24 Apr 2020 07:58:08 +0700 Subject: [Slackbuilds-users] Nix build requires newer library In-Reply-To: <18aae9c3-3b5b-c983-d5d2-929c4e0bbc08@server.ky> References: <18aae9c3-3b5b-c983-d5d2-929c4e0bbc08@server.ky> Message-ID: <581173e7-330f-167c-f3d7-30215bb25641@slackbuilds.org> > It looks like the latest version of the Nix package manager requires a > newer version of lib-boost (or some other library) than what the latest > stable has.? What's the best way to deal with this?? Is there > documentation on it? Hi If it requirer higher version than what we have in Slackware, then it will have to wait until next Slackware gets released. -- 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 willysr at slackbuilds.org Fri Apr 24 01:39:42 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 24 Apr 2020 08:39:42 +0700 Subject: [Slackbuilds-users] Updates - 20200424.1 Message-ID: <2321ebc6-5575-7bf4-46c2-074408ab12af@slackbuilds.org> Hi all Forgive me to send the public update one day ahead of normal public update on weekend. I was lost in time and was thinking that today is Saturday. Anyway, this batch push more updates to Qt5-related builds, hopefully this should fix the remaining issue. Fri Apr 24 01:19:39 UTC 2020 academic/rpy2: Updated for version 3.3.1. desktop/anki: Add REQUIRES python3-PyQtWebEngine. desktop/find-cursor: Updated for version 1.6. development/Sphinx: Fix README. development/cgit: Updated for version 1.2.3. development/jdk11: Updated for version 11.0.7. development/jdk12: Update script. development/jdk13: Update script. development/jdk14: Added (Java Platform SDK). games/edgar: Updated for version 1.33. games/ppsspp: Rename .info file to avoid confusion. gis/saga-gis: Add clarifying note about OpenCV. graphics/nomacs: Updated for version 3.14.2. ham/chirp: Updated for version 20200409. libraries/BeautifulSoup4: Updated for version 4.9.0. libraries/hdf5: Updated for version 1.10.6. libraries/libuv: Updated for version 1.37.0. libraries/med: Updated for version 4.0.0. libraries/opencv: Updated for version 4.3.0 libraries/pcre2: Updated for version 10.34 libraries/qt5-styleplugins: Patched for qt5-5.12.8. libraries/qt5-webkit: Fix source directory. libraries/qt5: Update README. misc/dmg2img: added missing man page multimedia/LBRY: Updated for version 0.45.0. multimedia/dvdbackup: Updated for version 0.4.2. multimedia/flashplayer-plugin: Updated for version 32.0.0.363. multimedia/pepperflash-plugin: Updated for version 32.0.0.363. multimedia/plexmediaserver: Updated for v 1.19.1.2701-6327e27bf. multimedia/strawberry: Updated for version 0.6.9. multimedia/xawtv: Fix path issue. network/RTL8192: Added (Realtek RTL8192 chip Driver). network/bluejeans: Updated for version 2.1.1. network/dnscrypt-proxy: Updated for version 2.0.42. network/easyrsa: Updated for version 3.0.7. network/keepalived: Updated for version 2.0.20. network/neomutt: Updated for version 20200417. network/pCloudDrive: Updated for version 1.8.0. network/pexip-infinity-connect: Updated for v 1.6.0.52922.63.120. network/qutebrowser-tox: Updated for version 1.10.2. network/vivaldi: Updated for version 3.0.1874.23. network/wp-cli: Added (A command line interface for WordPress). network/yle-dl: Updated for version 20200419. office/gnucash-docs: Updated for version 3.10. office/gnucash: Updated for version 3.10. office/xournalpp: Updated for version 1.0.18. python/pytables: Removed (abandoned and not compatible with hdf5). python/python-zipp: Updated dependencies. python/python3-setuptools_autover: Updated for version 1.0.2. python/python3-uth: Updated for version 1.1.1. ruby/rubygem-asciidoctor: Updated for version 2.0.10. system/ansible: Updated for version 2.9.7. system/cluster-glue: Updated for version 20161102_afaeeb. system/docker-proxy: Fix MD5SUM. system/fence-agents: Updated for version 4.5.2. system/heartbeat: Added (Linux-HA heartbeat). system/nvme-cli: Updated for version 1.11. system/resource-agents: Updated for version 4.5.0. system/worker: Updated for version 4.4.0. +--------------------------+ -- 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 Fri Apr 24 02:03:49 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 23 Apr 2020 19:03:49 -0700 Subject: [Slackbuilds-users] Updates - 20200424.1 In-Reply-To: <2321ebc6-5575-7bf4-46c2-074408ab12af@slackbuilds.org> References: <2321ebc6-5575-7bf4-46c2-074408ab12af@slackbuilds.org> Message-ID: On 4/23/20 6:39 PM, Willy Sudiarto Raharjo wrote: > Hi all > > Forgive me to send the public update one day ahead of normal public > update on weekend. I was lost in time and was thinking that today is > Saturday. > Well...since I was in the process of doing updates this evening, on a THURSDAY! https://youtu.be/sPbjPOgRtyA -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri Apr 24 02:05:43 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 24 Apr 2020 09:05:43 +0700 Subject: [Slackbuilds-users] Updates - 20200424.1 In-Reply-To: References: <2321ebc6-5575-7bf4-46c2-074408ab12af@slackbuilds.org> Message-ID: <067a86cf-11e8-c2aa-1f79-d9c9e1734496@slackbuilds.org> > Well...since I was in the process of doing updates this evening, on a > THURSDAY! Sorry about that :) anyway, push it, and i will probably push it again on this Saturday -- 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 Fri Apr 24 02:10:30 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 23 Apr 2020 19:10:30 -0700 Subject: [Slackbuilds-users] Development/jdk download URL points to a login page Message-ID: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> Getting directed to a login page is HIGHLY annoying, as many you may agree. more "direct" downloads are here: https://www.java.com/en/download/linux_manual.jsp Some of the links appear to be wget compatible (?). -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dave at slackbuilds.org Fri Apr 24 02:13:48 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 24 Apr 2020 03:13:48 +0100 Subject: [Slackbuilds-users] Development/jdk download URL points to a login page In-Reply-To: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> References: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> Message-ID: <20200424021348.GA7151@blackswan.r0t.uk> On 2020-04-23 19:10, King Beowulf put forth the proposition: > Getting directed to a login page is HIGHLY annoying, as many you may agree. > > more "direct" downloads are here: > > https://www.java.com/en/download/linux_manual.jsp > > Some of the links appear to be wget compatible (?). > > -Ed It's been like that for a long time. You need to agree to a license agreement on the page before you can download, at least for the new versions. Unless that's changed lately. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From kingbeowulf at gmail.com Fri Apr 24 02:18:42 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 23 Apr 2020 19:18:42 -0700 Subject: [Slackbuilds-users] Development/jdk download URL points to a login page In-Reply-To: <20200424021348.GA7151@blackswan.r0t.uk> References: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> <20200424021348.GA7151@blackswan.r0t.uk> Message-ID: <25075ed7-bfd3-0f30-fbec-efe75a80f954@gmail.com> On 4/23/20 7:13 PM, Dave Woodfall wrote: > On 2020-04-23 19:10, > King Beowulf put forth the proposition: >> Getting directed to a login page is HIGHLY annoying, as many you may agree. >> >> more "direct" downloads are here: >> >> https://www.java.com/en/download/linux_manual.jsp >> >> Some of the links appear to be wget compatible (?). >> >> -Ed > > It's been like that for a long time. You need to agree to a license > agreement on the page before you can download, at least for the new > versions. Unless that's changed lately. > > No...this is an ACTUAL login page asking for userID and password. It's been awhile since I downloaded it, and I recall that the license page was NOT https://login.oracle.com/mysso/signon.jsp but and actual page of license text with agree/cancel buttons. Unless Firefox here is doing something weird. -Ed -------------- 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 Fri Apr 24 02:22:22 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 23 Apr 2020 19:22:22 -0700 Subject: [Slackbuilds-users] Development/jdk download URL points to a login page In-Reply-To: <20200424021348.GA7151@blackswan.r0t.uk> References: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> <20200424021348.GA7151@blackswan.r0t.uk> Message-ID: <47f8672e-b88a-7a6e-6d9b-a3979fe55d9f@gmail.com> On 4/23/20 7:13 PM, Dave Woodfall wrote: > On 2020-04-23 19:10, > King Beowulf put forth the proposition: >> Getting directed to a login page is HIGHLY annoying, as many you may agree. >> >> more "direct" downloads are here: >> >> https://www.java.com/en/download/linux_manual.jsp >> >> Some of the links appear to be wget compatible (?). >> >> -Ed > > It's been like that for a long time. You need to agree to a license > agreement on the page before you can download, at least for the new > versions. Unless that's changed lately. > > I should also add that another "normal" download area is: https://www.oracle.com/java/technologies/javase-downloads.html -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dave at slackbuilds.org Fri Apr 24 02:40:55 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 24 Apr 2020 03:40:55 +0100 Subject: [Slackbuilds-users] Development/jdk download URL points to a login page In-Reply-To: <25075ed7-bfd3-0f30-fbec-efe75a80f954@gmail.com> References: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> <20200424021348.GA7151@blackswan.r0t.uk> <25075ed7-bfd3-0f30-fbec-efe75a80f954@gmail.com> Message-ID: <20200424024054.GB7151@blackswan.r0t.uk> On 2020-04-23 19:18, King Beowulf put forth the proposition: > On 4/23/20 7:13 PM, Dave Woodfall wrote: > > On 2020-04-23 19:10, > > King Beowulf put forth the proposition: > >> Getting directed to a login page is HIGHLY annoying, as many you may agree. > >> > >> more "direct" downloads are here: > >> > >> https://www.java.com/en/download/linux_manual.jsp > >> > >> Some of the links appear to be wget compatible (?). > >> > >> -Ed > > > > It's been like that for a long time. You need to agree to a license > > agreement on the page before you can download, at least for the new > > versions. Unless that's changed lately. > > > > > > No...this is an ACTUAL login page asking for userID and password. It's > been awhile since I downloaded it, and I recall that the license page > was NOT > > https://login.oracle.com/mysso/signon.jsp > > but and actual page of license text with agree/cancel buttons. > > Unless Firefox here is doing something weird. > > -Ed Ah I see. It gave me a telling off for `using a bookmark' to go directly to that second link. No login for me, but I do remember coming across a login page when I was looking for the latest version either last year or early this year. rworkman might know more. I notice that they have also changed the names of the downloads, or at least when I was looking for Linux source all I could find had `bin' in the file name. Unless that is a binary, but then where is the source? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From alex at dcclost.com Fri Apr 24 05:44:56 2020 From: alex at dcclost.com (Alexander Grotewohl) Date: Fri, 24 Apr 2020 05:44:56 +0000 Subject: [Slackbuilds-users] Development/jdk download URL points to a login page In-Reply-To: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> References: <23053a71-26ed-f22d-8e14-449133b9133b@gmail.com> Message-ID: This link also only provides the jre.. -- Alexander Grotewohl https://dcclost.com ________________________________ From: SlackBuilds-users on behalf of King Beowulf Sent: Thursday, April 23, 2020 10:10:30 PM To: SlackBuilds.org Users List Subject: [Slackbuilds-users] Development/jdk download URL points to a login page Getting directed to a login page is HIGHLY annoying, as many you may agree. more "direct" downloads are here: https://www.java.com/en/download/linux_manual.jsp Some of the links appear to be wget compatible (?). -Ed -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Fri Apr 24 08:39:25 2020 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 24 Apr 2020 18:39:25 +1000 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? Message-ID: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> At the moment, SBo builds of python3 on both my daily machine and a clean VM result in the include files being placed into /usr/include/python3.7m (rather than a plain /usr/include/python3.7). Apparently the different paths signified use (or non-use) of an internal memory allocator which is on by default but controllable using the --with(out)-pymalloc configure option when building python3. I've tested this and the --without-pymalloc does result in /usr/include/pyton3.7 (not python3.7m). BTW this behaviour has changed in 3.8 where everything goes into /usr/include/pyton3.8 (see -current, also see https://bugs.python.org/issue36707). Before proceeding here with a complaint about other packages wrongly hard coding python-related .h files into /usr/include/python3.7, rather than python3.7m, could people first confirm that their python3 installation is using /usr/include/python3.7m, as mine does, please? Thanks, chris From dave at slackbuilds.org Fri Apr 24 08:48:46 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 24 Apr 2020 09:48:46 +0100 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> Message-ID: <20200424084846.GC7151@blackswan.r0t.uk> On 2020-04-24 18:39, Christoph Willing put forth the proposition: > At the moment, SBo builds of python3 on both my daily machine and a > clean VM result in the include files being placed into > /usr/include/python3.7m (rather than a plain /usr/include/python3.7). > > Apparently the different paths signified use (or non-use) of an internal > memory allocator which is on by default but controllable using the > --with(out)-pymalloc configure option when building python3. I've tested > this and the --without-pymalloc does result in /usr/include/pyton3.7 > (not python3.7m). > > BTW this behaviour has changed in 3.8 where everything goes into > /usr/include/pyton3.8 (see -current, also see > https://bugs.python.org/issue36707). > > > Before proceeding here with a complaint about other packages wrongly > hard coding python-related .h files into /usr/include/python3.7, rather > than python3.7m, could people first confirm that their python3 > installation is using /usr/include/python3.7m, as mine does, please? Yup. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From mrvladislavovich at gmail.com Fri Apr 24 08:51:10 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Fri, 24 Apr 2020 12:51:10 +0400 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> Message-ID: <20200424085110.GA551@lenovo.myrequiem.net> Re: Christoph Willing 24.04.2020 <74588ed6-9214-79c1-3b2b-9fb252a5779d at linux.com> >At the moment, SBo builds of python3 on both my daily machine and a >clean VM result in the include files being placed into >/usr/include/python3.7m (rather than a plain /usr/include/python3.7). > >Apparently the different paths signified use (or non-use) of an internal >memory allocator which is on by default but controllable using the >--with(out)-pymalloc configure option when building python3. I've tested >this and the --without-pymalloc does result in /usr/include/pyton3.7 >(not python3.7m). > >BTW this behaviour has changed in 3.8 where everything goes into >/usr/include/pyton3.8 (see -current, also see >https://bugs.python.org/issue36707). > > >Before proceeding here with a complaint about other packages wrongly >hard coding python-related .h files into /usr/include/python3.7, rather >than python3.7m, could people first confirm that their python3 >installation is using /usr/include/python3.7m, as mine does, please? > > >Thanks, >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/ > Yes, Python3.7: /usr/include/python3.7m Python3.8: /usr/include/python3.8 From dickson.tim at googlemail.com Fri Apr 24 09:45:52 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 24 Apr 2020 10:45:52 +0100 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <20200424085110.GA551@lenovo.myrequiem.net> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> Message-ID: i've a reasonable collection of python .sbo packages installed, and sip.h is the only file in /usr/include/python3.7 which is from stock slackware 14.2 sip-4.18 package Regards, Tim On 24/04/2020 09:51, MyRequiem wrote: > Re: Christoph Willing 24.04.2020 > <74588ed6-9214-79c1-3b2b-9fb252a5779d at linux.com> >> At the moment, SBo builds of python3 on both my daily machine and a >> clean VM result in the include files being placed into >> /usr/include/python3.7m (rather than a plain /usr/include/python3.7). >> >> Apparently the different paths signified use (or non-use) of an internal >> memory allocator which is on by default but controllable using the >> --with(out)-pymalloc configure option when building python3. I've tested >> this and the --without-pymalloc does result in /usr/include/pyton3.7 >> (not python3.7m). >> >> BTW this behaviour has changed in 3.8 where everything goes into >> /usr/include/pyton3.8 (see -current, also see >> https://bugs.python.org/issue36707). >> >> >> Before proceeding here with a complaint about other packages wrongly >> hard coding python-related .h files into /usr/include/python3.7, rather >> than python3.7m, could people first confirm that their python3 >> installation is using /usr/include/python3.7m, as mine does, please? >> >> >> Thanks, >> 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/ >> > Yes, > Python3.7: /usr/include/python3.7m > Python3.8: /usr/include/python3.8 > _______________________________________________ > 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/ > --- This email has been checked for viruses by AVG. https://www.avg.com From chris.willing at linux.com Fri Apr 24 12:18:35 2020 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 24 Apr 2020 22:18:35 +1000 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> Message-ID: On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: > i've a reasonable collection of python .sbo packages installed, and > sip.h is the only file in /usr/include/python3.7 > which is from stock slackware 14.2 sip-4.18 package > Regards, Tim > Thanks all for the replies confirming the python3 include directories. Tim, I think you mean /usr/include/python2.7 for the sip.h from stock Slackware sip-4.18-x86_64-1 package? If you have a /usr/include/python3.7/sip.h (the one which should be in /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. I emailed the maintainer a few days ago with a version-independent method to install in the correct location but haven't heard back about it yet (so cc'd here now as a reminder). I just thought I should also check here in case there was something whacky about my own setup but based on the feedback, as well as noticing that AlienBob's python3 package uses /usr/include/python3.7m, I"m sure now that the problem is with the python3-sip SlackBuild. It looks very close to the SlackBuild in -current but of course -current uses python 3.8 where the issue has been fixed, rather than python 3.7 as on SBo. chris > > On 24/04/2020 09:51, MyRequiem wrote: >> Re: Christoph Willing 24.04.2020 >> <74588ed6-9214-79c1-3b2b-9fb252a5779d at linux.com> >>> At the moment, SBo builds of python3 on both my daily machine and a >>> clean VM result in the include files being placed into >>> /usr/include/python3.7m (rather than a plain /usr/include/python3.7). >>> >>> Apparently the different paths signified use (or non-use) of an internal >>> memory allocator which is on by default but controllable using the >>> --with(out)-pymalloc configure option when building python3. I've tested >>> this and the --without-pymalloc does result in /usr/include/pyton3.7 >>> (not python3.7m). >>> >>> BTW this behaviour has changed in 3.8 where everything goes into >>> /usr/include/pyton3.8 (see -current, also see >>> https://bugs.python.org/issue36707). >>> >>> >>> Before proceeding here with a complaint about other packages wrongly >>> hard coding python-related .h files into /usr/include/python3.7, rather >>> than python3.7m, could people first confirm that their python3 >>> installation is using /usr/include/python3.7m, as mine does, please? >>> >>> >>> Thanks, >>> 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/ >>> >> Yes, >> Python3.7: /usr/include/python3.7m >> Python3.8: /usr/include/python3.8 >> _______________________________________________ >> 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/ >> > > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > _______________________________________________ > 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 dave at slackbuilds.org Fri Apr 24 12:24:53 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 24 Apr 2020 13:24:53 +0100 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> Message-ID: <20200424122452.GD7151@blackswan.r0t.uk> On 2020-04-24 22:18, Christoph Willing put forth the proposition: > On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: > > i've a reasonable collection of python .sbo packages installed, and > > sip.h is the only file in /usr/include/python3.7 > > which is from stock slackware 14.2 sip-4.18 package > > Regards, Tim > > > > Thanks all for the replies confirming the python3 include directories. > > Tim, I think you mean /usr/include/python2.7 for the sip.h from stock > Slackware sip-4.18-x86_64-1 package? > > If you have a /usr/include/python3.7/sip.h (the one which should be in > /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. > > I emailed the maintainer a few days ago with a version-independent > method to install in the correct location but haven't heard back about > it yet (so cc'd here now as a reminder). I just thought I should also > check here in case there was something whacky about my own setup but > based on the feedback, as well as noticing that AlienBob's python3 > package uses /usr/include/python3.7m, I"m sure now that the problem is > with the python3-sip SlackBuild. It looks very close to the SlackBuild > in -current but of course -current uses python 3.8 where the issue has > been fixed, rather than python 3.7 as on SBo. > > chris I maintain python3-sip now, so if we are all in agreement that we use python3.7 I'll fix that this week. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Fri Apr 24 12:30:15 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 24 Apr 2020 13:30:15 +0100 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <20200424122452.GD7151@blackswan.r0t.uk> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> <20200424122452.GD7151@blackswan.r0t.uk> Message-ID: <20200424123015.GE7151@blackswan.r0t.uk> On 2020-04-24 13:24, Dave Woodfall put forth the proposition: > On 2020-04-24 22:18, > Christoph Willing put forth the proposition: > > On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: > > > i've a reasonable collection of python .sbo packages installed, and > > > sip.h is the only file in /usr/include/python3.7 > > > which is from stock slackware 14.2 sip-4.18 package > > > Regards, Tim > > > > > > > Thanks all for the replies confirming the python3 include directories. > > > > Tim, I think you mean /usr/include/python2.7 for the sip.h from stock > > Slackware sip-4.18-x86_64-1 package? > > > > If you have a /usr/include/python3.7/sip.h (the one which should be in > > /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. > > > > I emailed the maintainer a few days ago with a version-independent > > method to install in the correct location but haven't heard back about > > it yet (so cc'd here now as a reminder). I just thought I should also > > check here in case there was something whacky about my own setup but > > based on the feedback, as well as noticing that AlienBob's python3 > > package uses /usr/include/python3.7m, I"m sure now that the problem is > > with the python3-sip SlackBuild. It looks very close to the SlackBuild > > in -current but of course -current uses python 3.8 where the issue has > > been fixed, rather than python 3.7 as on SBo. > > > > chris > > I maintain python3-sip now, so if we are all in agreement that we use > python3.7 I'll fix that this week. I got that the wrong way around. We're want to use /usr/include/python3.7m right? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From chris.willing at linux.com Fri Apr 24 12:42:15 2020 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 24 Apr 2020 22:42:15 +1000 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <20200424123015.GE7151@blackswan.r0t.uk> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> <20200424122452.GD7151@blackswan.r0t.uk> <20200424123015.GE7151@blackswan.r0t.uk> Message-ID: <7173702c-8e0d-468d-e5f1-d215b783ecaf@linux.com> On 24/4/20 10:30 pm, Dave Woodfall wrote: > On 2020-04-24 13:24, > Dave Woodfall put forth the proposition: >> On 2020-04-24 22:18, >> Christoph Willing put forth the proposition: >>> On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: >>>> i've a reasonable collection of python .sbo packages installed, and >>>> sip.h is the only file in /usr/include/python3.7 >>>> which is from stock slackware 14.2 sip-4.18 package >>>> Regards, Tim >>>> >>> >>> Thanks all for the replies confirming the python3 include directories. >>> >>> Tim, I think you mean /usr/include/python2.7 for the sip.h from stock >>> Slackware sip-4.18-x86_64-1 package? >>> >>> If you have a /usr/include/python3.7/sip.h (the one which should be in >>> /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. >>> >>> I emailed the maintainer a few days ago with a version-independent >>> method to install in the correct location but haven't heard back about >>> it yet (so cc'd here now as a reminder). I just thought I should also >>> check here in case there was something whacky about my own setup but >>> based on the feedback, as well as noticing that AlienBob's python3 >>> package uses /usr/include/python3.7m, I"m sure now that the problem is >>> with the python3-sip SlackBuild. It looks very close to the SlackBuild >>> in -current but of course -current uses python 3.8 where the issue has >>> been fixed, rather than python 3.7 as on SBo. >>> >>> chris >> >> I maintain python3-sip now, so if we are all in agreement that we use >> python3.7 I'll fix that this week. > > I got that the wrong way around. > > We're want to use /usr/include/python3.7m right? > Yes Dave, that's correct. Although you could hard code it to python3.7m, I"d suggest a version-independent mechanism like changing the existing line: -e "/usr/include/python$PYTHONVER" \ to: -e $(pkg-config --cflags-only-I python3 | sed -e 's/^-I//' ) \ This uses pkg-config to find the "official" include path and strips the leading '-I'. Then sip.h would be installed in the correct location regardless of the python version. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From dave at slackbuilds.org Fri Apr 24 12:44:51 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 24 Apr 2020 13:44:51 +0100 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <7173702c-8e0d-468d-e5f1-d215b783ecaf@linux.com> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> <20200424122452.GD7151@blackswan.r0t.uk> <20200424123015.GE7151@blackswan.r0t.uk> <7173702c-8e0d-468d-e5f1-d215b783ecaf@linux.com> Message-ID: <20200424124451.GF7151@blackswan.r0t.uk> On 2020-04-24 22:42, Christoph Willing put forth the proposition: > On 24/4/20 10:30 pm, Dave Woodfall wrote: > > On 2020-04-24 13:24, > > Dave Woodfall put forth the proposition: > >> On 2020-04-24 22:18, > >> Christoph Willing put forth the proposition: > >>> On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: > >>>> i've a reasonable collection of python .sbo packages installed, and > >>>> sip.h is the only file in /usr/include/python3.7 > >>>> which is from stock slackware 14.2 sip-4.18 package > >>>> Regards, Tim > >>>> > >>> > >>> Thanks all for the replies confirming the python3 include directories. > >>> > >>> Tim, I think you mean /usr/include/python2.7 for the sip.h from stock > >>> Slackware sip-4.18-x86_64-1 package? > >>> > >>> If you have a /usr/include/python3.7/sip.h (the one which should be in > >>> /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. > >>> > >>> I emailed the maintainer a few days ago with a version-independent > >>> method to install in the correct location but haven't heard back about > >>> it yet (so cc'd here now as a reminder). I just thought I should also > >>> check here in case there was something whacky about my own setup but > >>> based on the feedback, as well as noticing that AlienBob's python3 > >>> package uses /usr/include/python3.7m, I"m sure now that the problem is > >>> with the python3-sip SlackBuild. It looks very close to the SlackBuild > >>> in -current but of course -current uses python 3.8 where the issue has > >>> been fixed, rather than python 3.7 as on SBo. > >>> > >>> chris > >> > >> I maintain python3-sip now, so if we are all in agreement that we use > >> python3.7 I'll fix that this week. > > > > I got that the wrong way around. > > > > We're want to use /usr/include/python3.7m right? > > > > Yes Dave, that's correct. > > Although you could hard code it to python3.7m, I"d suggest a > version-independent mechanism like changing the existing line: > -e "/usr/include/python$PYTHONVER" \ > to: > -e $(pkg-config --cflags-only-I python3 | sed -e 's/^-I//' ) \ > > This uses pkg-config to find the "official" include path and strips the > leading '-I'. Then sip.h would be installed in the correct location > regardless of the python version. > > chris > I'll test that now. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Fri Apr 24 13:02:21 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 24 Apr 2020 14:02:21 +0100 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> Message-ID: <20200424130221.GG7151@blackswan.r0t.uk> On 2020-04-24 22:18, Christoph Willing put forth the proposition: > On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: > > i've a reasonable collection of python .sbo packages installed, and > > sip.h is the only file in /usr/include/python3.7 > > which is from stock slackware 14.2 sip-4.18 package > > Regards, Tim > > > > Thanks all for the replies confirming the python3 include directories. > > Tim, I think you mean /usr/include/python2.7 for the sip.h from stock > Slackware sip-4.18-x86_64-1 package? > > If you have a /usr/include/python3.7/sip.h (the one which should be in > /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. > > I emailed the maintainer a few days ago with a version-independent > method to install in the correct location but haven't heard back about > it yet (so cc'd here now as a reminder). I just thought I should also I've just noticed that Marcel is still listed as maintainer. I also failed to get a reply during the Qt5 updates. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From slackbuilds at jaxartes.net Fri Apr 24 13:05:03 2020 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Fri, 24 Apr 2020 06:05:03 -0700 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <20200424130221.GG7151@blackswan.r0t.uk> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424130221.GG7151@blackswan.r0t.uk> Message-ID: <3809195.jkkN71MqXu@wintermute.sprawl.net> On Friday, 24 April 2020 06:02:21 PDT Dave Woodfall wrote: > On 2020-04-24 22:18, > > Christoph Willing put forth the proposition: > > On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: > > > i've a reasonable collection of python .sbo packages installed, and > > > sip.h is the only file in /usr/include/python3.7 > > > which is from stock slackware 14.2 sip-4.18 package > > > Regards, Tim > > > > Thanks all for the replies confirming the python3 include directories. > > > > Tim, I think you mean /usr/include/python2.7 for the sip.h from stock > > Slackware sip-4.18-x86_64-1 package? > > > > If you have a /usr/include/python3.7/sip.h (the one which should be in > > /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. > > > > I emailed the maintainer a few days ago with a version-independent > > method to install in the correct location but haven't heard back about > > it yet (so cc'd here now as a reminder). I just thought I should also > > I've just noticed that Marcel is still listed as maintainer. I also > failed to get a reply during the Qt5 updates. I contacted Marcel about this same sip.h location issue last year and did not hear back from him then either. Ben From majek at w7i.pl Fri Apr 24 15:28:50 2020 From: majek at w7i.pl (Marek Wodzinski) Date: Fri, 24 Apr 2020 17:28:50 +0200 (CEST) Subject: [Slackbuilds-users] ATT: anyone using python3-PyQt5 In-Reply-To: <20200423051149.GE2780@blackswan.r0t.uk> References: <20200423051149.GE2780@blackswan.r0t.uk> Message-ID: On Thu, 23 Apr 2020, Dave Woodfall wrote: > This is a heads-up for anyone using python3-PyQt5. The version we > have now has had support for QtWebEngine python bindings split into > a separate package - python3-PyQtWebEngine. > So far, `anki' is the only one that I know that needs it and I've > adjusted it in my branch. It looks like 'anki' also requires python3-soupsieve which is new and optional dependency of BeautifulSoup4. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg From srigungadinji2 at gmail.com Sat Apr 25 10:39:16 2020 From: srigungadinji2 at gmail.com (Gunga Din II) Date: Sat, 25 Apr 2020 11:39:16 +0100 Subject: [Slackbuilds-users] Error building codelite-14.0 Message-ID: <010adcb6-45de-f388-ab78-e51e20a0baca@gmail.com> Hi, I recently built codelite-13.0, and that went OK, but the recent upgrade to codelite-14.0 failed on my Slackware-14.2 machine. Here's the problem... =========================================== CodeLite/CMakeFiles/libcodelite.dir/cl_ssh.cpp.o /tmp/SBo/codelite-14.0/CodeLite/cl_ssh.cpp: In member function 'bool clSSH::AuthenticateServer(wxString&)': /tmp/SBo/codelite-14.0/CodeLite/cl_ssh.cpp:118:45: error: 'ssh_get_server_publickey' was not declared in this scope ???? ssh_get_server_publickey(m_session, &key); ^ ??? CodeLite/CMakeFiles/libcodelite.dir/build.make:758: recipe for target 'CodeLite/CMakeFiles/libcodelite.dir/cl_ssh.cpp.o' failed =========================================== I found mention on Github of the same issue on another distro (Linux Mint), and apparently it's a problem with the version checking of libssh The original post is here => https://github.com/eranif/codelite/issues/2443 There's mention of a quick fix in the bug report... ====CUT=== You will probably be able to 'fix' the build by changing CodeLite/cl_ssh.cpp #if LIBSSH_VERSION_INT < SSH_VERSION_INT(0, 6, 1) to e.g. (0, 6, 5). ====CUT=== So it looks like a know problem upstream...? Any chance of a patch until this is resolved upstream? Thanks. From 1.41421 at gmail.com Sat Apr 25 14:51:52 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 25 Apr 2020 08:51:52 -0600 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit Message-ID: I have seen this in two of my Slackware 14.2 systems, whereas in two others the latest qt5-webkit builds fine. What is particularly puzzling is the complaint about undefined phtreads-related symbols, when all of my 14.2 system have the pthread library installed. Anybody come across this? -- Found GStreamer: GSTREAMER_INCLUDE_DIRS;GSTREAMER_LIBRARIES;GSTREAMER_VERSION;GSTREAMER_BASE_INCLUDE_DIRS;GSTREAMER_BASE_LIBRARIES;GSTREAMER_APP_INCLUDE_DIRS;GSTREAMER_APP_LIBRARIES;GSTREAMER_PBUTILS_INCLUDE_DIRS;GSTREAMER_PBUTILS_LIBRARIES;GSTREAMER_VIDEO_INCLUDE_DIRS;GSTREAMER_VIDEO_LIBRARIES;GSTREAMER_MPEGTS_INCLUDE_DIRS;GSTREAMER_MPEGTS_LIBRARIES;GSTREAMER_TAG_INCLUDE_DIRS;GSTREAMER_TAG_LIBRARIES;GSTREAMER_GL_INCLUDE_DIRS;GSTREAMER_GL_LIBRARIES;GSTREAMER_AUDIO_INCLUDE_DIRS;GSTREAMER_AUDIO_LIBRARIES;GSTREAMER_FFT_INCLUDE_DIRS;GSTREAMER_FFT_LIBRARIES (Required is at least version "1.0.3") CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find Hyphen (missing: HYPHEN_INCLUDE_DIR HYPHEN_LIBRARIES) Call Stack (most recent call first): /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE) Source/cmake/FindHyphen.cmake:37 (find_package_handle_standard_args) Source/cmake/OptionsQt.cmake:842 (find_package) Source/cmake/WebKitCommon.cmake:51 (include) CMakeLists.txt:137 (include) -- Configuring incomplete, errors occurred! See also "/tmp/SBo/qtwebkit-5.212.0-alpha4/build/CMakeFiles/CMakeOutput.log". See also "/tmp/SBo/qtwebkit-5.212.0-alpha4/build/CMakeFiles/CMakeError.log". In CMakeError.log I have the following: Run Build Command:"/usr/bin/gmake" "cmTC_4f2cb/fast" /usr/bin/gmake -f CMakeFiles/cmTC_4f2cb.dir/build.make CMakeFiles/cmTC_4f2cb.dir /build gmake[1]: Entering directory '/tmp/SBo/qtwebkit-5.212.0-alpha4/build/CMakeFiles/ CMakeTmp' Building C object CMakeFiles/cmTC_4f2cb.dir/CheckSymbolExists.c.o /usr/bin/cc -O2 -fPIC -fno-exceptions -fno-strict-aliasing -o CMakeFiles/ cmTC_4f2cb.dir/CheckSymbolExists.c.o -c /tmp/SBo/qtwebkit-5.212.0-alpha4/build /CMakeFiles/CMakeTmp/CheckSymbolExists.c Linking C executable cmTC_4f2cb /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_4f2cb.dir/link.txt --verbose =1 /usr/bin/cc -O2 -fPIC -fno-exceptions -fno-strict-aliasing CMakeFiles/cmTC _4f2cb.dir/CheckSymbolExists.c.o -o cmTC_4f2cb -rdynamic CMakeFiles/cmTC_4f2cb.dir/CheckSymbolExists.c.o: In function `main': CheckSymbolExists.c:(.text.startup+0x3): undefined reference to `pthread_create' collect2: error: ld returned 1 exit status CMakeFiles/cmTC_4f2cb.dir/build.make:97: recipe for target 'cmTC_4f2cb' failed gmake[1]: *** [cmTC_4f2cb] Error 1 gmake[1]: Leaving directory '/tmp/SBo/qtwebkit-5.212.0-alpha4/build/CMakeFiles/C MakeTmp' Makefile:126: recipe for target 'cmTC_4f2cb/fast' failed gmake: *** [cmTC_4f2cb/fast] Error 2 File /tmp/SBo/qtwebkit-5.212.0-alpha4/build/CMakeFiles/CMakeTmp/CheckSymbolExist s.c: /* */ #include int main(int argc, char** argv) { (void)argv; #ifndef pthread_create return ((int*)(&pthread_create))[argc]; #else (void)argc; return 0; #endif } Determining if the function pthread_create exists in the pthreads failed with th e following output: Change Dir: /tmp/SBo/qtwebkit-5.212.0-alpha4/build/CMakeFiles/CMakeTmp -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sat Apr 25 14:58:05 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 25 Apr 2020 16:58:05 +0200 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit In-Reply-To: References: Message-ID: Il giorno sab 25 apr 2020 alle ore 16:52 Luveh Keraph <1.41421 at gmail.com> ha scritto: > Could NOT find Hyphen (missing: HYPHEN_INCLUDE_DIR HYPHEN_LIBRARIES) it seems you are missing at least one of the dependencies. From 1.41421 at gmail.com Sat Apr 25 15:30:32 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 25 Apr 2020 09:30:32 -0600 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit In-Reply-To: References: Message-ID: Right, it seems to be the hyphen package. After installing that, the error reported disappears and the build is ongoing. The report about pthread obviously was a red herring. On Sat, Apr 25, 2020 at 8:57 AM Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > Il giorno sab 25 apr 2020 alle ore 16:52 Luveh Keraph > <1.41421 at gmail.com> ha scritto: > > Could NOT find Hyphen (missing: HYPHEN_INCLUDE_DIR HYPHEN_LIBRARIES) > > it seems you are missing at least one of the dependencies. > _______________________________________________ > 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 dickson.tim at googlemail.com Sat Apr 25 16:36:32 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sat, 25 Apr 2020 17:36:32 +0100 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit In-Reply-To: References: Message-ID: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> i spotted an optional dep of qt5-webkit which is dwz this appears to de-duplicate debug symbols etc in elf files. however, as we tend to remove all extra debug stuff with strip, It doesn't appear to change the package size much. is anyone interested in a dwz as a package?. I did create one to see if it made much difference to the qt5-webkit package, and though the size was within 9bytes!, it did appear to create the package a bit quicker, so may be worth using. comments? regards, Tim On 25/04/2020 15:58, Matteo Bernardini wrote: > Il giorno sab 25 apr 2020 alle ore 16:52 Luveh Keraph > <1.41421 at gmail.com> ha scritto: >> Could NOT find Hyphen (missing: HYPHEN_INCLUDE_DIR HYPHEN_LIBRARIES) > it seems you are missing at least one of the dependencies. > _______________________________________________ > 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/ > --- This email has been checked for viruses by AVG. https://www.avg.com From dave at slackbuilds.org Sat Apr 25 17:13:38 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 25 Apr 2020 18:13:38 +0100 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit In-Reply-To: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> Message-ID: <20200425171338.GH7151@blackswan.r0t.uk> On 2020-04-25 17:36, Slackbuilds Users put forth the proposition: > i spotted an optional dep of qt5-webkit which is dwz > this appears to de-duplicate debug symbols etc in elf files. however, as we > tend to remove all > extra debug stuff with strip, It doesn't appear to change the package size > much. > is anyone interested in a dwz as a package?. I did create one to see if it > made much difference > to the qt5-webkit package, and though the size was within 9bytes!, it did > appear to create the package > a bit quicker, so may be worth using. > comments? > regards, Tim If you want to submit it, I'll add it to the readme as optional. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sat Apr 25 18:37:15 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 25 Apr 2020 19:37:15 +0100 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <7173702c-8e0d-468d-e5f1-d215b783ecaf@linux.com> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> <20200424122452.GD7151@blackswan.r0t.uk> <20200424123015.GE7151@blackswan.r0t.uk> <7173702c-8e0d-468d-e5f1-d215b783ecaf@linux.com> Message-ID: <20200425183715.GI7151@blackswan.r0t.uk> On 2020-04-24 22:42, Christoph Willing put forth the proposition: > On 24/4/20 10:30 pm, Dave Woodfall wrote: > > On 2020-04-24 13:24, > > Dave Woodfall put forth the proposition: > >> On 2020-04-24 22:18, > >> Christoph Willing put forth the proposition: > >>> On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: > >>>> i've a reasonable collection of python .sbo packages installed, and > >>>> sip.h is the only file in /usr/include/python3.7 > >>>> which is from stock slackware 14.2 sip-4.18 package > >>>> Regards, Tim > >>>> > >>> > >>> Thanks all for the replies confirming the python3 include directories. > >>> > >>> Tim, I think you mean /usr/include/python2.7 for the sip.h from stock > >>> Slackware sip-4.18-x86_64-1 package? > >>> > >>> If you have a /usr/include/python3.7/sip.h (the one which should be in > >>> /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. > >>> > >>> I emailed the maintainer a few days ago with a version-independent > >>> method to install in the correct location but haven't heard back about > >>> it yet (so cc'd here now as a reminder). I just thought I should also > >>> check here in case there was something whacky about my own setup but > >>> based on the feedback, as well as noticing that AlienBob's python3 > >>> package uses /usr/include/python3.7m, I"m sure now that the problem is > >>> with the python3-sip SlackBuild. It looks very close to the SlackBuild > >>> in -current but of course -current uses python 3.8 where the issue has > >>> been fixed, rather than python 3.7 as on SBo. > >>> > >>> chris > >> > >> I maintain python3-sip now, so if we are all in agreement that we use > >> python3.7 I'll fix that this week. > > > > I got that the wrong way around. > > > > We're want to use /usr/include/python3.7m right? > > > > Yes Dave, that's correct. > > Although you could hard code it to python3.7m, I"d suggest a > version-independent mechanism like changing the existing line: > -e "/usr/include/python$PYTHONVER" \ > to: > -e $(pkg-config --cflags-only-I python3 | sed -e 's/^-I//' ) \ > > This uses pkg-config to find the "official" include path and strips the > leading '-I'. Then sip.h would be installed in the correct location > regardless of the python version. > > chris I've changed both python3-sip and python3-PyQt5 to use that instead of hardcoding the paths in. The only two applications that directly depend on python3-sip are python3-PyQt5 and wxPython4, which seems to build fine. Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From chris.willing at linux.com Sat Apr 25 22:38:28 2020 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 26 Apr 2020 08:38:28 +1000 Subject: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ? In-Reply-To: <20200425183715.GI7151@blackswan.r0t.uk> References: <74588ed6-9214-79c1-3b2b-9fb252a5779d@linux.com> <20200424085110.GA551@lenovo.myrequiem.net> <20200424122452.GD7151@blackswan.r0t.uk> <20200424123015.GE7151@blackswan.r0t.uk> <7173702c-8e0d-468d-e5f1-d215b783ecaf@linux.com> <20200425183715.GI7151@blackswan.r0t.uk> Message-ID: On 26/4/20 4:37 am, Dave Woodfall wrote: > On 2020-04-24 22:42, > Christoph Willing put forth the proposition: >> On 24/4/20 10:30 pm, Dave Woodfall wrote: >>> On 2020-04-24 13:24, >>> Dave Woodfall put forth the proposition: >>>> On 2020-04-24 22:18, >>>> Christoph Willing put forth the proposition: >>>>> On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote: >>>>>> i've a reasonable collection of python .sbo packages installed, and >>>>>> sip.h is the only file in /usr/include/python3.7 >>>>>> which is from stock slackware 14.2 sip-4.18 package >>>>>> Regards, Tim >>>>>> >>>>> >>>>> Thanks all for the replies confirming the python3 include directories. >>>>> >>>>> Tim, I think you mean /usr/include/python2.7 for the sip.h from stock >>>>> Slackware sip-4.18-x86_64-1 package? >>>>> >>>>> If you have a /usr/include/python3.7/sip.h (the one which should be in >>>>> /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild. >>>>> >>>>> I emailed the maintainer a few days ago with a version-independent >>>>> method to install in the correct location but haven't heard back about >>>>> it yet (so cc'd here now as a reminder). I just thought I should also >>>>> check here in case there was something whacky about my own setup but >>>>> based on the feedback, as well as noticing that AlienBob's python3 >>>>> package uses /usr/include/python3.7m, I"m sure now that the problem is >>>>> with the python3-sip SlackBuild. It looks very close to the SlackBuild >>>>> in -current but of course -current uses python 3.8 where the issue has >>>>> been fixed, rather than python 3.7 as on SBo. >>>>> >>>>> chris >>>> >>>> I maintain python3-sip now, so if we are all in agreement that we use >>>> python3.7 I'll fix that this week. >>> >>> I got that the wrong way around. >>> >>> We're want to use /usr/include/python3.7m right? >>> >> >> Yes Dave, that's correct. >> >> Although you could hard code it to python3.7m, I"d suggest a >> version-independent mechanism like changing the existing line: >> -e "/usr/include/python$PYTHONVER" \ >> to: >> -e $(pkg-config --cflags-only-I python3 | sed -e 's/^-I//' ) \ >> >> This uses pkg-config to find the "official" include path and strips the >> leading '-I'. Then sip.h would be installed in the correct location >> regardless of the python version. >> >> chris > > I've changed both python3-sip and python3-PyQt5 to use that instead > of hardcoding the paths in. The only two applications that directly > depend on python3-sip are python3-PyQt5 and wxPython4, which seems to > build fine. > > Looks good - will help pkgs which indirectly depend on it too (in my case QScintilla-qt5 but maybe/probably others). Thanks, chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From dickson.tim at googlemail.com Sat Apr 25 23:13:35 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 26 Apr 2020 00:13:35 +0100 Subject: [Slackbuilds-users] qt5-webkit issues In-Reply-To: <20200425171338.GH7151@blackswan.r0t.uk> References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> <20200425171338.GH7151@blackswan.r0t.uk> Message-ID: <2ccc45bc-2f62-463e-cff4-5fd3046e4959@googlemail.com> i've noticed a change in qt5-webkit; any applications that use it will fail if run as root, unless you set QTWEBENGINE_DISABLE_SANDBOX=1 before running the executable that uses it. It may be worth a comment, or something as binaries that used to run as root will not any more without this environment variable set. it effects musescore 3.4.2, and possibly gambas and others that use it (approx 23 packages). regards, Tim On 25/04/2020 18:13, Dave Woodfall wrote: > On 2020-04-25 17:36, > Slackbuilds Users put forth the proposition: >> i spotted an optional dep of qt5-webkit which is dwz >> this appears to de-duplicate debug symbols etc in elf files. however, as we >> tend to remove all >> extra debug stuff with strip, It doesn't appear to change the package size >> much. >> is anyone interested in a dwz as a package?. I did create one to see if it >> made much difference >> to the qt5-webkit package, and though the size was within 9bytes!, it did >> appear to create the package >> a bit quicker, so may be worth using. >> comments? >> regards, Tim > > If you want to submit it, I'll add it to the readme as optional. > > _______________________________________________ > 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/ > --- This email has been checked for viruses by AVG. https://www.avg.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sun Apr 26 02:12:53 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 26 Apr 2020 03:12:53 +0100 Subject: [Slackbuilds-users] qt5-webkit issues In-Reply-To: <2ccc45bc-2f62-463e-cff4-5fd3046e4959@googlemail.com> References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> <20200425171338.GH7151@blackswan.r0t.uk> <2ccc45bc-2f62-463e-cff4-5fd3046e4959@googlemail.com> Message-ID: <20200426021253.GA7788@blackswan.r0t.uk> On 2020-04-26 00:13, Slackbuilds Users put forth the proposition: > i've noticed a change in qt5-webkit; any applications that use it will fail > if run as root, > unless you set QTWEBENGINE_DISABLE_SANDBOX=1 before running the executable > that uses it. It may be worth a comment, or something as binaries that used > to run as root > will not any more without this environment variable set. it effects > musescore 3.4.2, and possibly > gambas and others that use it (approx 23 packages). > regards, Tim I'll make a note of it in README, but it's not a good idea to run GUI applications as root, especially anything web-browserish, and most people would have no need. Sandboxing it is for safety. > On 25/04/2020 18:13, Dave Woodfall wrote: > > On 2020-04-25 17:36, > > Slackbuilds Users put forth the proposition: > > > i spotted an optional dep of qt5-webkit which is dwz > > > this appears to de-duplicate debug symbols etc in elf files. however, as we > > > tend to remove all > > > extra debug stuff with strip, It doesn't appear to change the package size > > > much. > > > is anyone interested in a dwz as a package?. I did create one to see if it > > > made much difference > > > to the qt5-webkit package, and though the size was within 9bytes!, it did > > > appear to create the package > > > a bit quicker, so may be worth using. > > > comments? > > > regards, Tim > > > > If you want to submit it, I'll add it to the readme as optional. > > > > _______________________________________________ > > 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/ > > > > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sun Apr 26 08:08:27 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 26 Apr 2020 09:08:27 +0100 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit In-Reply-To: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> Message-ID: <20200426080827.GC1476@blackswan.r0t.uk> On 2020-04-25 17:36, Slackbuilds Users put forth the proposition: > i spotted an optional dep of qt5-webkit which is dwz > this appears to de-duplicate debug symbols etc in elf files. however, as we > tend to remove all > extra debug stuff with strip, It doesn't appear to change the package size > much. > is anyone interested in a dwz as a package?. I did create one to see if it > made much difference > to the qt5-webkit package, and though the size was within 9bytes!, it did > appear to create the package > a bit quicker, so may be worth using. > comments? > regards, Tim According to the man page[1], it isn't for qt5-webkit, but for any ELF binary. [1] https://www.mankier.com/1/dwz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dickson.tim at googlemail.com Sun Apr 26 08:46:09 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 26 Apr 2020 09:46:09 +0100 Subject: [Slackbuilds-users] qt5-webkit issues In-Reply-To: <20200426021253.GA7788@blackswan.r0t.uk> References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> <20200425171338.GH7151@blackswan.r0t.uk> <2ccc45bc-2f62-463e-cff4-5fd3046e4959@googlemail.com> <20200426021253.GA7788@blackswan.r0t.uk> Message-ID: On 26/04/2020 03:12, Dave Woodfall wrote: > On 2020-04-26 00:13, > Slackbuilds Users put forth the proposition: >> i've noticed a change in qt5-webkit; any applications that use it will fail >> if run as root, >> unless you set QTWEBENGINE_DISABLE_SANDBOX=1 before running the executable >> that uses it. It may be worth a comment, or something as binaries that used >> to run as root >> will not any more without this environment variable set. it effects >> musescore 3.4.2, and possibly >> gambas and others that use it (approx 23 packages). >> regards, Tim > I'll make a note of it in README, but it's not a good idea to run GUI > applications as root, especially anything web-browserish, and most > people would have no need. Sandboxing it is for safety. thanks. yes I'm aware of the risks of running browsers as root, the "software police" doesn't like anyone running as root. but for package builders you often should be building packages as root, with full root path env ie. su - (at least a number of packages will fail otherwise) and a quick test (while still as root) that the package built and runs ok would fail in those cases. This is how I spotted the problem anyway. :-) musescore just crashes (fails to come up) unless you call it with -w? to disable the web related component, or set that environment variable I mentioned. talking of which, incase klaatu is checking this mail group, if he is interested, musescore 3.4.2 has been out for a few months now, and just requires the usual version bump and updated download links and md5 sums in the slackbuild to get it to work. >> On 25/04/2020 18:13, Dave Woodfall wrote: >>> On 2020-04-25 17:36, >>> Slackbuilds Users put forth the proposition: >>>> i spotted an optional dep of qt5-webkit which is dwz >>>> this appears to de-duplicate debug symbols etc in elf files. however, as we >>>> tend to remove all >>>> extra debug stuff with strip, It doesn't appear to change the package size >>>> much. >>>> is anyone interested in a dwz as a package?. I did create one to see if it >>>> made much difference >>>> to the qt5-webkit package, and though the size was within 9bytes!, it did >>>> appear to create the package >>>> a bit quicker, so may be worth using. >>>> comments? >>>> regards, Tim >>> If you want to submit it, I'll add it to the readme as optional. >>> >>> _______________________________________________ >>> 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/ >>> >> >> >> --- >> This email has been checked for viruses by AVG. >> https://www.avg.com >> _______________________________________________ >> 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Sun Apr 26 09:02:48 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 26 Apr 2020 10:02:48 +0100 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit In-Reply-To: <20200426080827.GC1476@blackswan.r0t.uk> References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> <20200426080827.GC1476@blackswan.r0t.uk> Message-ID: <7a15934c-c442-0138-27e6-ed20c3f91145@googlemail.com> On 26/04/2020 09:08, Dave Woodfall wrote: > On 2020-04-25 17:36, > Slackbuilds Users put forth the proposition: >> i spotted an optional dep of qt5-webkit which is dwz >> this appears to de-duplicate debug symbols etc in elf files. however, as we >> tend to remove all >> extra debug stuff with strip, It doesn't appear to change the package size >> much. >> is anyone interested in a dwz as a package?. I did create one to see if it >> made much difference >> to the qt5-webkit package, and though the size was within 9bytes!, it did >> appear to create the package >> a bit quicker, so may be worth using. >> comments? >> regards, Tim > According to the man page[1], it isn't for qt5-webkit, but for any > ELF binary. > > [1] https://www.mankier.com/1/dwz > that's right. I haven't seen what else may have code to use it if it is there (I'm not sure how to do that anyway without downloading all the sbo package sources and greping for it in makefiles). I submitted the dwz package yesterday. Generally because the practice is often to strip the? binaries, we wouldn't see much benefit, unless there are lots of intermediate stages which are sped up with smaller ELF binaries during the build process. I only spotted the existence of dwz? when going through the (qt5-webkit) build log, I saw the mention of it, and checked it out, and saw it is available for lots of other distros, so why not for slackware? if it improves executable size or build speeds I'm in favour, but I don't know what else uses it. it appears to be used by debian, ubuntu, redhat, fedora etc. so the odds are we may see it appearing more? in some packages. I'm not sure which category it should go in, development or system, but it can be moved if I picked the wrong one. > _______________________________________________ > 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/ > --- This email has been checked for viruses by AVG. https://www.avg.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sun Apr 26 09:17:58 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 26 Apr 2020 10:17:58 +0100 Subject: [Slackbuilds-users] qt5-webkit issues In-Reply-To: References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> <20200425171338.GH7151@blackswan.r0t.uk> <2ccc45bc-2f62-463e-cff4-5fd3046e4959@googlemail.com> <20200426021253.GA7788@blackswan.r0t.uk> Message-ID: <20200426091758.GE1476@blackswan.r0t.uk> On 2020-04-26 09:46, Slackbuilds Users put forth the proposition: > yes I'm aware of the risks of running browsers as root, the "software > police" doesn't like anyone running as root. but for package builders you > often should be building packages as root, with full root path env ie. su - > (at least a number of packages will fail otherwise) We aren't talking about building packages though. You don't need qt5-webkit to build a package. These "software police" are the people who made *nix systems as secure as they can be by making a root account for maintenance and user accounts for normal, everyday use. Otherwise we end up with a situation like in Windows, where new users are running everything under the admin account because they know no better, and where any nasty little thing they encounter will run with full access and privileges to screw up their installation, and frequently does. > and a quick test (while still as root) that the package built and runs ok > would fail in those cases. SlackBuild scripts are mean to be run as root, or some of the commands in them will fail. E.G. you can't `chown -R root:root' unless you are have root privileges, and if you don't do that, you end up with files all over the filesystem with wrong ownerships. > This is how I spotted the problem anyway. :-) > musescore just crashes (fails to come up) unless you call it with -w? to > disable the web related component, or set that environment variable I > mentioned. If you need to run musescore as root then something is wrong somewhere. Which groups are you in? What exactly does musescore need to access that isn't accessible while running as your normal user? We may be able to help with a little more info on the problem. > talking of which, incase klaatu is checking this mail group, if he is > interested, musescore 3.4.2 has been out for a few months now, and just > requires the usual version bump and updated download links and md5 sums in I emailed him a few weeks ago, while doing my first Qt5 testing, and got no reply, so if you want to submit an update feel free. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sun Apr 26 09:26:36 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 26 Apr 2020 10:26:36 +0100 Subject: [Slackbuilds-users] Puzzling error building qt5-webkit In-Reply-To: <7a15934c-c442-0138-27e6-ed20c3f91145@googlemail.com> References: <0071ab6f-ea75-3e9b-6319-432b3e774cbb@googlemail.com> <20200426080827.GC1476@blackswan.r0t.uk> <7a15934c-c442-0138-27e6-ed20c3f91145@googlemail.com> Message-ID: <20200426092636.GF1476@blackswan.r0t.uk> On 2020-04-26 10:02, Slackbuilds Users put forth the proposition: > > On 26/04/2020 09:08, Dave Woodfall wrote: > > On 2020-04-25 17:36, > > Slackbuilds Users put forth the proposition: > > > i spotted an optional dep of qt5-webkit which is dwz > > > this appears to de-duplicate debug symbols etc in elf files. however, as we > > > tend to remove all > > > extra debug stuff with strip, It doesn't appear to change the package size > > > much. > > > is anyone interested in a dwz as a package?. I did create one to see if it > > > made much difference > > > to the qt5-webkit package, and though the size was within 9bytes!, it did > > > appear to create the package > > > a bit quicker, so may be worth using. > > > comments? > > > regards, Tim > > According to the man page[1], it isn't for qt5-webkit, but for any > > ELF binary. > > > > [1] https://www.mankier.com/1/dwz > > > that's right. I haven't seen what else may have code to use it if it is > there (I'm not sure how to do that anyway without downloading all the sbo > package sources and greping for it in makefiles). I submitted the dwz > package yesterday. Generally because the practice is often to strip the? > binaries, we wouldn't see much benefit, unless there are lots of > intermediate stages which are sped up with smaller ELF binaries during the > build process. > I only spotted the existence of dwz? when going through the (qt5-webkit) > build log, I saw the mention of it, and checked it out, and saw it is > available for lots of other distros, so why not for slackware? if it > improves executable size or build speeds I'm in favour, but I don't know > what else uses it. it appears to be used by debian, ubuntu, redhat, fedora > etc. so the odds are we may see it appearing more? in some packages. I'm not > sure which category it should go in, development or system, but it can be > moved if I picked the wrong one. It's only to remove duplicated symbols. We normally strip them, so it would only be useful if, for example, you want to debug something that crashed or segfaulted. In that case you would rebuild the application without stripping the binaries by commenting out the strip lines in the SlackBuild, or by building and running it from the source directory without installing it, if it supports running like that. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From artourter at gmail.com Sun Apr 26 17:46:31 2020 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sun, 26 Apr 2020 18:46:31 +0100 Subject: [Slackbuilds-users] netcdf package update Message-ID: Hi, I was wondering if David Spencer was was still active here. I have send him a couple of emails earlier this months about updating his netcdf slackbuild but I haven't received any replies from either of his email addresses. I noticed that at least one of his script has been updated by someone else but without changing the maintainership. I am happy to update it myself or take over but not sure what is going on. Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From christopher.duston at protonmail.com Tue Apr 28 20:38:47 2020 From: christopher.duston at protonmail.com (Christopher L Duston) Date: Tue, 28 Apr 2020 20:38:47 +0000 Subject: [Slackbuilds-users] build errors with libquicktime Message-ID: I am having some trouble building libquicktime, errors are below. I naively believe this might be because I'm running multilib, but that section of the script already includes what I would have added to try and fix that: if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" else SLKCFLAGS="-O2" LIBDIRSUFFIX="" fi Any thoughts? Build Errors: libtool: link: gcc -shared .libs/vorbis.o .libs/lqt_vorbis.o -Wl,-rpath -Wl,/tmp/SBo/libquicktime-1.2.4/src/.libs ../../src/.libs/libquicktime.so /usr/lib/libvorbisenc.so -L/usr/lib /usr/lib/libvorbis.so /usr/lib/libvorbisfile.so -lpthread -lm -lz -ldl -Wl,-soname -Wl,lqt_vorbis.so -o .libs/lqt_vorbis.so /usr/lib/libvorbisenc.so: error adding symbols: File in wrong format collect2: error: ld returned 1 exit status Makefile:374: recipe for target 'lqt_vorbis.la' failed make[3]: *** [lqt_vorbis.la] Error 1 make[3]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins/vorbis' Makefile:371: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins' Makefile:444: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/libquicktime-1.2.4' Makefile:351: recipe for target 'all' failed make: *** [all] Error 2 Sent with [ProtonMail](https://protonmail.com) Secure Email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Tue Apr 28 21:18:36 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 28 Apr 2020 14:18:36 -0700 Subject: [Slackbuilds-users] build errors with libquicktime In-Reply-To: References: Message-ID: On 4/28/20 1:38 PM, Christopher L Duston via SlackBuilds-users wrote: > I am having some trouble building libquicktime, errors are below. I > naively believe this might be because I'm running multilib, but that > section of the script already includes what I would have added to try > and fix that: > > if [ "$ARCH" = "i486" ]; then > ? SLKCFLAGS="-O2 -march=i486 -mtune=i686" > ? LIBDIRSUFFIX="" > elif [ "$ARCH" = "i686" ]; then > ? SLKCFLAGS="-O2 -march=i686 -mtune=i686" > ? LIBDIRSUFFIX="" > elif [ "$ARCH" = "x86_64" ]; then > ? SLKCFLAGS="-O2 -fPIC" > ? LIBDIRSUFFIX="64" > else > ? SLKCFLAGS="-O2" > ? LIBDIRSUFFIX="" > fi > > Any thoughts? > > Build Errors: > > libtool: link: gcc -shared? .libs/vorbis.o .libs/lqt_vorbis.o?? > -Wl,-rpath -Wl,/tmp/SBo/libquicktime-1.2.4/src/.libs > ../../src/.libs/libquicktime.so /usr/lib/libvorbisenc.so -L/usr/lib > /usr/lib/libvorbis.so /usr/lib/libvorbisfile.so -lpthread -lm -lz > -ldl??? -Wl,-soname -Wl,lqt_vorbis.so -o .libs/lqt_vorbis.so > /usr/lib/libvorbisenc.so: error adding symbols: File in wrong format > collect2: error: ld returned 1 exit status > Makefile:374: recipe for target 'lqt_vorbis.la' failed > make[3]: *** [lqt_vorbis.la] Error 1 > make[3]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins/vorbis' > Makefile:371: recipe for target 'all-recursive' failed > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins' > Makefile:444: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/libquicktime-1.2.4' > Makefile:351: recipe for target 'all' failed > make: *** [all] Error 2 > > On multilib, you may need this modification in the buildscript: ... CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ LDFLAGS="-L/usr/lib$LIBDIRSUFFIX" \ ./configure \ --prefix=/usr \ ... libquicktime's configure gets confused when there is both /usr/lib and /usr/lib64 -Ed -------------- 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 Apr 28 21:22:11 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 28 Apr 2020 14:22:11 -0700 Subject: [Slackbuilds-users] build errors with libquicktime In-Reply-To: References: Message-ID: On 4/28/20 1:38 PM, Christopher L Duston via SlackBuilds-users wrote: > I am having some trouble building libquicktime, errors are below. I > naively believe this might be because I'm running multilib, but that > section of the script already includes what I would have added to try > and fix that: > Forgot to add the LQ reference to my earlier reply: https://www.linuxquestions.org/questions/slackware-14/slackware-14-2-libquicktime-1-2-4-from-slackbuilds-fails-to-install-4175593159/ -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From christopher.duston at protonmail.com Tue Apr 28 21:26:12 2020 From: christopher.duston at protonmail.com (Christopher L Duston) Date: Tue, 28 Apr 2020 21:26:12 +0000 Subject: [Slackbuilds-users] build errors with libquicktime In-Reply-To: References: Message-ID: <1__cq0OZiS0a3-kip8qwA5U4X-USE_ff1skL2iH2-gc_FCFN74m5XIvgj05Yb5KbF7NwRwY6fVG5oaD0Cmbxe5EK6OpVFe163ep48pi2_kI=@protonmail.com> Of course, sorry I knew that. I just didn't know it right when I needed to know it. Builds now with those changes, thanks. Sent with ProtonMail Secure Email. ??????? Original Message ??????? On Tuesday, April 28, 2020 5:18 PM, King Beowulf wrote: > On 4/28/20 1:38 PM, Christopher L Duston via SlackBuilds-users wrote: > > > I am having some trouble building libquicktime, errors are below. I > > naively believe this might be because I'm running multilib, but that > > section of the script already includes what I would have added to try > > and fix that: > > if [ "$ARCH" = "i486" ]; then > > ? SLKCFLAGS="-O2 -march=i486 -mtune=i686" > > ? LIBDIRSUFFIX="" > > elif [ "$ARCH" = "i686" ]; then > > ? SLKCFLAGS="-O2 -march=i686 -mtune=i686" > > ? LIBDIRSUFFIX="" > > elif [ "$ARCH" = "x86_64" ]; then > > ? SLKCFLAGS="-O2 -fPIC" > > ? LIBDIRSUFFIX="64" > > else > > ? SLKCFLAGS="-O2" > > ? LIBDIRSUFFIX="" > > fi > > Any thoughts? > > Build Errors: > > libtool: link: gcc -shared? .libs/vorbis.o .libs/lqt_vorbis.o?? > > -Wl,-rpath -Wl,/tmp/SBo/libquicktime-1.2.4/src/.libs > > ../../src/.libs/libquicktime.so /usr/lib/libvorbisenc.so -L/usr/lib > > /usr/lib/libvorbis.so /usr/lib/libvorbisfile.so -lpthread -lm -lz > > -ldl??? -Wl,-soname -Wl,lqt_vorbis.so -o .libs/lqt_vorbis.so > > /usr/lib/libvorbisenc.so: error adding symbols: File in wrong format > > collect2: error: ld returned 1 exit status > > Makefile:374: recipe for target 'lqt_vorbis.la' failed > > make[3]: *** [lqt_vorbis.la] Error 1 > > make[3]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins/vorbis' > > Makefile:371: recipe for target 'all-recursive' failed > > make[2]: *** [all-recursive] Error 1 > > make[2]: Leaving directory '/tmp/SBo/libquicktime-1.2.4/plugins' > > Makefile:444: recipe for target 'all-recursive' failed > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory '/tmp/SBo/libquicktime-1.2.4' > > Makefile:351: recipe for target 'all' failed > > make: *** [all] Error 2 > > On multilib, you may need this modification in the buildscript: > > ... > > CFLAGS="$SLKCFLAGS" \ > CXXFLAGS="$SLKCFLAGS" \ > LDFLAGS="-L/usr/lib$LIBDIRSUFFIX" \ > ./configure \ > --prefix=/usr \ > > ... > > libquicktime's configure gets confused when there is both /usr/lib > and /usr/lib64 > > -Ed > > 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 davidnchmelik at gmail.com Wed Apr 29 01:07:51 2020 From: davidnchmelik at gmail.com (David Chmelik) Date: Tue, 28 Apr 2020 18:07:51 -0700 Subject: [Slackbuilds-users] palemoon-bin.SlackBuild broken (wrong version number; maintainer unlisted) Message-ID: <6712415f-fdb0-22a4-dd7e-0b4c46881cd4@gmail.com> As said on IRC weeks ago, palemoon-bin is broken: version number in palemoon-bin.SlackBuild (28.8.1) hasn't been updated to used source code version number (28.8.4.)? Additionally, khronosschoty isn't listed maintainer in palemoon-bin.SlackBuild; people will email the old maintaner or check the webpage (where he is listed; ) but his email address is returning mail with an error. Isn't anyone verifying/double-checking submissions anymore?! From dchmelik at gmail.com Wed Apr 29 01:08:07 2020 From: dchmelik at gmail.com (David Chmelik) Date: Tue, 28 Apr 2020 18:08:07 -0700 Subject: [Slackbuilds-users] palemoon-bin.SlackBuild broken (wrong version number; maintainer unlisted) Message-ID: As said on IRC weeks ago, palemoon-bin is broken: version number in palemoon-bin.SlackBuild (28.8.1) hasn't been updated to used source code version number (28.8.4.)? Additionally, khronosschoty isn't listed maintainer in palemoon-bin.SlackBuild; people will email the old maintaner or check the webpage (where he is listed; ) but his email address is returning mail with an error. Isn't anyone verifying/double-checking submissions anymore?! From dave at slackbuilds.org Wed Apr 29 01:25:12 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 29 Apr 2020 02:25:12 +0100 Subject: [Slackbuilds-users] palemoon-bin.SlackBuild broken (wrong version number; maintainer unlisted) In-Reply-To: References: Message-ID: <20200429012512.GA32512@blackswan.r0t.uk> On 2020-04-28 18:08, David Chmelik put forth the proposition: > As said on IRC weeks ago, palemoon-bin is broken: version number in > palemoon-bin.SlackBuild (28.8.1) hasn't been updated to used source code > version number (28.8.4.)? Additionally, khronosschoty isn't listed > maintainer in palemoon-bin.SlackBuild; people will email the old maintaner > or check the webpage (where he is listed; ) but his email address is > returning mail with an error. > > Isn't anyone verifying/double-checking submissions anymore?! Hi David, I've fixed the slackbuild and pushed to my branch. I'll see if I can contact him. -- Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From pfeifer.felix at gmail.com Wed Apr 29 12:34:00 2020 From: pfeifer.felix at gmail.com (Felix Pfeifer) Date: Wed, 29 Apr 2020 14:34:00 +0200 Subject: [Slackbuilds-users] octave requires pcre2 Message-ID: Hi, I was reinstalling octave and it complained about a missing pcre2 during build. Is that only on my system or is it a change that didn't make it into the requirements of the slacksbuilds description? Cheers, Felix From dave at slackbuilds.org Wed Apr 29 13:05:33 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 29 Apr 2020 14:05:33 +0100 Subject: [Slackbuilds-users] octave requires pcre2 In-Reply-To: References: Message-ID: <20200429130533.GC32163@blackswan.r0t.uk> On 2020-04-29 14:34, Felix Pfeifer put forth the proposition: > Hi, > > I was reinstalling octave and it complained about a missing > pcre2 during build. Is that only on my system or is it a change > that didn't make it into the requirements of the slacksbuilds > description? Do you have stock pcre-8.39 installed? It's still building here, but I think that's what it's looking for. Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From phalange at komputermatrix.com Wed Apr 29 13:59:00 2020 From: phalange at komputermatrix.com (Andrew Payne) Date: Wed, 29 Apr 2020 09:59:00 -0400 (EDT) Subject: [Slackbuilds-users] rclone Message-ID: Hi, may I take over rclone? I reached out to the maintainer two weeks ago but no reply. The SBo version is stale. Best, Andrew From pfeifer.felix at gmail.com Wed Apr 29 14:10:25 2020 From: pfeifer.felix at gmail.com (Felix Pfeifer) Date: Wed, 29 Apr 2020 16:10:25 +0200 Subject: [Slackbuilds-users] octave requires pcre2 In-Reply-To: <20200429130533.GC32163@blackswan.r0t.uk> References: <20200429130533.GC32163@blackswan.r0t.uk> Message-ID: On 4/29/20 3:05 PM, Dave Woodfall wrote: > On 2020-04-29 14:34, > Felix Pfeifer put forth the proposition: >> Hi, >> >> I was reinstalling octave and it complained about a missing >> pcre2 during build. Is that only on my system or is it a change >> that didn't make it into the requirements of the slacksbuilds >> description? > > Do you have stock pcre-8.39 installed? > > It's still building here, but I think that's what it's looking for. > Yes, I have stock pcre-8.39 installed. I don't recall the build error exactly but it complained about libpcre2-???.so missing. From dave at slackbuilds.org Wed Apr 29 14:33:03 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 29 Apr 2020 15:33:03 +0100 Subject: [Slackbuilds-users] octave requires pcre2 In-Reply-To: References: <20200429130533.GC32163@blackswan.r0t.uk> Message-ID: <20200429143303.GD32163@blackswan.r0t.uk> On 2020-04-29 16:10, Felix Pfeifer put forth the proposition: > > > On 4/29/20 3:05 PM, Dave Woodfall wrote: > > On 2020-04-29 14:34, > > Felix Pfeifer put forth the proposition: > >> Hi, > >> > >> I was reinstalling octave and it complained about a missing > >> pcre2 during build. Is that only on my system or is it a change > >> that didn't make it into the requirements of the slacksbuilds > >> description? > > > > Do you have stock pcre-8.39 installed? > > > > It's still building here, but I think that's what it's looking for. > > > > Yes, I have stock pcre-8.39 installed. I don't recall the build > error exactly but it complained about libpcre2-???.so missing. It just built here with only pcre not pcre2. Did you rebuild the two dependencies too? Perhaps one of those was built against pcre2, so now it needs it too. Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Wed Apr 29 14:34:35 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 29 Apr 2020 15:34:35 +0100 Subject: [Slackbuilds-users] rclone In-Reply-To: References: Message-ID: <20200429143435.GE32163@blackswan.r0t.uk> On 2020-04-29 09:59, Andrew Payne put forth the proposition: > Hi, may I take over rclone? I reached out to the maintainer two weeks ago > but no reply. The SBo version is stale. > > Best, > Andrew OK. Any preference for maintainer name and email? Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From phalange at komputermatrix.com Wed Apr 29 14:38:44 2020 From: phalange at komputermatrix.com (Andrew Payne) Date: Wed, 29 Apr 2020 10:38:44 -0400 (EDT) Subject: [Slackbuilds-users] rclone In-Reply-To: <20200429143435.GE32163@blackswan.r0t.uk> References: <20200429143435.GE32163@blackswan.r0t.uk> Message-ID: I have an updated build ready to roll. I'll submit via SBo. From stairs.flowers at gmail.com Wed Apr 29 14:37:04 2020 From: stairs.flowers at gmail.com (Andrew Payne) Date: Wed, 29 Apr 2020 10:37:04 -0400 Subject: [Slackbuilds-users] rclone In-Reply-To: <20200429143435.GE32163@blackswan.r0t.uk> References: <20200429143435.GE32163@blackswan.r0t.uk> Message-ID: <088b5486-7d32-a317-ec13-eb9c19a6882a@gmail.com> I have an updated build for 1.5 ready to roll.? I'll submit via SBo. On 4/29/20 10:34 AM, Dave Woodfall wrote: > On 2020-04-29 09:59, > Andrew Payne put forth the proposition: >> Hi, may I take over rclone? I reached out to the maintainer two weeks ago >> but no reply. The SBo version is stale. >> >> Best, >> Andrew > OK. Any preference for maintainer name and email? > > 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 rshepard at appl-ecosys.com Wed Apr 29 16:51:08 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 29 Apr 2020 09:51:08 -0700 (PDT) Subject: [Slackbuilds-users] utimer source download link ... (fwd) Message-ID: My message to Fah bounced: no such user. ---------- Forwarded message ---------- Fah, ... is broken. I get to souceforge.net but it cannot find the utimer source page. Regards, Rich From pfeifer.felix at gmail.com Wed Apr 29 17:00:20 2020 From: pfeifer.felix at gmail.com (Felix Pfeifer) Date: Wed, 29 Apr 2020 19:00:20 +0200 Subject: [Slackbuilds-users] octave requires pcre2 In-Reply-To: <20200429143303.GD32163@blackswan.r0t.uk> References: <20200429130533.GC32163@blackswan.r0t.uk> <20200429143303.GD32163@blackswan.r0t.uk> Message-ID: <00cf5c54-d7fc-12f8-bca8-1d33804ca18e@gmail.com> On 4/29/20 4:33 PM, Dave Woodfall wrote: > On 2020-04-29 16:10, > Felix Pfeifer put forth the proposition: >> >> >> On 4/29/20 3:05 PM, Dave Woodfall wrote: >>> On 2020-04-29 14:34, >>> Felix Pfeifer put forth the proposition: >>>> Hi, >>>> >>>> I was reinstalling octave and it complained about a missing >>>> pcre2 during build. Is that only on my system or is it a change >>>> that didn't make it into the requirements of the slacksbuilds >>>> description? >>> >>> Do you have stock pcre-8.39 installed? >>> >>> It's still building here, but I think that's what it's looking for. >>> >> >> Yes, I have stock pcre-8.39 installed. I don't recall the build >> error exactly but it complained about libpcre2-???.so missing. > > It just built here with only pcre not pcre2. Did you rebuild the two > dependencies too? Perhaps one of those was built against pcre2, so > now it needs it too. > That might be it. From yalhcru at gmail.com Wed Apr 29 18:38:11 2020 From: yalhcru at gmail.com (B Watson) Date: Wed, 29 Apr 2020 14:38:11 -0400 Subject: [Slackbuilds-users] utimer source download link ... (fwd) In-Reply-To: References: Message-ID: On 4/29/20, Rich Shepard wrote: > My message to Fah bounced: no such user. > > ---------- Forwarded message ---------- > Fah, > > ... is broken. I get to souceforge.net but it cannot find the utimer source > page. Hm. I just downloaded the utimer source using the link in the .info file. If you really can't download it from sourceforge, try grabbing it from here: http://slackware.uk/sbosrcarch/by-name/misc/utimer/utimer-0.4.tar.gz It looks like Fah submitted the build in 2012 and has never updated it since then. If you (or anyone else reading this) wants to take over, feel free. Whoever does take over, I see one minor issue with the build: the file /usr/doc/utimer-0.4/NEWS is 0 bytes long, and shouldn't be installed with the package. Also INSTALL is useless, might as well get rid of it too. From rshepard at appl-ecosys.com Wed Apr 29 19:06:20 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 29 Apr 2020 12:06:20 -0700 (PDT) Subject: [Slackbuilds-users] utimer source download link ... (fwd) In-Reply-To: References: Message-ID: On Wed, 29 Apr 2020, B Watson wrote: > Hm. I just downloaded the utimer source using the link in the > .info file. Okay. I didn't think to try that. > It looks like Fah submitted the build in 2012 and has never updated it > since then. That's a shame. > Whoever does take over, I see one minor issue with the build: the file > /usr/doc/utimer-0.4/NEWS is 0 bytes long, and shouldn't be installed with > the package. Also INSTALL is useless, might as well get rid of it too. I downloaded, built, installed, and used the kronometer package. It does exactly what I need it to do: timing presentations before I give them. Thanks, Rich