From willysr at slackbuilds.org Sun May 3 02:03:22 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 May 2020 09:03:22 +0700 Subject: [Slackbuilds-users] Updates - 20200503.1 Message-ID: <3b08272c-82a9-dbb3-b9d6-064752625cf4@slackbuilds.org> Sun May 3 01:49:27 UTC 2020 academic/fet: Fix download link. academic/fet: Updated for version 5.44.3. audio/exhale: Added (a CLI xHE-AAC encoder). audio/mixxx: Remove unnecessary scons routine. business/stansoft: Updated for version 7.19. desktop/breath-gtk-theme: Added (Theme for Manjaro Linux). desktop/i3blocks: Updated for version 1.5. desktop/ssr: Updated for version 0.4.1. desktop/xfce4-wavelan-plugin: Updated for version 0.6.1. development/Sphinx: 3.0.3. development/adoptopenjdk-openj9: Added (Open Implementation of JDK). development/arm-binutils: Updated for version 2.34. development/cgit: Fix GIT version. development/composer: Updated for version 1.10.5 development/d-tools: Updated for version 2.091.1 development/dbeaver-ce: Updated for version 7.0.3. development/dmd: Updated for version 2.091.1 development/dwz: Added (dwarf compressor). development/google-go-lang: Updated for version 1.13.10. development/jdk: Updated for version 8u251. development/mg-troglobit: Fix slack-desc. development/psycopg2: Updated for version 2.8.5. development/robotframework: Updated for version 3.2. development/sbcl: Updated for version 2.0.4. development/svn-all-fast-export: Updated for version 1.0.18. development/universal-ctags: Updated for version 41e1fb6 games/crispy-doom: Updated for version 5.8.0. games/endless-sky: updated for version 0.9.12 games/fs-uae-arcade: Updated for version 3.0.3. games/fs-uae-launcher: Updated for version 3.0.3. games/fs-uae: Updated for version 3.0.3, moved from system. games/gzdoom-legacy: Fix window title. games/hatari: Support IPF/CTR images, various fixes. games/jfsw: Update docs, support Twin Dragon. games/jfsw_registered_data: Use CD image as source. games/jfsw_twin_dragon: Added (game data for Shadow Warrior) games/nblood: Added (Game Engine for Blood). games/powerslave_demo_data: Added (game data for nblood). games/steam: Updated for version 1.0.0.62 gis/OTB: Updated for version 7.1.0. gis/ossim: Updated for version 2.11.1. gis/pdal: Updated for version 2.1.0. gis/proj: Updated for 7.0.1. gis/saga-gis: Updated for version 7.6.2. graphics/SweetHome3D: changed src for openjdk8 graphics/SweetHome3D: updated for version 6.3 graphics/fritzing: build against newer version of libgit2 graphics/ueberzug: Added ueberzug (An alternative to w3mimgdisplay). haskell/haskell-ShellCheck: Updated for version 0.7.1. libraries/grantlee-qt5: Updated for version 5.2.0 libraries/grpc: Updated for version 1.28.1 libraries/jsoncpp: Updated for version 1.9.2 libraries/libaal: Updated for version 1.0.7. libraries/libbluray: Updated for version 1.2.0 libraries/libcapsimage: Added libcapsimage (decoder library) libraries/libcbor: updated for version 0.7.0 libraries/libcec: Updated for version 4.0.4 libraries/libgit2-glib: build against newer version of libgit2 libraries/libgit2: Updated for version 1.0.0 libraries/libotf: Updated for version 0.9.16 libraries/libsass: updated for version 3.6.4 libraries/liburcu: Updated for version 0.12.1. libraries/live555: Updated for version 2020.04.24 libraries/nltk: Updated for version 3.5. libraries/python3-PyQt5: Change python3 include path. libraries/qt5: Update README. libraries/re2: Updated for version 2020_05_01 libraries/tinyxml2: Updated for version 8.0.0 libraries/wxGTK3: Updated for version 3.0.5. libraries/xmlsec: Updated for version 1.2.30. misc/bchunk: Updated for version 1.2.2. misc/dvtm: Fix and install terminfo. misc/subsurface: Fix building against newer version of libgit2 multimedia/MuseScore: Updated for version 3.4.2. multimedia/plexmediaserver: Updated for v 1.19.2.2737_b69929dab. multimedia/vlc: Updated for version 3.0.10 multimedia/xmms-cue: Added xmms-cue (XMMS Cuesheet reader plugin). network/coturn: Updated for version 4.5.1.2. network/hostapd: Updated for version 2.9. network/opensmtpd-extras: updated for version 6.7.1 network/owncloud-client: Updated for version 2.5.4.11654. network/palemoon-bin: Fix SlackBuild for version 28.8.4. network/pexip-infinity-connect: Add missing image. network/prosody-mod-cloud-notify: Updated for version hg3979. network/prosody-mod-smacks: Updated for version hg3986. network/qutebrowser-tox: Updated for version 1.11.0. network/shorewall-core: Updated for version 5.2.4.4. network/shorewall6: Updated for version 5.2.4.4. network/shorewall: Updated for version 5.2.4.4. network/signal-desktop: Updated for version 1.33.3. network/sqlmap: Updated for version 1.4.4. network/teamviewer: Updated for version 15.5.3. network/telegram: Updated for version 2.1.0. network/telegram: Updated for version 2.1.1. network/tgt: Added SCSI target driver (iSCSI, Fibre Channel, SRP, etc) network/unbound: Updated for version 1.10.0. network/vivaldi: Updated for version 3.0.1874.33. network/wireguard-linux-compat: Updated for version 1.0.20200429. network/zabbix_agentd: Updated for version 4.4.7. network/zabbix_java_gateway: Updated for version 4.4.7. network/zabbix_proxy: Updated for version 4.4.7. network/zabbix_server: Updated for version 4.4.7. network/zoom-linux: Updated for version 5.0.398100.0427. office/calcurse: Updated for version 4.6.0. office/calibre-bin: Updated for version 4.14.0. office/calibre-bin: Updated for version 4.15.0. office/htmldoc: Updated for version 1.9.8. office/pdfstudio: Updated for version 2019.2.2. office/pdfstudioviewer: Updated for version 2019.2.2. perl/perl-Data-IEEE754: Added (Support for IEEE754 floats) perl/perl-MaxMind-DB-Common: Added (Common code/metadata) perl/perl-Net-ARP: Updated for version 1.0.10. perl/perl-Net-Works: Added (APIs for IP addresses and networks) perl/perl-Path-Tiny: Updated for version 0.114. perl/perl-Test-Bits: Added perl-Test-Bits (Test single bits) python/PyGreSQL: Updated for version 5.1.2 python/bleach: Updated for version 3.1.5. python/et_xmlfile: Added (python library to create large XML files) python/jdcal: Added jdcal (python module to convert dates) python/pyperclip: Updated for version 1.7.0. python/python-configargparse: Updated for version 1.2.3. python/python-toml: Added (A Python library). python/python3-aiohttp-socks: Updated for version 0.3.9. python/python3-openpyxl: Added (lib to read/write Excel 2010 files) python/python3-sip: Change python3 include path. python/sphinxcontrib-websupport: Updated for version 1.2.2. ruby/ruby-native-package-installer: Updated for version 1.0.9. ruby/rubygem-mime-types-data: Updated for version 3.2020.0425. ruby/rubygem-parser: Updated for version 2.7.1.1. system/avfs: Updated for version 1.1.2. system/bat: Updated for version 0.15.0. system/corosync: Updated for version 2.4.5. system/dlm: Updated for version 4.0.9. system/dtrx: Updated for version 7.1. system/epson-inkjet-printer-escpr2: Updated for version 1.1.11. system/fio: Updated for version 3.19. system/hwloc: Updated for version 2.2.0. system/isextract: Added (extract v3 InstallShield files). system/kapacitor: Updated for version 1.5.5. system/kbfs: Updated for version 5.4.2_20200424214931. system/keybase: Updated for version 5.4.2. system/motion: Updated for version 4.3.1. system/numactl: Updated for version 2.0.13. system/nvme-cli: Updated for version 1.11.1. system/pacemaker: Updated for version 2.0.3. system/passwordsafe: Updated for version 1.010.0. system/phoronix-test-suite: Updated for version 9.6.0. system/pspg: Updated for version 3.0.7. system/rclone: Updated for version 1.51.0. system/reiserfs4progs: Updated for version 1.2.1. system/sysdig: Updated for version 0.26.6 system/wine-staging: Updated for version 5.7. system/wine: Updated for version 5.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 willysr at slackbuilds.org Sun May 3 15:17:33 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 May 2020 22:17:33 +0700 Subject: [Slackbuilds-users] nodejs update Message-ID: Hi IL KA has provided a solution to update nodejs to the latest LTS release without having to upgrade openssl version in Slackware, and that is to use the internal openssl provided in the source instead of using shared library provided by Slackware package. For maintainers who maintains scripts that depends on nodejs, it's time to test it against new version of nodejs thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From achirvasub at gmail.com Sun May 3 14:51:24 2020 From: achirvasub at gmail.com (AC) Date: Sun, 03 May 2020 10:51:24 -0400 Subject: [Slackbuilds-users] snappy 1.1.8 Slackbuild fails to build on 14.2 In-Reply-To: <881afe44-62c9-d1af-c995-c3ff55517d10@gmail.com> References: <20200329232254.GA7712@chirva-slack.chirva-slack> <20200329235211.GB7712@chirva-slack.chirva-slack> <881afe44-62c9-d1af-c995-c3ff55517d10@gmail.com> Message-ID: Apologies for the long delay: my Slackware machine doesn't see the light of day that often. The new slackbuild installs fine, thank you! On April 1, 2020 1:48:49 PM EDT, "M?rio Antunes" wrote: >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_ptrstd::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()' >>> 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<< const*>(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<< [5]>(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::CmpHelperOpFailurechar>(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::CmpHelperOpFailureunsigned short>(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 From erich.public at protonmail.com Tue May 5 00:05:28 2020 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 05 May 2020 00:05:28 +0000 Subject: [Slackbuilds-users] bat: failed build (newer rust required?) Message-ID: Hi Benjamin and list, Trying to build system/bat from a 64-bit chroot using sbopkg I get the following error: ... Compiling git2 v0.13.3 error: enum variants on type aliases are experimental --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:24:48 | 24 | raw::GIT_APPLY_LOCATION_WORKDIR => Self::WorkDir, | ^^^^^^^^^^^^^ error: enum variants on type aliases are experimental --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:25:46 | 25 | raw::GIT_APPLY_LOCATION_INDEX => Self::Index, | ^^^^^^^^^^^ error: enum variants on type aliases are experimental --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:26:45 | 26 | raw::GIT_APPLY_LOCATION_BOTH => Self::Both, | ^^^^^^^^^^ error: enum variants on type aliases are experimental --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:32:13 | 32 | Self::WorkDir => raw::GIT_APPLY_LOCATION_WORKDIR, | ^^^^^^^^^^^^^ error: enum variants on type aliases are experimental --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:33:13 | 33 | Self::Index => raw::GIT_APPLY_LOCATION_INDEX, | ^^^^^^^^^^^ error: enum variants on type aliases are experimental --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:34:13 | 34 | Self::Both => raw::GIT_APPLY_LOCATION_BOTH, | ^^^^^^^^^^ error: aborting due to 6 previous errors error: Could not compile `git2`. warning: build failed, waiting for other jobs to finish... error: build failed I have rust 1.36.0 installed: # ls /var/log/packages/ | grep rust rust-1.36.0-x86_64-1_slack14.2 Does bat (actually in this case it looks like the git2 library (crate, whatever)) require a newer rust? Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From wedinm at gmail.com Tue May 5 14:16:33 2020 From: wedinm at gmail.com (M Wedin) Date: Tue, 5 May 2020 16:16:33 +0200 Subject: [Slackbuilds-users] I failed to build qt5 Message-ID: The old qt 5.9.9 was removed. I did have some stuff after the env check. So I exited root and logged in again in the terminal window. The next check showed the following: # env | grep -i qt5 PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# Thus I ran the command ./qt5.SlackBuild [641/2162] /usr/bin/g++ -MMD -MF obj/content/browser/browser/save_package.o.d -DENABLE_SCREEN_CAPTURE=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 -DCONTENT_IMPLEMENTATION -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -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\" -DLEVELDB_PLATFORM_CHROMIUM=1 -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DMESA_EGL_NO_X11_HEADERS -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DUSE_SYSTEM_ZLIB=1 -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 -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/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/libwebm/source -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -I../../3rdparty/chromium/third_party/leveldatabase -I../../3rdparty/chromium/third_party/leveldatabase/src -I../../3rdparty/chromium/third_party/leveldatabase/src/include -I../../3rdparty/chromium/third_party/webrtc_overrides -I../../3rdparty/chromium/testing/gtest/include -I../../3rdparty/chromium/third_party/webrtc -I../../3rdparty/chromium/third_party/webrtc_overrides -I../../3rdparty/chromium/third_party/webrtc -Igen/third_party/metrics_proto -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/third_party/mesa/src/include -I../../3rdparty/chromium/v8/include -Igen/v8/include -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base -Igen/angle -I../../3rdparty/chromium/third_party/brotli/include -I../../3rdparty/chromium/third_party/re2/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 -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -isystem../../../../../../../usr/include/nss -isystem../../../../../../../usr/include/nspr -isystem ../../3rdparty/chromium/third_party/abseil-cpp -isystem../../../../../../../usr/include/dbus-1.0 -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c ../../3rdparty/chromium/content/browser/download/save_package.cc -o obj/content/browser/browser/save_package.o ninja: build stopped: subcommand failed. Makefile.gn_run:1151: recipe for target 'run_ninja' failed make[4]: *** [run_ninja] Error 1 make[4]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.8/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.8/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.8/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.8/qtwebengine' Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed make: *** [module-qtwebengine-make_first] Error 2 root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# My machine takes well over 24 hours to this stage. So any help is appreciated. Wedin From davidnchmelik at gmail.com Tue May 5 14:24:55 2020 From: davidnchmelik at gmail.com (David Chmelik) Date: Tue, 5 May 2020 07:24:55 -0700 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: On 5/5/20 7:16 AM, M Wedin wrote: > The old qt 5.9.9 was removed. > > I did have some stuff after the env check. So I exited root and logged > in again in the terminal window. The next check showed the following: > > # env | grep -i qt5 > PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > > Thus I ran the command > ./qt5.SlackBuild > > [641/2162] /usr/bin/g++ -MMD -MF > obj/content/browser/browser/save_package.o.d -DENABLE_SCREEN_CAPTURE=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 -DCONTENT_IMPLEMENTATION > -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -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\" > -DLEVELDB_PLATFORM_CHROMIUM=1 > -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH > -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX > -DMESA_EGL_NO_X11_HEADERS -DABSL_ALLOCATOR_NOTHROW=1 > -DNO_MAIN_THREAD_WRAPPING -DUSE_SYSTEM_ZLIB=1 -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 > -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/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/libwebm/source > -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out > -I../../3rdparty/chromium/third_party/leveldatabase > -I../../3rdparty/chromium/third_party/leveldatabase/src > -I../../3rdparty/chromium/third_party/leveldatabase/src/include > -I../../3rdparty/chromium/third_party/webrtc_overrides > -I../../3rdparty/chromium/testing/gtest/include > -I../../3rdparty/chromium/third_party/webrtc > -I../../3rdparty/chromium/third_party/webrtc_overrides > -I../../3rdparty/chromium/third_party/webrtc > -Igen/third_party/metrics_proto > -I../../3rdparty/chromium/third_party/boringssl/src/include > -I../../3rdparty/chromium/third_party/mesa/src/include > -I../../3rdparty/chromium/v8/include -Igen/v8/include > -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base > -Igen/angle -I../../3rdparty/chromium/third_party/brotli/include > -I../../3rdparty/chromium/third_party/re2/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 -O2 -fno-ident > -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 > -fvisibility=hidden -isystem../../../../../../../usr/include/nss > -isystem../../../../../../../usr/include/nspr -isystem > ../../3rdparty/chromium/third_party/abseil-cpp > -isystem../../../../../../../usr/include/dbus-1.0 > -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 > -Wno-narrowing -Wno-attributes -Wno-class-memaccess > -Wno-subobject-linkage -fno-exceptions -fno-rtti > -fvisibility-inlines-hidden -c > ../../3rdparty/chromium/content/browser/download/save_package.cc -o > obj/content/browser/browser/save_package.o > ninja: build stopped: subcommand failed. > Makefile.gn_run:1151: recipe for target 'run_ninja' failed > make[4]: *** [run_ninja] Error 1 > make[4]: Leaving directory > '/tmp/SBo/qt-everywhere-src-5.12.8/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.8/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.8/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.8/qtwebengine' > Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed > make: *** [module-qtwebengine-make_first] Error 2 > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > > My machine takes well over 24 hours to this stage. So any help is appreciated. > > Wedin In recent days, I couldn't build qt5 either, on a machine I'm not using qt programs often enough that it's more than a minor problem yet, but if I recall correctly (IIRC) I had a similar/same problem as above. From willysr at slackbuilds.org Tue May 5 14:32:39 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 5 May 2020 21:32:39 +0700 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: >> I did have some stuff after the env check. So I exited root and logged >> in again in the terminal window. The next check showed the following: >> >> # env | grep -i qt5 >> PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 >> root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# >> >> Thus I ran the command >> ./qt5.SlackBuild >> My machine takes well over 24 hours to this stage. So any help is >> appreciated. >> >> Wedin > > In recent days, I couldn't build qt5 either, on a machine I'm not using > qt programs often enough that it's more than a minor problem yet, but if > I recall correctly (IIRC) I had a similar/same problem as above. i was able to build qt5 on my slow build machine with only 2 GB of RAM but i used 8 GB of swap space. It just took longer to build (more than 1 day i believe). -- 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 wedinm at gmail.com Tue May 5 14:45:15 2020 From: wedinm at gmail.com (M Wedin) Date: Tue, 5 May 2020 16:45:15 +0200 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: 2020-05-05 16:32 GMT+02:00, Willy Sudiarto Raharjo : >>> I did have some stuff after the env check. So I exited root and logged >>> in again in the terminal window. The next check showed the following: >>> >>> # env | grep -i qt5 >>> PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 >>> root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# >>> >>> Thus I ran the command >>> ./qt5.SlackBuild > >>> My machine takes well over 24 hours to this stage. So any help is >>> appreciated. >>> >>> Wedin >> >> In recent days, I couldn't build qt5 either, on a machine I'm not using >> qt programs often enough that it's more than a minor problem yet, but if >> I recall correctly (IIRC) I had a similar/same problem as above. > > i was able to build qt5 on my slow build machine with only 2 GB of RAM > but i used 8 GB of swap space. It just took longer to build (more than 1 > day i believe). I can live with the time frame. But I'd like to get a package for the effort. Is there any issue I can fix for the next attempt? I don't understand the error. I have 4GB RAM and 3GB Swap. It is sufficient for daily use. Wedin From dave at slackbuilds.org Tue May 5 16:21:16 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 5 May 2020 17:21:16 +0100 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: <20200505162116.GC11324@blackswan.r0t.uk> On 2020-05-05 16:16, M Wedin put forth the proposition: > The old qt 5.9.9 was removed. The old qt 5.9.9 was renamed to qt5-legacy. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From wedinm at gmail.com Tue May 5 21:18:40 2020 From: wedinm at gmail.com (M Wedin) Date: Tue, 5 May 2020 23:18:40 +0200 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: <20200505162116.GC11324@blackswan.r0t.uk> References: <20200505162116.GC11324@blackswan.r0t.uk> Message-ID: 2020-05-05 18:21 GMT+02:00, Dave Woodfall : > On 2020-05-05 16:16, > M Wedin put forth the proposition: >> The old qt 5.9.9 was removed. > > The old qt 5.9.9 was renamed to qt5-legacy. I removed it per recommendation. Sorry if I wasn't clear. I wanted as few obstacles as possible. ------------- If Qt5 fails to build, it may be worth using the following steps. 1 Uninstall the old Qt5 package ------------- Wedin From dave at slackbuilds.org Wed May 6 00:31:41 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 6 May 2020 01:31:41 +0100 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: <20200505162116.GC11324@blackswan.r0t.uk> Message-ID: <20200506003141.GE11324@blackswan.r0t.uk> On 2020-05-05 23:18, M Wedin put forth the proposition: > 2020-05-05 18:21 GMT+02:00, Dave Woodfall : > > On 2020-05-05 16:16, > > M Wedin put forth the proposition: > >> The old qt 5.9.9 was removed. > > > > The old qt 5.9.9 was renamed to qt5-legacy. > > I removed it per recommendation. Sorry if I wasn't clear. I wanted as > few obstacles as possible. > > ------------- > If Qt5 fails to build, it may be worth using the following > steps. > > 1 Uninstall the old Qt5 package > ------------- My point was that if qt5-5.12 takes too long or won't build, then you could use qt5-legacy instead of qt5. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From davidnchmelik at gmail.com Wed May 6 02:23:50 2020 From: davidnchmelik at gmail.com (David Chmelik) Date: Tue, 5 May 2020 19:23:50 -0700 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: <20200506003141.GE11324@blackswan.r0t.uk> References: <20200505162116.GC11324@blackswan.r0t.uk> <20200506003141.GE11324@blackswan.r0t.uk> Message-ID: <4f09fdf9-4fba-876d-04ba-bbfb9871fea4@gmail.com> On 5/5/20 5:31 PM, Dave Woodfall wrote: > On 2020-05-05 23:18, > M Wedin put forth the proposition: >> 2020-05-05 18:21 GMT+02:00, Dave Woodfall : >>> On 2020-05-05 16:16, >>> M Wedin put forth the proposition: >>>> The old qt 5.9.9 was removed. >>> The old qt 5.9.9 was renamed to qt5-legacy. >> I removed it per recommendation. Sorry if I wasn't clear. I wanted as >> few obstacles as possible. >> >> ------------- >> If Qt5 fails to build, it may be worth using the following >> steps. >> >> 1 Uninstall the old Qt5 package >> ------------- > My point was that if qt5-5.12 takes too long or won't build, then you > could use qt5-legacy instead of qt5. If all one has to do is remove & rebuild, surely it's worth the wait to compile to upgrade?? That's what I'll do.? Another option might be if one of almost all pre-built SlackOnly.com (?slonly?) packages, if you judge them trustworthy. From dave at slackbuilds.org Wed May 6 04:07:52 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 6 May 2020 05:07:52 +0100 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: <4f09fdf9-4fba-876d-04ba-bbfb9871fea4@gmail.com> References: <20200505162116.GC11324@blackswan.r0t.uk> <20200506003141.GE11324@blackswan.r0t.uk> <4f09fdf9-4fba-876d-04ba-bbfb9871fea4@gmail.com> Message-ID: <20200506040752.GF11324@blackswan.r0t.uk> On 2020-05-05 19:23, David Chmelik put forth the proposition: > On 5/5/20 5:31 PM, Dave Woodfall wrote: > > On 2020-05-05 23:18, > > M Wedin put forth the proposition: > > > 2020-05-05 18:21 GMT+02:00, Dave Woodfall : > > > > On 2020-05-05 16:16, > > > > M Wedin put forth the proposition: > > > > > The old qt 5.9.9 was removed. > > > > The old qt 5.9.9 was renamed to qt5-legacy. > > > I removed it per recommendation. Sorry if I wasn't clear. I wanted as > > > few obstacles as possible. > > > > > > ------------- > > > If Qt5 fails to build, it may be worth using the following > > > steps. > > > > > > 1 Uninstall the old Qt5 package > > > ------------- > > My point was that if qt5-5.12 takes too long or won't build, then you > > could use qt5-legacy instead of qt5. > > If all one has to do is remove & rebuild, surely it's worth the wait to > compile to upgrade?? That's what I'll do.? Another option might be if one of > almost all pre-built SlackOnly.com (?slonly?) packages, if you judge them > trustworthy. I don't know slackonly enough to comment on that. -------------- 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 May 6 04:10:06 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 6 May 2020 05:10:06 +0100 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: <20200506041006.GG11324@blackswan.r0t.uk> On 2020-05-05 16:16, M Wedin put forth the proposition: > The old qt 5.9.9 was removed. > > I did have some stuff after the env check. So I exited root and logged > in again in the terminal window. The next check showed the following: > > # env | grep -i qt5 > PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > > Thus I ran the command > ./qt5.SlackBuild > > [641/2162] /usr/bin/g++ -MMD -MF > obj/content/browser/browser/save_package.o.d -DENABLE_SCREEN_CAPTURE=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 -DCONTENT_IMPLEMENTATION > -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -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\" > -DLEVELDB_PLATFORM_CHROMIUM=1 > -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH > -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX > -DMESA_EGL_NO_X11_HEADERS -DABSL_ALLOCATOR_NOTHROW=1 > -DNO_MAIN_THREAD_WRAPPING -DUSE_SYSTEM_ZLIB=1 -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 > -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/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/libwebm/source > -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out > -I../../3rdparty/chromium/third_party/leveldatabase > -I../../3rdparty/chromium/third_party/leveldatabase/src > -I../../3rdparty/chromium/third_party/leveldatabase/src/include > -I../../3rdparty/chromium/third_party/webrtc_overrides > -I../../3rdparty/chromium/testing/gtest/include > -I../../3rdparty/chromium/third_party/webrtc > -I../../3rdparty/chromium/third_party/webrtc_overrides > -I../../3rdparty/chromium/third_party/webrtc > -Igen/third_party/metrics_proto > -I../../3rdparty/chromium/third_party/boringssl/src/include > -I../../3rdparty/chromium/third_party/mesa/src/include > -I../../3rdparty/chromium/v8/include -Igen/v8/include > -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base > -Igen/angle -I../../3rdparty/chromium/third_party/brotli/include > -I../../3rdparty/chromium/third_party/re2/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 -O2 -fno-ident > -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 > -fvisibility=hidden -isystem../../../../../../../usr/include/nss > -isystem../../../../../../../usr/include/nspr -isystem > ../../3rdparty/chromium/third_party/abseil-cpp > -isystem../../../../../../../usr/include/dbus-1.0 > -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 > -Wno-narrowing -Wno-attributes -Wno-class-memaccess > -Wno-subobject-linkage -fno-exceptions -fno-rtti > -fvisibility-inlines-hidden -c > ../../3rdparty/chromium/content/browser/download/save_package.cc -o > obj/content/browser/browser/save_package.o > ninja: build stopped: subcommand failed. > Makefile.gn_run:1151: recipe for target 'run_ninja' failed > make[4]: *** [run_ninja] Error 1 > make[4]: Leaving directory > '/tmp/SBo/qt-everywhere-src-5.12.8/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.8/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.8/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.8/qtwebengine' > Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed > make: *** [module-qtwebengine-make_first] Error 2 > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# Can you try installing the ninja package from SBo, since the error seems to be connected with that? https://slackbuilds.org/repository/14.2/development/ninja/ -- 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 Wed May 6 05:21:43 2020 From: chris.willing at linux.com (Christoph Willing) Date: Wed, 6 May 2020 15:21:43 +1000 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: On 6/5/20 12:16 am, M Wedin wrote: > The old qt 5.9.9 was removed. > > I did have some stuff after the env check. So I exited root and logged > in again in the terminal window. The next check showed the following: > > # env | grep -i qt5 > PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > > Thus I ran the command > ./qt5.SlackBuild > > [641/2162] /usr/bin/g++ -MMD -MF > obj/content/browser/browser/save_package.o.d -DENABLE_SCREEN_CAPTURE=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 -DCONTENT_IMPLEMENTATION > -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -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\" > -DLEVELDB_PLATFORM_CHROMIUM=1 > -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH > -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX > -DMESA_EGL_NO_X11_HEADERS -DABSL_ALLOCATOR_NOTHROW=1 > -DNO_MAIN_THREAD_WRAPPING -DUSE_SYSTEM_ZLIB=1 -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 > -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/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/libwebm/source > -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out > -I../../3rdparty/chromium/third_party/leveldatabase > -I../../3rdparty/chromium/third_party/leveldatabase/src > -I../../3rdparty/chromium/third_party/leveldatabase/src/include > -I../../3rdparty/chromium/third_party/webrtc_overrides > -I../../3rdparty/chromium/testing/gtest/include > -I../../3rdparty/chromium/third_party/webrtc > -I../../3rdparty/chromium/third_party/webrtc_overrides > -I../../3rdparty/chromium/third_party/webrtc > -Igen/third_party/metrics_proto > -I../../3rdparty/chromium/third_party/boringssl/src/include > -I../../3rdparty/chromium/third_party/mesa/src/include > -I../../3rdparty/chromium/v8/include -Igen/v8/include > -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base > -Igen/angle -I../../3rdparty/chromium/third_party/brotli/include > -I../../3rdparty/chromium/third_party/re2/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 -O2 -fno-ident > -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 > -fvisibility=hidden -isystem../../../../../../../usr/include/nss > -isystem../../../../../../../usr/include/nspr -isystem > ../../3rdparty/chromium/third_party/abseil-cpp > -isystem../../../../../../../usr/include/dbus-1.0 > -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 > -Wno-narrowing -Wno-attributes -Wno-class-memaccess > -Wno-subobject-linkage -fno-exceptions -fno-rtti > -fvisibility-inlines-hidden -c > ../../3rdparty/chromium/content/browser/download/save_package.cc -o > obj/content/browser/browser/save_package.o > ninja: build stopped: subcommand failed. > Makefile.gn_run:1151: recipe for target 'run_ninja' failed > make[4]: *** [run_ninja] Error 1 > make[4]: Leaving directory > '/tmp/SBo/qt-everywhere-src-5.12.8/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.8/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.8/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.8/qtwebengine' > Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed > make: *** [module-qtwebengine-make_first] Error 2 > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > Have you changed the SlackBuild in any way? I saw a similar problem recently while experimenting with the use of additional "system" libraries (as opposed to using third party code included in the source tarball). One thing that stands out is: > -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 I don't think that standard is supported in the stock g++ supplied with 14.2 is it? Sorry I don't recall exactly which additional system package triggered that particular error. It may have been ffmpeg because that was definitely one system package that I couldn't integrate into the qt5 build at all. However I"m not sure if that failure was the one associated with the c++14 and subsequent meson error. Good luck, chris From dave at slackbuilds.org Wed May 6 05:33:49 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 6 May 2020 06:33:49 +0100 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: <20200506053349.GH11324@blackswan.r0t.uk> On 2020-05-06 15:21, Christoph Willing put forth the proposition: > On 6/5/20 12:16 am, M Wedin wrote: > > The old qt 5.9.9 was removed. > > > > I did have some stuff after the env check. So I exited root and logged > > in again in the terminal window. The next check showed the following: > > > > # env | grep -i qt5 > > PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 > > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > > > > Thus I ran the command > > ./qt5.SlackBuild > > > > [641/2162] /usr/bin/g++ -MMD -MF > > obj/content/browser/browser/save_package.o.d -DENABLE_SCREEN_CAPTURE=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 -DCONTENT_IMPLEMENTATION > > -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -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\" > > -DLEVELDB_PLATFORM_CHROMIUM=1 > > -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH > > -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX > > -DMESA_EGL_NO_X11_HEADERS -DABSL_ALLOCATOR_NOTHROW=1 > > -DNO_MAIN_THREAD_WRAPPING -DUSE_SYSTEM_ZLIB=1 -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 > > -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/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/libwebm/source > > -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out > > -I../../3rdparty/chromium/third_party/leveldatabase > > -I../../3rdparty/chromium/third_party/leveldatabase/src > > -I../../3rdparty/chromium/third_party/leveldatabase/src/include > > -I../../3rdparty/chromium/third_party/webrtc_overrides > > -I../../3rdparty/chromium/testing/gtest/include > > -I../../3rdparty/chromium/third_party/webrtc > > -I../../3rdparty/chromium/third_party/webrtc_overrides > > -I../../3rdparty/chromium/third_party/webrtc > > -Igen/third_party/metrics_proto > > -I../../3rdparty/chromium/third_party/boringssl/src/include > > -I../../3rdparty/chromium/third_party/mesa/src/include > > -I../../3rdparty/chromium/v8/include -Igen/v8/include > > -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base > > -Igen/angle -I../../3rdparty/chromium/third_party/brotli/include > > -I../../3rdparty/chromium/third_party/re2/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 -O2 -fno-ident > > -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 > > -fvisibility=hidden -isystem../../../../../../../usr/include/nss > > -isystem../../../../../../../usr/include/nspr -isystem > > ../../3rdparty/chromium/third_party/abseil-cpp > > -isystem../../../../../../../usr/include/dbus-1.0 > > -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 > > -Wno-narrowing -Wno-attributes -Wno-class-memaccess > > -Wno-subobject-linkage -fno-exceptions -fno-rtti > > -fvisibility-inlines-hidden -c > > ../../3rdparty/chromium/content/browser/download/save_package.cc -o > > obj/content/browser/browser/save_package.o > > ninja: build stopped: subcommand failed. > > Makefile.gn_run:1151: recipe for target 'run_ninja' failed > > make[4]: *** [run_ninja] Error 1 > > make[4]: Leaving directory > > '/tmp/SBo/qt-everywhere-src-5.12.8/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.8/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.8/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.8/qtwebengine' > > Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed > > make: *** [module-qtwebengine-make_first] Error 2 > > root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > > > > Have you changed the SlackBuild in any way? I saw a similar problem > recently while experimenting with the use of additional "system" > libraries (as opposed to using third party code included in the source > tarball). > > One thing that stands out is: > > -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 > > I don't think that standard is supported in the stock g++ supplied with > 14.2 is it? > > Sorry I don't recall exactly which additional system package triggered > that particular error. It may have been ffmpeg because that was > definitely one system package that I couldn't integrate into the qt5 > build at all. However I"m not sure if that failure was the one > associated with the c++14 and subsequent meson error. > > Good luck, > chris Yes, the 5.9.x slackbuild used c++11 explicitly, because (python3-)PyQt5 wouldn't build without it. I noticed that it wasn't needed after updating PyQt5, and that it built fine without it so I removed it. It has been commented on before, and I wasn't sure whether to add it back in or not. I guess it won't hurt to take it down a few pegs. -- Dave -------------- 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 Wed May 6 07:32:31 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 06 May 2020 07:32:31 +0000 Subject: [Slackbuilds-users] bat: failed build (newer rust required?) In-Reply-To: References: Message-ID: <6a860ed3-8626-425e-a1bd-52c7aefb1a0b@www.fastmail.com> On Tue, 5 May 2020, at 12:05 AM, Erich Ritz via SlackBuilds-users wrote: > Hi Benjamin and list, > > Trying to build system/bat from a 64-bit chroot using sbopkg I get the following error: > > ... > Compiling git2 v0.13.3 > error: enum variants on type aliases are experimental > --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:24:48 > | > 24 | raw::GIT_APPLY_LOCATION_WORKDIR => Self::WorkDir, > | ^^^^^^^^^^^^^ > > > Does bat (actually in this case it looks like the git2 library (crate, whatever)) require a newer rust? I don't know about 0.15.0, but the version on SBo (0.13.0) builds for me on both -current and in 14.2. I'd test with the newer release, but the .info file looks like it must take some automation to prepare! Had never heard of bat though, nice program (from the author of the excellent fd too). Seems to nicely replace both cat and less for cmd-line usage. -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From wedinm at gmail.com Wed May 6 12:19:03 2020 From: wedinm at gmail.com (M Wedin) Date: Wed, 6 May 2020 14:19:03 +0200 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: <4f09fdf9-4fba-876d-04ba-bbfb9871fea4@gmail.com> References: <20200505162116.GC11324@blackswan.r0t.uk> <20200506003141.GE11324@blackswan.r0t.uk> <4f09fdf9-4fba-876d-04ba-bbfb9871fea4@gmail.com> Message-ID: >>> 1 Uninstall the old Qt5 package >>> ------------- >> My point was that if qt5-5.12 takes too long or won't build, then you >> could use qt5-legacy instead of qt5. > > If all one has to do is remove & rebuild, surely it's worth the wait to > compile to upgrade? That's what I'll do. Another option might be if > one of almost all pre-built SlackOnly.com (?slonly?) packages, if you > judge them trustworthy. I thought it worthwhile, so I tried to rebuild after removal of the older version. It's just that it bailed on me. I could possibly try to fetch somebody elses package. Wedin From wedinm at gmail.com Wed May 6 12:21:55 2020 From: wedinm at gmail.com (M Wedin) Date: Wed, 6 May 2020 14:21:55 +0200 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: <20200506041006.GG11324@blackswan.r0t.uk> References: <20200506041006.GG11324@blackswan.r0t.uk> Message-ID: >> ninja: build stopped: subcommand failed. >> Makefile.gn_run:1151: recipe for target 'run_ninja' failed >> make[4]: *** [run_ninja] Error 1 >> make[4]: Leaving directory >> '/tmp/SBo/qt-everywhere-src-5.12.8/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.8/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.8/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.8/qtwebengine' >> Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed >> make: *** [module-qtwebengine-make_first] Error 2 >> root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# > > Can you try installing the ninja package from SBo, since the error > seems to be connected with that? > > https://slackbuilds.org/repository/14.2/development/ninja/ It is installed. It is a dep of somethings something. I checked. I'll be happy to recompile and install it though if it helps me with the main package. Wedin From wedinm at gmail.com Wed May 6 12:27:07 2020 From: wedinm at gmail.com (M Wedin) Date: Wed, 6 May 2020 14:27:07 +0200 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: > Have you changed the SlackBuild in any way? I saw a similar problem > recently while experimenting with the use of additional "system" > libraries (as opposed to using third party code included in the source > tarball). No. I haven't changed a single thing. I tried at first to update it with sboupgrade. But that failed instantly. So I downloaded the tar.gz from slackbuilds.org and the source for qt5 via slackbuilds.org. That's it. I ran ./qt5.SlackBuild without any options. > One thing that stands out is: >> -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 > > I don't think that standard is supported in the stock g++ supplied with > 14.2 is it? That's beyond me. Wedin From dave at slackbuilds.org Wed May 6 15:00:03 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 6 May 2020 16:00:03 +0100 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: Message-ID: <20200506150003.GA8269@blackswan.r0t.uk> On 2020-05-06 14:27, M Wedin put forth the proposition: > > Have you changed the SlackBuild in any way? I saw a similar problem > > recently while experimenting with the use of additional "system" > > libraries (as opposed to using third party code included in the source > > tarball). > > No. I haven't changed a single thing. I tried at first to update it > with sboupgrade. But that failed instantly. So I downloaded the tar.gz > from slackbuilds.org and the source for qt5 via slackbuilds.org. > That's it. I ran ./qt5.SlackBuild without any options. > > > One thing that stands out is: > >> -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 > > > > I don't think that standard is supported in the stock g++ supplied with > > 14.2 is it? > > That's beyond me. > > Wedin That was addressed to me. What does `which ninja' output? -- Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From wedinm at gmail.com Wed May 6 15:30:35 2020 From: wedinm at gmail.com (M Wedin) Date: Wed, 6 May 2020 17:30:35 +0200 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: <20200506150003.GA8269@blackswan.r0t.uk> References: <20200506150003.GA8269@blackswan.r0t.uk> Message-ID: 2020-05-06 17:00 GMT+02:00, Dave Woodfall : > On 2020-05-06 14:27, > M Wedin put forth the proposition: >> > Have you changed the SlackBuild in any way? I saw a similar problem >> > recently while experimenting with the use of additional "system" >> > libraries (as opposed to using third party code included in the source >> > tarball). >> >> No. I haven't changed a single thing. I tried at first to update it >> with sboupgrade. But that failed instantly. So I downloaded the tar.gz >> from slackbuilds.org and the source for qt5 via slackbuilds.org. >> That's it. I ran ./qt5.SlackBuild without any options. >> >> > One thing that stands out is: >> >> -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 >> > >> > I don't think that standard is supported in the stock g++ supplied with >> > 14.2 is it? >> >> That's beyond me. >> >> Wedin > > That was addressed to me. > > What does `which ninja' output? This is from a different machine, but with the same set of software. I surmise the one at home would show exactly the same result. root at rick:~# which ninja /usr/bin/ninja root at rick:~# Wedin From slackbuilds at jaxartes.net Wed May 6 16:12:00 2020 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Wed, 6 May 2020 09:12:00 -0700 Subject: [Slackbuilds-users] bat: failed build (newer rust required?) In-Reply-To: <6a860ed3-8626-425e-a1bd-52c7aefb1a0b@www.fastmail.com> References: <6a860ed3-8626-425e-a1bd-52c7aefb1a0b@www.fastmail.com> Message-ID: On 2020-05-06 12:32 a.m., David O'Shaughnessy wrote: > On Tue, 5 May 2020, at 12:05 AM, Erich Ritz via SlackBuilds-users wrote: > > I don't know about 0.15.0, but the version on SBo (0.13.0) builds for me > on both -current and in 14.2. I'd test with the newer release, but the > .info file looks like it must take some automation to prepare! Yeah I have a horrible script that does all the .info updating for my rust scripts. I tried once by hand. Never again. I'm going to update the bat build to fix the build issue even if it's just downgrading to 0.13.0. Ben From chris.willing at linux.com Wed May 6 23:36:42 2020 From: chris.willing at linux.com (Christoph Willing) Date: Thu, 7 May 2020 09:36:42 +1000 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: <20200506053349.GH11324@blackswan.r0t.uk> References: <20200506053349.GH11324@blackswan.r0t.uk> Message-ID: On 6/5/20 3:33 pm, Dave Woodfall wrote: > On 2020-05-06 15:21, > Christoph Willing put forth the proposition: >> On 6/5/20 12:16 am, M Wedin wrote: >>> The old qt 5.9.9 was removed. >>> >>> I did have some stuff after the env check. So I exited root and logged >>> in again in the terminal window. The next check showed the following: >>> >>> # env | grep -i qt5 >>> PWD=/home/wed/slackpacks64_14.2/slackbuilds/qt5 >>> root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# >>> >>> Thus I ran the command >>> ./qt5.SlackBuild >>> >>> [641/2162] /usr/bin/g++ -MMD -MF >>> obj/content/browser/browser/save_package.o.d -DENABLE_SCREEN_CAPTURE=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 -DCONTENT_IMPLEMENTATION >>> -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -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\" >>> -DLEVELDB_PLATFORM_CHROMIUM=1 >>> -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH >>> -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX >>> -DMESA_EGL_NO_X11_HEADERS -DABSL_ALLOCATOR_NOTHROW=1 >>> -DNO_MAIN_THREAD_WRAPPING -DUSE_SYSTEM_ZLIB=1 -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 >>> -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/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/libwebm/source >>> -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out >>> -I../../3rdparty/chromium/third_party/leveldatabase >>> -I../../3rdparty/chromium/third_party/leveldatabase/src >>> -I../../3rdparty/chromium/third_party/leveldatabase/src/include >>> -I../../3rdparty/chromium/third_party/webrtc_overrides >>> -I../../3rdparty/chromium/testing/gtest/include >>> -I../../3rdparty/chromium/third_party/webrtc >>> -I../../3rdparty/chromium/third_party/webrtc_overrides >>> -I../../3rdparty/chromium/third_party/webrtc >>> -Igen/third_party/metrics_proto >>> -I../../3rdparty/chromium/third_party/boringssl/src/include >>> -I../../3rdparty/chromium/third_party/mesa/src/include >>> -I../../3rdparty/chromium/v8/include -Igen/v8/include >>> -I../../3rdparty/chromium/third_party/angle/src/common/third_party/base >>> -Igen/angle -I../../3rdparty/chromium/third_party/brotli/include >>> -I../../3rdparty/chromium/third_party/re2/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 -O2 -fno-ident >>> -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 >>> -fvisibility=hidden -isystem../../../../../../../usr/include/nss >>> -isystem../../../../../../../usr/include/nspr -isystem >>> ../../3rdparty/chromium/third_party/abseil-cpp >>> -isystem../../../../../../../usr/include/dbus-1.0 >>> -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 >>> -Wno-narrowing -Wno-attributes -Wno-class-memaccess >>> -Wno-subobject-linkage -fno-exceptions -fno-rtti >>> -fvisibility-inlines-hidden -c >>> ../../3rdparty/chromium/content/browser/download/save_package.cc -o >>> obj/content/browser/browser/save_package.o >>> ninja: build stopped: subcommand failed. >>> Makefile.gn_run:1151: recipe for target 'run_ninja' failed >>> make[4]: *** [run_ninja] Error 1 >>> make[4]: Leaving directory >>> '/tmp/SBo/qt-everywhere-src-5.12.8/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.8/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.8/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.8/qtwebengine' >>> Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed >>> make: *** [module-qtwebengine-make_first] Error 2 >>> root at headroom:/home/wed/slackpacks64_14.2/slackbuilds/qt5# >>> >> >> Have you changed the SlackBuild in any way? I saw a similar problem >> recently while experimenting with the use of additional "system" >> libraries (as opposed to using third party code included in the source >> tarball). >> >> One thing that stands out is: >>> -isystem../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 >> >> I don't think that standard is supported in the stock g++ supplied with >> 14.2 is it? >> >> Sorry I don't recall exactly which additional system package triggered >> that particular error. It may have been ffmpeg because that was >> definitely one system package that I couldn't integrate into the qt5 >> build at all. However I"m not sure if that failure was the one >> associated with the c++14 and subsequent meson error. >> >> Good luck, >> chris > > Yes, the 5.9.x slackbuild used c++11 explicitly, because > (python3-)PyQt5 wouldn't build without it. I noticed that it wasn't > needed after updating PyQt5, and that it built fine without it so I > removed it. > > It has been commented on before, and I wasn't sure whether to add it > back in or not. I guess it won't hurt to take it down a few pegs. > I did a rebuild overnight to make sure everything is still working and kept a log. Unfortunately, no magical insights from it though. However, it looks like the c++14 thing was a red herring - I see plenty of references to it (including checking for its capability). I noticed that ninja itself (version, whatever) is probably not implicated; the configuration finds the system ninja to be too old and doesn't use it: Checking for system ninja... Found ninja from path: /usr/bin/ninja + /usr/bin/ninja --version > 1.10.0 Ninja version too old Building own ninja I also found the area where OP's build failed. No failure here but it is interesting that the progress indicator was quite different. In my build it was [15020/16427] but for OP it was [641/2162]. I wonder if that means different things are being built - leading to question of what the configuration discovered on the build machine (therefore determining what needed to be built). My build was on a clean, up to date, VM - nothing else installed except the required ninja, python3, meson & libxkbcommon packages. A question for Wedin: did you have those packages installed before starting build of qt5? Also, any other packages installed that may have influenced qt5's build configuration (some are listed in the qt5.README file)? 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 ardutu at gmail.com Fri May 8 07:43:04 2020 From: ardutu at gmail.com (ilmich) Date: Fri, 8 May 2020 09:43:04 +0200 Subject: [Slackbuilds-users] Outdated openconnect slackbuilds Message-ID: Hi all, after an infrastructure update, the vpn of my company does not work anymore with the openconnect version of slackbuild. Instead with the latest version (8.09) it works. It's possible an upgrade of version?! Thanks in advance Michele -------------- next part -------------- An HTML attachment was scrubbed... URL: From majek at w7i.pl Fri May 8 09:30:40 2020 From: majek at w7i.pl (Marek Wodzinski) Date: Fri, 8 May 2020 11:30:40 +0200 (CEST) Subject: [Slackbuilds-users] Outdated openconnect slackbuilds In-Reply-To: References: Message-ID: On Fri, 8 May 2020, ilmich wrote: > Hi all, after an infrastructure update, the vpn of my company does not work anymore with the openconnect version of > slackbuild. Instead with the latest version (8.09) it works. It's possible an upgrade of version?! Thanks in advance I sent e-mail to Robby 2 weeks ago about it, but I didn't get any response. I also offered maintaing it if Robby don't want or can't do it anymore. Robby? Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg From rworkman at slackbuilds.org Fri May 8 17:58:34 2020 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 8 May 2020 12:58:34 -0500 Subject: [Slackbuilds-users] Outdated openconnect slackbuilds In-Reply-To: References: Message-ID: <20200508125834.6052d5b0@home.rlworkman.net> On Fri, 8 May 2020 11:30:40 +0200 (CEST) Marek Wodzinski wrote: > On Fri, 8 May 2020, ilmich wrote: > > > Hi all, after an infrastructure update, the vpn of my company does > > not work anymore with the openconnect version of slackbuild. > > Instead with the latest version (8.09) it works. It's possible an > > upgrade of version?! Thanks in advance > > I sent e-mail to Robby 2 weeks ago about it, but I didn't get any > response. > I also offered maintaing it if Robby don't want or can't do it > anymore. > > Robby? Sorry; I mentally replied, but apparently it didn't go any farther. They're all yours. :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From majek at w7i.pl Fri May 8 19:16:11 2020 From: majek at w7i.pl (Marek Wodzinski) Date: Fri, 8 May 2020 21:16:11 +0200 (CEST) Subject: [Slackbuilds-users] Outdated openconnect slackbuilds In-Reply-To: <20200508125834.6052d5b0@home.rlworkman.net> References: <20200508125834.6052d5b0@home.rlworkman.net> Message-ID: On Fri, 8 May 2020, Robby Workman wrote: >> I also offered maintaing it if Robby don't want or can't do it >> anymore. >> >> Robby? > > Sorry; I mentally replied, but apparently it didn't go any farther. Busy life :-) No problem. > They're all yours. :-) Thank you. I submited PR on Github for openconnect. But there are also NetworkManager-openconnect and plasma-nm-openconnect. I don't use any of these, I don't even use NM or KDE, so I'm not the best person to get them. I know, it's not very good situation to not get all three, but at least Michele, I and maybe others will get up-to-date openconnect package. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg From artourter at gmail.com Sat May 9 17:04:53 2020 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 9 May 2020 18:04:53 +0100 Subject: [Slackbuilds-users] netcdf package update In-Reply-To: References: Message-ID: Hi, Any admin with opinions on this? I still haven't received anything back from David. Cheers Greg On Sun, 26 Apr 2020 at 18:46, Greg' Ar Tourter wrote: > 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 willysr at slackbuilds.org Sat May 9 17:17:52 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 10 May 2020 00:17:52 +0700 Subject: [Slackbuilds-users] netcdf package update In-Reply-To: References: Message-ID: > Any admin with opinions on this? I still haven't received anything back > from David. >> 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. David is dealing with personal issue, so he may not be around for a while. As of netcdf, i think it's ok to bump this package with a simple condition that every package that depends on netcdf must be tested to avoid breakage. So far, i can only see GMT, grace, nco, and ncview If you can test them before sending the update, it would be much appreciated. -- 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 artourter at gmail.com Sat May 9 17:25:36 2020 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 9 May 2020 18:25:36 +0100 Subject: [Slackbuilds-users] netcdf package update In-Reply-To: References: Message-ID: Thanks Willy, I wish David the best. I have tested nco (which I maintain) and ncview. I will test grace and GMT and proceed accordingly. Cheers Greg On Sat, 9 May 2020 at 18:18, Willy Sudiarto Raharjo wrote: > > Any admin with opinions on this? I still haven't received anything back > > from David. > > >> 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. > > David is dealing with personal issue, so he may not be around for a while. > > As of netcdf, i think it's ok to bump this package with a simple > condition that every package that depends on netcdf must be tested to > avoid breakage. > > So far, i can only see GMT, grace, nco, and ncview > If you can test them before sending the update, it would be much > appreciated. > > > -- > 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 slackbuilds at jaxartes.net Sat May 9 17:27:29 2020 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 09 May 2020 10:27:29 -0700 Subject: [Slackbuilds-users] netcdf package update In-Reply-To: References: Message-ID: <2637636.DJkKcVGEfx@wintermute.sprawl.net> Could you send over the updated script (or point to a git commit) and I'll test gdal which optionally depends on netcdf? Thanks, Ben On Saturday, 9 May 2020 10:25:36 PDT Greg' Ar Tourter wrote: > Thanks Willy, I wish David the best. > > I have tested nco (which I maintain) and ncview. I will test grace and GMT > and proceed accordingly. > > Cheers > > Greg > > On Sat, 9 May 2020 at 18:18, Willy Sudiarto Raharjo > > wrote: > > > Any admin with opinions on this? I still haven't received anything back > > > from David. > > > > > >> 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. > > > > David is dealing with personal issue, so he may not be around for a while. > > > > As of netcdf, i think it's ok to bump this package with a simple > > condition that every package that depends on netcdf must be tested to > > avoid breakage. > > > > So far, i can only see GMT, grace, nco, and ncview > > If you can test them before sending the update, it would be much > > appreciated. > > > > > > -- > > 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 artourter at gmail.com Sat May 9 21:45:19 2020 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 9 May 2020 22:45:19 +0100 Subject: [Slackbuilds-users] netcdf package update In-Reply-To: References: Message-ID: Hi, Grace compiles fine but GMT's slackbuilds is not correct since 'make docs_man' and 'make docs_html' are not valid make targets. additionally, -DLIB_SUFFIX is not a valid cmake option (although that doesn't stop it to compile. Once the two make commands are removed from the scripts, it compiles fine. I also compiled gdal since I needed it as a requirement for GMT and it automatically picked up netcdf and compiled ok. I attach the new slackbuild if you want to test it more extensively. Note that CDF5 is now enabled by default as the bug affecting 32 bit install was fixed. I would probably remove the option to disable it altogether but for now I have set it to default to yes and if for some reason one wants to disable CDF5, one had to set CDF5=no but it is likely to cause more issue than it is to solve. Let me know if you are happy with it and I'll update the README file and submit it. Cheers Greg On Sat, 9 May 2020 at 18:25, Greg' Ar Tourter wrote: > Thanks Willy, I wish David the best. > > I have tested nco (which I maintain) and ncview. I will test grace and GMT > and proceed accordingly. > > Cheers > > Greg > > On Sat, 9 May 2020 at 18:18, Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> > Any admin with opinions on this? I still haven't received anything back >> > from David. >> >> >> 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. >> >> David is dealing with personal issue, so he may not be around for a while. >> >> As of netcdf, i think it's ok to bump this package with a simple >> condition that every package that depends on netcdf must be tested to >> avoid breakage. >> >> So far, i can only see GMT, grace, nco, and ncview >> If you can test them before sending the update, it would be much >> appreciated. >> >> >> -- >> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: netcdf.tar.gz Type: application/gzip Size: 2999 bytes Desc: not available URL: From slackbuilds at jaxartes.net Sat May 9 21:56:58 2020 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 09 May 2020 14:56:58 -0700 Subject: [Slackbuilds-users] netcdf package update In-Reply-To: References: Message-ID: <1761764.LH7GnMWURc@wintermute.sprawl.net> On Saturday, 9 May 2020 14:45:19 PDT Greg' Ar Tourter wrote: > > I also compiled gdal since I needed it as a requirement for GMT and it > automatically picked up netcdf and compiled ok. Thanks for checking GDAL! From willysr at slackbuilds.org Sun May 10 02:00:45 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 10 May 2020 09:00:45 +0700 Subject: [Slackbuilds-users] Updates - 20200510.1 Message-ID: <28f1720a-c079-2611-6863-3a0b26272f70@slackbuilds.org> Sun May 10 01:38:26 UTC 2020 academic/biblesync: Fix pkg-config. academic/chartgeany: Added (market analysis tool) academic/cryptominisat: Updated for version 5.7.1. academic/freechartgeany: Removed academic/gcompris-qt: Added (an educational software suite) academic/libqalculate: Updated for version 3.9.0a academic/mpb: Added (computing electromagnetic band). academic/qalculate-gtk: Updated for version 3.9.0a academic/sage: Fix post-installation path. academic/sword: Add patch to fix formatting. audio/qmmp-plugin-pack: Updated for version 0.12.2. audio/qmmp: Updated for version 0.12.7. desktop/bukubrow: Updated for version 5.1.0. desktop/simplenote: Updated for version 1.16.0. development/cmocka: Updated for version 6.5.2. development/jdk11: Fix shebang. development/jdk12: Fix shebang. development/jdk13: Fix shebang. development/jdk14: Fix shebang. development/libb2: Updated for version 0.98.1. development/nodejs: Updated for version 12.16.3. development/robotframework: Updated for version 3.2.1. development/spin: Updated for version 6.5.2. games/fceux: Fix build with scons. games/onscripter: Updated for version 20200419. gis/cartopy: Updated for version 0.18.0. gis/qgis: Updated for version 3.12.2. graphics/brlcad: updated for version 7.30.8 ham/ax25-apps: Added (AX.25 Packet radio support software). ham/ax25-tools: Added (AX.25 Packet radio supporting tools). ham/libax25: Added (AX.25 Packet radio support for linux). libraries/SDL_kitchensink: updated for version 1.0.8 libraries/VTK: Note VTK-8.2.0 is last suitable version for SL-14.2 libraries/hoel: updated for version 1.4.16 libraries/http-parser: Updated for version 2.9.4 libraries/podofo: Updated for version 0.9.6 libraries/zziplib: Updated for version 0.13.71 misc/KeePass: Updated for version 2.45. multimedia/dvdbackup: Fix name. multimedia/k9copy-reloaded: Fix path. multimedia/lives: Fix email. multimedia/plexmediaserver: Updated for v 1.19.3.2764_ef515a800. network/asterisk: Updated for version 16.10.0. network/bluejeans: Fix shebang. network/openconnect: Updated for version 8.09 + new maintainer. network/pexip-infinity-connect: Fix shebang. network/prosody-mod-cloud-notify: Updated for version hg3996. network/prosody-mod-smacks: Updated for version hg4009. network/qutebrowser-tox: Updated for version 1.11.1. network/slimjet: Updated for version 26.0.5.0. network/telegram: Updated for version 2.1.2. network/telegram: Updated for version 2.1.4. network/tor-browser: Updated for version 9.0.10. network/vivaldi: Updated for version 3.0.1874.38. network/wireguard-linux-compat: Updated for version 1.0.20200506. network/zeek: Updated for version 3.0.5. office/gnucash-legacy-docs: Update email. office/gnucash-legacy: Update README. office/gnucash: Update README. office/texmaker: Updated for version 5.0.4 office/texstudio: Updated for version 2.12.22 office/timew: Updated for version 1.3.0. office/when: Added (an extremely simple personal calendar program) perl/MoarVM: Updated for version 2020.05. perl/nqp: Updated for version 2020.05. perl/perl-Net-ARP: Updated for version 1.0.11. perl/rakudo: Updated for version 2020.05. perl/zef: Updated for version 0.8.4. python/python3-astroid: Updated for version 2.4.0. python/python3-ipython: Updated for version 7.14.0. python/python3-pylint: Updated for version 2.5.0. system/bat: Revert to version 0.13.0. system/ccd2cue: Added (convert CloneCD images to bin/cue) system/chronograf: Updated for version 1.8.4. system/crc32_simple: Added (calculate crc32 checksum of files) system/dosbox-x: Updated for version 0.98.1. system/mksh: Updated for version R59. system/nvidia-driver: Update script. system/nvidia-legacy390-driver: Update script. system/osquery-bin: Added (OS instrumentation framework) system/ripgrep: Updated for version 12.1.0. system/skopeo: Updated to version 0.2.0. system/sleuthkit: Updated for version 4.9.0. system/telegraf: Updated for version 1.14.2. +--------------------------+ -- 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 artourter at gmail.com Sun May 10 02:02:09 2020 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sun, 10 May 2020 03:02:09 +0100 Subject: [Slackbuilds-users] Updates - 20200510.1 In-Reply-To: <28f1720a-c079-2611-6863-3a0b26272f70@slackbuilds.org> References: <28f1720a-c079-2611-6863-3a0b26272f70@slackbuilds.org> Message-ID: Willy, What happened to the netcdf update? was there something wrong? On Sun, 10 May 2020 at 03:00, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Sun May 10 01:38:26 UTC 2020 > academic/biblesync: Fix pkg-config. > academic/chartgeany: Added (market analysis tool) > academic/cryptominisat: Updated for version 5.7.1. > academic/freechartgeany: Removed > academic/gcompris-qt: Added (an educational software suite) > academic/libqalculate: Updated for version 3.9.0a > academic/mpb: Added (computing electromagnetic band). > academic/qalculate-gtk: Updated for version 3.9.0a > academic/sage: Fix post-installation path. > academic/sword: Add patch to fix formatting. > audio/qmmp-plugin-pack: Updated for version 0.12.2. > audio/qmmp: Updated for version 0.12.7. > desktop/bukubrow: Updated for version 5.1.0. > desktop/simplenote: Updated for version 1.16.0. > development/cmocka: Updated for version 6.5.2. > development/jdk11: Fix shebang. > development/jdk12: Fix shebang. > development/jdk13: Fix shebang. > development/jdk14: Fix shebang. > development/libb2: Updated for version 0.98.1. > development/nodejs: Updated for version 12.16.3. > development/robotframework: Updated for version 3.2.1. > development/spin: Updated for version 6.5.2. > games/fceux: Fix build with scons. > games/onscripter: Updated for version 20200419. > gis/cartopy: Updated for version 0.18.0. > gis/qgis: Updated for version 3.12.2. > graphics/brlcad: updated for version 7.30.8 > ham/ax25-apps: Added (AX.25 Packet radio support software). > ham/ax25-tools: Added (AX.25 Packet radio supporting tools). > ham/libax25: Added (AX.25 Packet radio support for linux). > libraries/SDL_kitchensink: updated for version 1.0.8 > libraries/VTK: Note VTK-8.2.0 is last suitable version for SL-14.2 > libraries/hoel: updated for version 1.4.16 > libraries/http-parser: Updated for version 2.9.4 > libraries/podofo: Updated for version 0.9.6 > libraries/zziplib: Updated for version 0.13.71 > misc/KeePass: Updated for version 2.45. > multimedia/dvdbackup: Fix name. > multimedia/k9copy-reloaded: Fix path. > multimedia/lives: Fix email. > multimedia/plexmediaserver: Updated for v 1.19.3.2764_ef515a800. > network/asterisk: Updated for version 16.10.0. > network/bluejeans: Fix shebang. > network/openconnect: Updated for version 8.09 + new maintainer. > network/pexip-infinity-connect: Fix shebang. > network/prosody-mod-cloud-notify: Updated for version hg3996. > network/prosody-mod-smacks: Updated for version hg4009. > network/qutebrowser-tox: Updated for version 1.11.1. > network/slimjet: Updated for version 26.0.5.0. > network/telegram: Updated for version 2.1.2. > network/telegram: Updated for version 2.1.4. > network/tor-browser: Updated for version 9.0.10. > network/vivaldi: Updated for version 3.0.1874.38. > network/wireguard-linux-compat: Updated for version 1.0.20200506. > network/zeek: Updated for version 3.0.5. > office/gnucash-legacy-docs: Update email. > office/gnucash-legacy: Update README. > office/gnucash: Update README. > office/texmaker: Updated for version 5.0.4 > office/texstudio: Updated for version 2.12.22 > office/timew: Updated for version 1.3.0. > office/when: Added (an extremely simple personal calendar program) > perl/MoarVM: Updated for version 2020.05. > perl/nqp: Updated for version 2020.05. > perl/perl-Net-ARP: Updated for version 1.0.11. > perl/rakudo: Updated for version 2020.05. > perl/zef: Updated for version 0.8.4. > python/python3-astroid: Updated for version 2.4.0. > python/python3-ipython: Updated for version 7.14.0. > python/python3-pylint: Updated for version 2.5.0. > system/bat: Revert to version 0.13.0. > system/ccd2cue: Added (convert CloneCD images to bin/cue) > system/chronograf: Updated for version 1.8.4. > system/crc32_simple: Added (calculate crc32 checksum of files) > system/dosbox-x: Updated for version 0.98.1. > system/mksh: Updated for version R59. > system/nvidia-driver: Update script. > system/nvidia-legacy390-driver: Update script. > system/osquery-bin: Added (OS instrumentation framework) > system/ripgrep: Updated for version 12.1.0. > system/skopeo: Updated to version 0.2.0. > system/sleuthkit: Updated for version 4.9.0. > system/telegraf: Updated for version 1.14.2. > +--------------------------+ > > > -- > 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 Sun May 10 02:32:28 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 10 May 2020 09:32:28 +0700 Subject: [Slackbuilds-users] Updates - 20200510.1 In-Reply-To: References: <28f1720a-c079-2611-6863-3a0b26272f70@slackbuilds.org> Message-ID: > Willy, What happened to the netcdf update? was there something wrong? Sorry, i forgot to push it from my build machine along with 2 other submissions, so it didn't get merged into this week's public update. I have it on my branch now, so it will be part of next week's public update. This will also gives time to check other scripts that depends on netcdf and GDAL. -- 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 gerardo.zamudio at linux.com Sun May 10 04:57:13 2020 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sat, 09 May 2020 23:57:13 -0500 Subject: [Slackbuilds-users] update openfortivpn Message-ID: Hi Antonio, I want to submit a SlackBuild for NetworkManager-fortisslvpn, but this requires openfortivpn 1.10+. The latest at the moment is version 1.13.3. Can you update your SlackBuild to this version or at least 1.10? I have tested both here on Slackware64 14.2 and -current and they work. I see your latest update was in 2016 If you are unable to update, I can gladly take over the SlackBuild since I need both of these for work. Regards, Gerardo Zamudio From willysr at slackbuilds.org Sun May 10 07:10:26 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 10 May 2020 14:10:26 +0700 Subject: [Slackbuilds-users] Error building codelite-14.0 In-Reply-To: <010adcb6-45de-f388-ab78-e51e20a0baca@gmail.com> References: <010adcb6-45de-f388-ab78-e51e20a0baca@gmail.com> Message-ID: > 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? It's now fixed on my branch the patch need some adjustment for Slackware as it uses newer version of libssh compared to Ubuntu/Debian. -- 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 Sun May 10 17:44:45 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 10 May 2020 11:44:45 -0600 Subject: [Slackbuilds-users] Latest nodejs not building Message-ID: g++ -o /tmp/sbopkg.uWewFs/node-v12.16.3/out/Release/obj.target/torque_base/deps/v8/src/torque/cfg.o ../deps/v8/src/torque/cfg.cc '-DV8_GYP_BUILD' '-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64' '-D__STDC_FORMAT_MACROS' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DV8_TARGET_ARCH_X64' '-DV8_EMBEDDER_STRING="-node.35"' '-DENABLE_DISASSEMBLER' '-DV8_PROMISE_INTERNAL_FIELD_COUNT=1' '-DENABLE_MINOR_MC' '-DV8_INTL_SUPPORT' '-DV8_USE_SNAPSHOT' '-DV8_CONCURRENT_MARKING' '-DV8_ENABLE_LAZY_SOURCE_POSITIONS' '-DV8_EMBEDDED_BUILTINS' '-DV8_USE_SIPHASH' '-DDISABLE_UNTRUSTED_CODE_MITIGATIONS' '-DV8_WIN64_UNWINDING_INFO' '-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH' -I../deps/v8 -I../deps/v8/include -pthread -Wno-unused-parameter -m64 -Wno-return-type -fno-strict-aliasing -m64 -O3 -fno-omit-frame-pointer -fdata-sections -ffunction-sections -O3 -fno-rtti -std=gnu++1y -fexceptions -MMD -MF /tmp/sbopkg.uWewFs/node-v12.16.3/out/Release/.deps//tmp/sbopkg.uWewFs/node-v12.16.3/out/Release/obj.target/torque_base/deps/v8/src/torque/cfg.o.d.raw -O2 -fPIC -c In file included from ../deps/v8/src/torque/cfg.h:13:0, from ../deps/v8/src/torque/cfg.cc:5: ../deps/v8/src/torque/ast.h: In static member function 'static v8::internal::torque::ParameterList v8::internal::torque::ParameterList::Empty()': ../deps/v8/src/torque/ast.h:573:42: error: could not convert '()' from '' to 'v8::internal::torque::ParameterList' static ParameterList Empty() { return {}; } ^ tools/v8_gypfiles/torque_base.target.mk:148: recipe for target '/tmp/sbopkg.uWewFs/node-v12.16.3/out/Release/obj.target/torque_base/deps/v8/src/torque/cfg.o' failed make[1]: *** [/tmp/sbopkg.uWewFs/node-v12.16.3/out/Release/obj.target/torque_base/deps/v8/src/torque/cfg.o] Error 1 Makefile:101: recipe for target 'node' failed make: *** [node] Error 2 Cleaning up... -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun May 10 18:14:51 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 11 May 2020 01:14:51 +0700 Subject: [Slackbuilds-users] Latest nodejs not building In-Reply-To: References: Message-ID: > g++ -o Did you try using su or "su -" ? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From 1.41421 at gmail.com Sun May 10 18:18:38 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 10 May 2020 12:18:38 -0600 Subject: [Slackbuilds-users] Latest nodejs not building In-Reply-To: References: Message-ID: I did use su - On Sun, May 10, 2020 at 12:15 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > g++ -o > > Did you try using su or "su -" ? > > -- > 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 matteo.bernardini at gmail.com Sun May 10 18:30:33 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 10 May 2020 20:30:33 +0200 Subject: [Slackbuilds-users] Latest nodejs not building In-Reply-To: References: Message-ID: FWIW I can confirm that it built fine here on my slackware64-14.2. Il giorno dom 10 mag 2020 alle ore 20:18 Luveh Keraph <1.41421 at gmail.com> ha scritto: > > I did use su - > > > On Sun, May 10, 2020 at 12:15 PM Willy Sudiarto Raharjo wrote: >> >> > g++ -o >> >> Did you try using su or "su -" ? >> >> -- >> 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/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From 1.41421 at gmail.com Sun May 10 21:22:03 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 10 May 2020 15:22:03 -0600 Subject: [Slackbuilds-users] Latest nodejs not building In-Reply-To: References: Message-ID: Got it to build. The problem was that in that system I had version 5.3.0 of the Gnu compiler tools. Once I upgraded to version 5.5.0 the build proceeded without any issues. On Sun, May 10, 2020 at 12:30 PM Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > FWIW I can confirm that it built fine here on my slackware64-14.2. > > Il giorno dom 10 mag 2020 alle ore 20:18 Luveh Keraph > <1.41421 at gmail.com> ha scritto: > > > > I did use su - > > > > > > On Sun, May 10, 2020 at 12:15 PM Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> > >> > g++ -o > >> > >> Did you try using su or "su -" ? > >> > >> -- > >> 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/ > >> > > _______________________________________________ > > 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 lenardrspencer at gmail.com Sun May 10 23:45:59 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 10 May 2020 19:45:59 -0400 Subject: [Slackbuilds-users] Latest nodejs not building In-Reply-To: References: Message-ID: FYI, it built fine here with 'su -', haven't tried with just 'su'. On Sun, May 10, 2020, 14:15 Willy Sudiarto Raharjo wrote: > > g++ -o > > Did you try using su or "su -" ? > > -- > 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 lenardrspencer at gmail.com Sun May 10 23:48:18 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 10 May 2020 19:48:18 -0400 Subject: [Slackbuilds-users] Latest nodejs not building In-Reply-To: References: Message-ID: oops, let ne qualify that. It built fine on current, tring 14.2 now. On Sun, May 10, 2020, 14:15 Willy Sudiarto Raharjo wrote: > > g++ -o > > Did you try using su or "su -" ? > > -- > 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 lenardrspencer at gmail.com Mon May 11 01:04:23 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 10 May 2020 21:04:23 -0400 Subject: [Slackbuilds-users] Latest nodejs not building In-Reply-To: References: Message-ID: I was able to build it both with 'su' and 'su -', but i did notice it threw warnings (NOT errors) about gcc being too old. This is on a clean 14.2 install partition (not a vm). Hope this helps. On Sun, May 10, 2020, 19:48 Lenard Spencer wrote: > oops, let ne qualify that. It built fine on current, tring 14.2 now. > > On Sun, May 10, 2020, 14:15 Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> > g++ -o >> >> Did you try using su or "su -" ? >> >> -- >> 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 falsetti at clansco.org Mon May 11 10:16:14 2020 From: falsetti at clansco.org (=?UTF-8?B?RnLDqWTDqXJpYw==?= Falsetti) Date: Mon, 11 May 2020 12:16:14 +0200 Subject: [Slackbuilds-users] vlc-3.0.10 Message-ID: <20200511121614.b3d51f5c177c8a3a96654780@clansco.org> Hi, vlc-3.0.10 fails to build /tmp/SBo/vlc-3.0.10/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv I have VTK-8.2.0-i486-1_SBo opencv-4.3.0-i586-1_SBo Making all in bin make[2]?: on entre dans le r?pertoire ??/tmp/SBo/vlc-3.0.10/bin?? CC vlc-vlc.o CC vlc-override.o CCLD vlc CC rootwrap.o rootwrap.c: Dans la fonction ?main?: rootwrap.c:251:5: attention : ignoring return value of ?setuid?, declared with attribute warn_unused_result [-Wunused-result] setuid (uid); ^ CCLD vlc-wrapper CC vlc_static-vlc.o CC vlc_static-override.o CCLD vlc-static CC cachegen.o CCLD vlc-cache-gen GEN ../modules/plugins.dat /tmp/SBo/vlc-3.0.10/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv Makefile:1795?: la recette pour la cible ??../modules/plugins.dat?? a ?chou?e make[2]: *** [../modules/plugins.dat] Erreur 127 make[2]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.10/bin?? Makefile:1556?: la recette pour la cible ??all-recursive?? a ?chou?e make[1]: *** [all-recursive] Erreur 1 make[1]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.10?? Makefile:1441?: la recette pour la cible ??all?? a ?chou?e make: *** [all] Erreur 2 From chris.willing at linux.com Mon May 11 11:28:48 2020 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 11 May 2020 21:28:48 +1000 Subject: [Slackbuilds-users] vlc-3.0.10 In-Reply-To: <20200511121614.b3d51f5c177c8a3a96654780@clansco.org> References: <20200511121614.b3d51f5c177c8a3a96654780@clansco.org> Message-ID: On 11/5/20 8:16 pm, Fr?d?ric Falsetti wrote: > Hi, > vlc-3.0.10 fails to build > > /tmp/SBo/vlc-3.0.10/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv > > I have VTK-8.2.0-i486-1_SBo > opencv-4.3.0-i586-1_SBo > > Making all in bin > make[2]?: on entre dans le r?pertoire ??/tmp/SBo/vlc-3.0.10/bin?? > CC vlc-vlc.o > CC vlc-override.o > CCLD vlc > CC rootwrap.o > rootwrap.c: Dans la fonction ?main?: > rootwrap.c:251:5: attention : ignoring return value of ?setuid?, declared with attribute warn_unused_result [-Wunused-result] > setuid (uid); > ^ > CCLD vlc-wrapper > CC vlc_static-vlc.o > CC vlc_static-override.o > CCLD vlc-static > CC cachegen.o > CCLD vlc-cache-gen > GEN ../modules/plugins.dat > /tmp/SBo/vlc-3.0.10/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv > Makefile:1795?: la recette pour la cible ??../modules/plugins.dat?? a ?chou?e > make[2]: *** [../modules/plugins.dat] Erreur 127 > make[2]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.10/bin?? > Makefile:1556?: la recette pour la cible ??all-recursive?? a ?chou?e > make[1]: *** [all-recursive] Erreur 1 > make[1]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.10?? > Makefile:1441?: la recette pour la cible ??all?? a ?chou?e > make: *** [all] Erreur 2 > I think this is a problem with your VTK build. I just built the 32bit version to check this in a clean VM and found that the /usr/lib/libvtkCommonExecutionModel.so.1 file definitely _does_ contain the _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv symbol - so shouldn't be a problem for building vlc. chris From chris.willing at linux.com Mon May 11 13:31:43 2020 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 11 May 2020 23:31:43 +1000 Subject: [Slackbuilds-users] vlc-3.0.10 In-Reply-To: References: <20200511121614.b3d51f5c177c8a3a96654780@clansco.org> Message-ID: On 11/5/20 9:28 pm, Christoph Willing wrote: > On 11/5/20 8:16 pm, Fr?d?ric Falsetti wrote: >> Hi, >> vlc-3.0.10 fails to build >> >> /tmp/SBo/vlc-3.0.10/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv >> >> I have VTK-8.2.0-i486-1_SBo >> opencv-4.3.0-i586-1_SBo >> >> Making all in bin >> make[2]?: on entre dans le r?pertoire ??/tmp/SBo/vlc-3.0.10/bin?? >> CC vlc-vlc.o >> CC vlc-override.o >> CCLD vlc >> CC rootwrap.o >> rootwrap.c: Dans la fonction ?main?: >> rootwrap.c:251:5: attention : ignoring return value of ?setuid?, declared with attribute warn_unused_result [-Wunused-result] >> setuid (uid); >> ^ >> CCLD vlc-wrapper >> CC vlc_static-vlc.o >> CC vlc_static-override.o >> CCLD vlc-static >> CC cachegen.o >> CCLD vlc-cache-gen >> GEN ../modules/plugins.dat >> /tmp/SBo/vlc-3.0.10/bin/.libs/lt-vlc-cache-gen: symbol lookup error: /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv >> Makefile:1795?: la recette pour la cible ??../modules/plugins.dat?? a ?chou?e >> make[2]: *** [../modules/plugins.dat] Erreur 127 >> make[2]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.10/bin?? >> Makefile:1556?: la recette pour la cible ??all-recursive?? a ?chou?e >> make[1]: *** [all-recursive] Erreur 1 >> make[1]?: on quitte le r?pertoire ??/tmp/SBo/vlc-3.0.10?? >> Makefile:1441?: la recette pour la cible ??all?? a ?chou?e >> make: *** [all] Erreur 2 >> > > I think this is a problem with your VTK build. I just built the 32bit > version to check this in a clean VM and found that the > /usr/lib/libvtkCommonExecutionModel.so.1 file definitely _does_ contain > the _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv symbol - so > shouldn't be a problem for building vlc. > After building opencv in the same VM (so VTK is detected & used) and then building vlc, build log shows: Making all in bin make[2]: Entering directory '/var/tmp/SBo/vlc-3.0.10/bin' CC vlc-vlc.o CC rootwrap.o CC cachegen.o CC vlc-override.o CC vlc_static-vlc.o CC vlc_static-override.o rootwrap.c: In function 'main': rootwrap.c:251:5: warning: ignoring return value of 'setuid', declared with attribute warn_unused_result [-Wunused-result] setuid (uid); ^ CCLD vlc-cache-gen CCLD vlc-wrapper CCLD vlc CCLD vlc-static GEN ../modules/plugins.dat make[2]: Leaving directory '/var/tmp/SBo/vlc-3.0.10/bin' Making all in test ... ... i.e. no problem building 32bit vlc with VTK & opencv support. I suggest you rebuild VTK (perhaps it would be good to remove existing VTK first) and check for the "missing" symbol by running: strings /usr/lib/libvtkCommonExecutionModel.so.1 | grep _ZN33 and look for the symbol in the output. If the symbol is listed (as it should be) then go on to rebuild opencv (so it's built against a correctly working VTK), then try building vlc again. chris From erich.public at protonmail.com Mon May 11 15:51:50 2020 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 11 May 2020 15:51:50 +0000 Subject: [Slackbuilds-users] nodejs md5sum Message-ID: ??????? Original Message ??????? On Saturday, May 9, 2020 7:00 PM, Willy Sudiarto Raharjo wrote: > Sun May 10 01:38:26 UTC 2020 > development/nodejs: Updated for version 12.16.3. Hi Willy, Download link for nodejs points to the .tar.xz file, but the md5sum given in the .info file is for the .tar.gz file: $ md5sum node-v12.16.3.tar.* 8977bcdb78c5ea63544e57115aeff8d8 node-v12.16.3.tar.gz 3f23ba05c01f6f03170059057a7bd727 node-v12.16.3.tar.xz Erich From willysr at slackbuilds.org Mon May 11 17:16:04 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 12 May 2020 00:16:04 +0700 Subject: [Slackbuilds-users] nodejs md5sum In-Reply-To: References: Message-ID: > Download link for nodejs points to the .tar.xz file, but the md5sum given in the .info file is for the .tar.gz file: > > $ md5sum node-v12.16.3.tar.* > 8977bcdb78c5ea63544e57115aeff8d8 node-v12.16.3.tar.gz > 3f23ba05c01f6f03170059057a7bd727 node-v12.16.3.tar.xz Yeah, i fixed it already in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From larryhaja at gmail.com Tue May 12 13:11:24 2020 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 12 May 2020 06:11:24 -0700 Subject: [Slackbuilds-users] I failed to build qt5 In-Reply-To: References: <20200506053349.GH11324@blackswan.r0t.uk> Message-ID: > > I did a rebuild overnight to make sure everything is still working and > kept a log. Unfortunately, no magical insights from it though. > > However, it looks like the c++14 thing was a red herring - I see plenty > of references to it (including checking for its capability). > Yeah, I don't believe this is an issue. > I noticed that ninja itself (version, whatever) is probably not > implicated; the configuration finds the system ninja to be too old and > doesn't use it: > > Checking for system ninja... > Found ninja from path: /usr/bin/ninja > + /usr/bin/ninja --version > > 1.10.0 > Ninja version too old > Building own ninja > The upstream qtwebengine repo has a patch that hasn't been back ported it to a version > 5.12.8 in the 5.12.x branch, which adds logic to pick up ninja version >= 1.10.x. https://github.com/qt/qtwebengine/commit/8c1a4841174a90299ba2e2851b4d9e79da3b9b25 Patch attached to pick up newer ninja version. I also found the area where OP's build failed. No failure here but it is > interesting that the progress indicator was quite different. In my build > it was [15020/16427] but for OP it was [641/2162]. I wonder if that > means different things are being built - leading to question of what the > configuration discovered on the build machine (therefore determining > what needed to be built). > Same. Mine failed on [116/2525]. Looking up farther in the build output I saw the following lines. FAILED: obj/third_party/blink/renderer/core/core/core_initializer.o ...... virtual memory exhausted: Cannot allocate memory > My build was on a clean, up to date, VM - nothing else installed except > the required ninja, python3, meson & libxkbcommon packages. > Same. Original VM had 4GB of RAM and no swap. I increased it to 8GB of RAM and that succeeded in less than half the time it took to fail on 4GB of RAM. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: qt5.SlackBuild.diff Type: application/octet-stream Size: 472 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ninja-1.10.patch Type: application/x-patch Size: 925 bytes Desc: not available URL: From falsetti at clansco.org Tue May 12 14:11:19 2020 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Tue, 12 May 2020 16:11:19 +0200 Subject: [Slackbuilds-users] vlc-3.0.10 In-Reply-To: References: <20200511121614.b3d51f5c177c8a3a96654780@clansco.org> Message-ID: <20200512161119.6dd251f870b5a700e5684664@clansco.org> le Mon, 11 May 2020 23:31:43 +1000 Christoph Willing a ?crit : > I suggest you rebuild VTK (perhaps it would be good to remove existing > VTK first) and check for the "missing" symbol by running: > strings /usr/lib/libvtkCommonExecutionModel.so.1 | grep _ZN33 > > and look for the symbol in the output. If the symbol is listed (as it > should be) then go on to rebuild opencv (so it's built against a > correctly working VTK), then try building vlc again. > > chris Thanks it works now with last VTK sbo and rebuild opencv. From willysr at slackbuilds.org Sat May 16 02:04:40 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 May 2020 09:04:40 +0700 Subject: [Slackbuilds-users] Updates - 20200516.1 Message-ID: <393b61cf-2721-1dbe-2f5d-5698dd9cf7ed@slackbuilds.org> Sat May 16 01:45:30 UTC 2020 academic/fet: Updated for version 5.44.6. academic/latex2html: Updated for version 2020. academic/libqalculate: Updated to version 3.10.0 academic/meep: Updated for version 1.14. academic/mpb: Updated for version 1.10.0. academic/qalculate-gtk: Updated to version 3.10.0 audio/ocp: Updated for version 0.2.1. desktop/x-tile: updated for version 3.1 development/codelite: Fix build against newer libssh. development/colordiff: Updated for version 1.0.19. development/dbeaver-ce: Updated for version 7.0.4. development/git-lfs: Updated for version 2.11.0. development/nodejs: Fix MD5SUM. development/vscode-bin: Updated for version 0.98. games/FlightGear-data: Updated for version 2020.1.1. games/FlightGear: Updated for version 2020.1.1. games/mrboom: Updated for version 4.9. games/peg-e: Updated to version 1.2.8 games/quarry: Added (a universal board game interface program) gis/Fiona: Remove Python 2 support. gis/Shapely: Remove Python 2 support. gis/geopandas: Added (Python tools for geographic data) gis/geopy: Updated for version 1.22.0. gis/navit: Updated for version 0.5.4. gis/pgsql-ogr-fdw: Updated for version 1.0.11. gis/pyproj: Updated for version 2.6.1. gis/rasterio: Updated for version 1.1.4. gis/saga-gis: Updated for version 7.6.3. graphics/qrencode: Remove .la files. libraries/Jinja2: Updated for version 2.11.2. libraries/SimGear: Updated for version 2020.1.1. libraries/digimend-kernel-drivers: Updated for version 20200429. libraries/libctl: Updated for version 4.5.0. libraries/libqb: Updated for version 2.0.0. libraries/libxnvctrl: Updated for version 440.82. libraries/libyang: Updated for version 1.0.167. libraries/live555: Updated for version 2020.05.15 libraries/luasec: Updated for version 0.9. libraries/netcdf: Updated for version 4.7.4. libraries/pcre2: Updated to version 10.35 libraries/podofo: Fix build version number misc/linux_logo: Updated for version 6.0. misc/yubioath-desktop: Added (Yubico Authenticator) multimedia/flashplayer-plugin: Updated for version 32.0.0.371. multimedia/pepperflash-plugin: Updated for version 32.0.0.371. multimedia/strawberry: Updated for version 0.6.10. multimedia/webvfx: Added (video effects engine). network/AdGuardHome: Updated for version 0.102.0. network/brave-browser: Updated for version 1.8.95. network/broadcom-sta: Support for Linux 5.6. network/deluge: Update DEP. network/icecat: Updated for version 60.7.0. network/netsniff-ng: Updated for version 0.6.7. network/prosody: Updated for version 11.5. network/sfeed: Updated for version 0.9.17. network/shorewall-core: Updated for version 5.2.4.5. network/shorewall6: Updated for version 5.2.4.5. network/shorewall: Updated for version 5.2.4.5. network/signal-desktop: Updated for version 1.33.4. network/spamassassin: Updated for version 3.4.4. network/syncthing: Updated for version 1.5.0. network/telegram: Updated for version 2.1.5. network/wireguard-tools: Updated for version 1.0.20200510. network/zoom-linux: Updated for version 5.0.403652.0509. office/calibre-bin: Updated for version 4.16.0. office/ganttproject: Updated for version 2.8.11. office/gnucash: Patched. office/when: Updated for version 1.1.40. perl/perl-MaxMind-DB-Reader-XS: Added (XS searching in MaxMind DB) perl/perl-MaxMind-DB-Reader: Added (MaxMind DB reader) python/contextlib2: Added (Context management). python/internetarchive: Added (CLI interface to Archive.org). python/jsonpointer: Added (Library to resolve JSON Pointers). python/python-branca: Updated for version 0.4.1. python/python-libnacl: Updated to version 1.7.1 python/python-toml: Updated for version 0.10.1. python/python3-Cython: Updated for version 0.29.17 python/python3-astroid: Updated for version 2.4.1. python/python3-jupyter-ipykernel: Updated for version 5.2.1. python/python3-pandas: Updated for version 1.0.3. python/python3-pylint: Updated for version 2.5.2. python/python3-seaborn: Updated for version 0.10.1. python/python3-wrapt: Updated for version 1.12.1. python/schema: Added (Python data structures validation). python/sphinx-rtd-theme: Added (decorator) python/typing-extensions: Added (Backported/Experimental Type Hints) python/vine: Added (promise, async, future) python/workbook: Added (App that creates xls reports or tables) python/xlutils: Added (utilities for working with Excel files) ruby/rubygem-parser: Updated for version 2.7.1.2. system/ansible: Updated for version 2.9.9. system/clamav: Updated for version 0.102.3. system/goaccess: Updated for version 1.3. system/letsencrypt: Updated for version 1.4.0. system/runit: Update config.tar. system/targetcli-fb: Updated for version 2.1.52. system/usbrelay: Updated for version 0.7. system/vagrant: Updated for version 2.2.9. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From mrvladislavovich at gmail.com Wed May 20 09:06:31 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Wed, 20 May 2020 13:06:31 +0400 Subject: [Slackbuilds-users] tuxguitar with fluidsynth Message-ID: <20200520090631.GA13607@lenovo.myrequiem.net> The library /usr/lib64/libtuxguitar-fluidsynth-jni.so from the package tuxguitar requires libfluidsynth.so.1 from the package fluidsynth, but the package fluidsynth provides a version 2 $ ldd /usr/lib64/libtuxguitar-fluidsynth-jni.so ... libfluidsynth.so.1 => not found ... ls -l /usr/lib64/libfluidsynth* lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so -> libfluidsynth.so.2* lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so.2 -> libfluidsynth.so.2.3.1* -rwxr-xr-x 1 root root /usr/lib64/libfluidsynth.so.2.3.1* The package fluidsynth was recently updated and there was version 1 before the update. Need to return version 1 or update tuxguitar package. From korgie at gmail.com Wed May 20 09:28:15 2020 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Wed, 20 May 2020 12:28:15 +0300 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: <20200520090631.GA13607@lenovo.myrequiem.net> References: <20200520090631.GA13607@lenovo.myrequiem.net> Message-ID: 20 ??? 2020, 12:06 ??, ? ??????? ?MyRequiem ? ??????: > The library /usr/lib64/libtuxguitar-fluidsynth-jni.so from the package > tuxguitar requires libfluidsynth.so.1 from the package fluidsynth, but > the package fluidsynth provides a version 2 > > The package fluidsynth was recently updated and there was version 1 > before the update. Need to return version 1 or update tuxguitar package. 1. maybe with it works with linking 2. maybe it?s better to have a fluidsynth1 version. In the meantime, you can downgrade to fluidsynth1 From mrvladislavovich at gmail.com Wed May 20 09:44:25 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Wed, 20 May 2020 13:44:25 +0400 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: References: <20200520090631.GA13607@lenovo.myrequiem.net> Message-ID: <20200520094425.GA29433@lenovo.myrequiem.net> Re: ??????? ?????????? 20.05.2020 >20 ??? 2020, 12:06 ??, ? ??????? ?MyRequiem ? ??????: > >> The library /usr/lib64/libtuxguitar-fluidsynth-jni.so from the package >> tuxguitar requires libfluidsynth.so.1 from the package fluidsynth, but >> the package fluidsynth provides a version 2 >> > >> The package fluidsynth was recently updated and there was version 1 >> before the update. Need to return version 1 or update tuxguitar package. > >1. maybe with it works with linking >2. maybe it?s better to have a fluidsynth1 version. > >In the meantime, you can downgrade to fluidsynth1 >_______________________________________________ >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/ > 1) If create a link in /usr/lib64 libfluidsynth.so.1 -> libfluidsynth.so.2.3.1 tuxguitar does not start at all with error: $ tuxguitar /usr/lib64/libtuxguitar-fluidsynth-jni.so: undefined symbol: fluid_settings_getstr 2) But in the SBo repository there is only version 2 From willysr at slackbuilds.org Wed May 20 09:52:25 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 May 2020 16:52:25 +0700 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: <20200520090631.GA13607@lenovo.myrequiem.net> References: <20200520090631.GA13607@lenovo.myrequiem.net> Message-ID: <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> > The library /usr/lib64/libtuxguitar-fluidsynth-jni.so from the package > tuxguitar requires libfluidsynth.so.1 from the package fluidsynth, but > the package fluidsynth provides a version 2 > > $ ldd /usr/lib64/libtuxguitar-fluidsynth-jni.so > ... > libfluidsynth.so.1 => not found > ... > > ls -l /usr/lib64/libfluidsynth* > lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so -> libfluidsynth.so.2* > lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so.2 -> libfluidsynth.so.2.3.1* > -rwxr-xr-x 1 root root /usr/lib64/libfluidsynth.so.2.3.1* > > The package fluidsynth was recently updated and there was version 1 > before the update. Need to return version 1 or update tuxguitar package. Have you tried to rebuild tuxguitar? fluidsynth is not a dependency for tuxguitar -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From chris.willing at linux.com Wed May 20 10:01:53 2020 From: chris.willing at linux.com (Christoph Willing) Date: Wed, 20 May 2020 20:01:53 +1000 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> References: <20200520090631.GA13607@lenovo.myrequiem.net> <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> Message-ID: On 20/5/20 7:52 pm, Willy Sudiarto Raharjo wrote: >> The library /usr/lib64/libtuxguitar-fluidsynth-jni.so from the package >> tuxguitar requires libfluidsynth.so.1 from the package fluidsynth, but >> the package fluidsynth provides a version 2 >> >> $ ldd /usr/lib64/libtuxguitar-fluidsynth-jni.so >> ... >> libfluidsynth.so.1 => not found >> ... >> >> ls -l /usr/lib64/libfluidsynth* >> lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so -> libfluidsynth.so.2* >> lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so.2 -> libfluidsynth.so.2.3.1* >> -rwxr-xr-x 1 root root /usr/lib64/libfluidsynth.so.2.3.1* >> >> The package fluidsynth was recently updated and there was version 1 >> before the update. Need to return version 1 or update tuxguitar package. > > Have you tried to rebuild tuxguitar? > fluidsynth is not a dependency for tuxguitar > The existing SlackBuild is just a repackaging of a binary release. The source code is available though - maybe someone wants to do a "from source" SlackBuild? I see there is also a version 1.5.4 available now (compared with 1.5.1 in SBo). Maybe it is more compatible with the newer fluidsynth. 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 mrvladislavovich at gmail.com Wed May 20 10:03:56 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Wed, 20 May 2020 14:03:56 +0400 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> References: <20200520090631.GA13607@lenovo.myrequiem.net> <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> Message-ID: <20200520100356.GB29433@lenovo.myrequiem.net> Re: Willy Sudiarto Raharjo 20.05.2020 <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d at slackbuilds.org> >> The library /usr/lib64/libtuxguitar-fluidsynth-jni.so from the package >> tuxguitar requires libfluidsynth.so.1 from the package fluidsynth, but >> the package fluidsynth provides a version 2 >> >> $ ldd /usr/lib64/libtuxguitar-fluidsynth-jni.so >> ... >> libfluidsynth.so.1 => not found >> ... >> >> ls -l /usr/lib64/libfluidsynth* >> lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so -> libfluidsynth.so.2* >> lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so.2 -> libfluidsynth.so.2.3.1* >> -rwxr-xr-x 1 root root /usr/lib64/libfluidsynth.so.2.3.1* >> >> The package fluidsynth was recently updated and there was version 1 >> before the update. Need to return version 1 or update tuxguitar package. > >Have you tried to rebuild tuxguitar? >fluidsynth is not a dependency for tuxguitar > >-- >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/ > Slackbuild simply repackages the binary package tuxguitar-1.5.1-linux-x86_64.tar.gz. Nothing compiles during the build tuxguitar package. In this case, just need to rename package fluidsynth to fluidsynth2 and add fluidsynth1 :) From korgie at gmail.com Wed May 20 10:30:26 2020 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Wed, 20 May 2020 13:30:26 +0300 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> References: <20200520090631.GA13607@lenovo.myrequiem.net> <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> Message-ID: 20 ??? 2020, 12:52 ??, ? ??????? ?Willy Sudiarto Raharjo ? ??????: >> >> The package fluidsynth was recently updated and there was version 1 >> before the update. Need to return version 1 or update tuxguitar package. Temporarily you can try to downgrade fluidsynth https://slackbuilds.org/repository/14.1/audio/fluidsynth/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrvladislavovich at gmail.com Wed May 20 10:36:51 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Wed, 20 May 2020 14:36:51 +0400 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: References: <20200520090631.GA13607@lenovo.myrequiem.net> <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> Message-ID: <20200520103651.GC29433@lenovo.myrequiem.net> Re: Christoph Willing 20.05.2020 >On 20/5/20 7:52 pm, Willy Sudiarto Raharjo wrote: >>> The library /usr/lib64/libtuxguitar-fluidsynth-jni.so from the package >>> tuxguitar requires libfluidsynth.so.1 from the package fluidsynth, but >>> the package fluidsynth provides a version 2 >>> >>> $ ldd /usr/lib64/libtuxguitar-fluidsynth-jni.so >>> ... >>> libfluidsynth.so.1 => not found >>> ... >>> >>> ls -l /usr/lib64/libfluidsynth* >>> lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so -> libfluidsynth.so.2* >>> lrwxrwxrwx 1 root root /usr/lib64/libfluidsynth.so.2 -> libfluidsynth.so.2.3.1* >>> -rwxr-xr-x 1 root root /usr/lib64/libfluidsynth.so.2.3.1* >>> >>> The package fluidsynth was recently updated and there was version 1 >>> before the update. Need to return version 1 or update tuxguitar package. >> >> Have you tried to rebuild tuxguitar? >> fluidsynth is not a dependency for tuxguitar >> > >The existing SlackBuild is just a repackaging of a binary release. The >source code is available though - maybe someone wants to do a "from >source" SlackBuild? > >I see there is also a version 1.5.4 available now (compared with 1.5.1 >in SBo). Maybe it is more compatible with the newer fluidsynth. > >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. The problem is solved by installing the latest version tuxguitar-1.5.4 from binary release. Need to write to the maintainer to update the tuxguitar version. This will be easier than splitting fluidsynth package into two versions (fluidsynth1 and fluidsynth2). From willysr at slackbuilds.org Wed May 20 13:31:06 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 May 2020 20:31:06 +0700 Subject: [Slackbuilds-users] tuxguitar with fluidsynth In-Reply-To: References: <20200520090631.GA13607@lenovo.myrequiem.net> <5288ecd0-ede2-c371-6ea6-d49bc6a6ee1d@slackbuilds.org> Message-ID: <2197f105-ace9-22c4-39ab-f13ff1be59a7@slackbuilds.org> >> Have you tried to rebuild tuxguitar? >> fluidsynth is not a dependency for tuxguitar >> > > The existing SlackBuild is just a repackaging of a binary release. The > source code is available though - maybe someone wants to do a "from > source" SlackBuild? > > I see there is also a version 1.5.4 available now (compared with 1.5.1 > in SBo). Maybe it is more compatible with the newer fluidsynth. i tested on a vm and it still works with the current version of what we have here in our repository. i install fluidsynth first and then tuxguitar -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed May 20 14:37:48 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 20 May 2020 07:37:48 -0700 (PDT) Subject: [Slackbuilds-users] Updates - 20200516.1 In-Reply-To: <393b61cf-2721-1dbe-2f5d-5698dd9cf7ed@slackbuilds.org> References: <393b61cf-2721-1dbe-2f5d-5698dd9cf7ed@slackbuilds.org> Message-ID: On Sat, 16 May 2020, Willy Sudiarto Raharjo wrote: > development/dbeaver-ce: Updated for version 7.0.4. The repo hosts both dbeaver-3.5.8 and dbeaver-ce-7.0.4 with different maintainers but descriptions that are essentially the same. I've been using dbeaver for years and would like to learn how the two versions differ. Regards, Rich From dickson.tim at googlemail.com Wed May 20 15:18:35 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 20 May 2020 16:18:35 +0100 Subject: [Slackbuilds-users] perl-Module-Build slackbuild In-Reply-To: <1411506960.1366812.1589967447587@mail.yahoo.com> References: <1411506960.1366812.1589967447587@mail.yahoo.com> Message-ID: <32cbfc82-04c0-42de-8a71-efdcf16d11c4@googlemail.com> regarding the? perl-Module-Build slackbuild This package has an extra (unlisted) optional dependency, perl-Archive-Zip I emailed the maintainer (Edinaldo) regarding adding it to the readme, and he suggested posting to the list, as he is too busy to look at it at the moment. if it could be added to the README that would be great. many thanks. Tim --- This email has been checked for viruses by AVG. https://www.avg.com From rshepard at appl-ecosys.com Wed May 20 15:29:38 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 20 May 2020 08:29:38 -0700 (PDT) Subject: [Slackbuilds-users] sbopkg issues Message-ID: Is there a separate sbopkg mail list? I want to learn why when sbopkg builds a file of upgrades it keep listing python3-PyQt5 when the installed version is the current one which to it wants to upgrade. And today, it did the same thing with gnucash-3.10 which I've had installed and running. Rich From dave at slackbuilds.org Wed May 20 16:48:57 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 20 May 2020 17:48:57 +0100 Subject: [Slackbuilds-users] perl-Module-Build slackbuild In-Reply-To: <32cbfc82-04c0-42de-8a71-efdcf16d11c4@googlemail.com> References: <1411506960.1366812.1589967447587@mail.yahoo.com> <32cbfc82-04c0-42de-8a71-efdcf16d11c4@googlemail.com> Message-ID: <20200520164857.GI7990@blackswan.r0t.uk> > regarding the? perl-Module-Build slackbuild > > This package has an extra (unlisted) optional dependency, > perl-Archive-Zip > > I emailed the maintainer (Edinaldo) regarding adding it to the > readme, and he suggested posting to the list, as he is too busy > to look at it at the moment. > > if it could be added to the README that would be great. > many thanks. > Tim Hi Tim, I'll take a look. Cheers, -- Dave -------------- 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 Wed May 20 17:33:35 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 May 2020 00:33:35 +0700 Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: References: Message-ID: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> > Is there a separate sbopkg mail list? > > I want to learn why when sbopkg builds a file of upgrades it keep listing > python3-PyQt5 when the installed version is the current one which to it > wants > to upgrade. And today, it did the same thing with gnucash-3.10 which I've > had installed and running. https://sbopkg.org/mailman/listinfo/sbopkg-users -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed May 20 17:38:08 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 20 May 2020 10:38:08 -0700 (PDT) Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> References: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> Message-ID: On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote: > https://sbopkg.org/mailman/listinfo/sbopkg-users Thanks, Willy. I should have looked there first. Stay well, Rich From willysr at slackbuilds.org Wed May 20 17:42:46 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 May 2020 00:42:46 +0700 Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: References: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> Message-ID: On 5/21/20 12:38 AM, Rich Shepard wrote: >> https://sbopkg.org/mailman/listinfo/sbopkg-users > > Thanks, Willy. I should have looked there first. Although you might want to run sqg to generate the queue file again for the package you want to build. Perhaps it was from an old queue file that hasn't been updated after some public update. I don't see python3-PyQt5 in gnucash's queue file. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed May 20 17:50:50 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 20 May 2020 10:50:50 -0700 (PDT) Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: References: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> Message-ID: On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote: > Although you might want to run sqg to generate the queue file again for > the package you want to build. Perhaps it was from an old queue file that > hasn't been updated after some public update. Willy, I don't keep the update file when sbopkg is finished. I'll look for the queue file. > I don't see python3-PyQt5 in gnucash's queue file. Two separate issues: python3-PyQt5 has been presented for several weeks. GnuCash upgrade is a new one this week. Thanks, Rich From willysr at slackbuilds.org Wed May 20 17:53:29 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 May 2020 00:53:29 +0700 Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: References: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> Message-ID: <897ee404-9099-bdca-bfc5-e492e104e611@slackbuilds.org> > I don't keep the update file when sbopkg is finished. I'll look for the > queue file. queue file need to be updated manually if there's a chance in the repository after public update. It's always a good practice to run sqg -a on every public update after running sbopkg -r >> I don't see python3-PyQt5 in gnucash's queue file. > > Two separate issues: python3-PyQt5 has been presented for several weeks. > GnuCash upgrade is a new one this week. In what package? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed May 20 18:00:29 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 20 May 2020 11:00:29 -0700 (PDT) Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: <897ee404-9099-bdca-bfc5-e492e104e611@slackbuilds.org> References: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> <897ee404-9099-bdca-bfc5-e492e104e611@slackbuilds.org> Message-ID: On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote: > queue file need to be updated manually if there's a chance in the > repository after public update. It's always a good practice to run sqg -a > on every public update after running sbopkg -r Willy, I've been using the GUI so I need to learn the CLI. >> Two separate issues: python3-PyQt5 has been presented for several weeks. >> GnuCash upgrade is a new one this week. > > In what package? Here, gnucash-3.10 was installed. After synchronizing sbopkg with the repo I had it search for upgrades. One upgrade was for python3-PyQt5-5.13.2, noting that -5.13.2 is installed. Another upgrade was for gnucash-3.10, noting that -3.10 is installed. Regards, Rich From willysr at slackbuilds.org Wed May 20 18:04:16 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 May 2020 01:04:16 +0700 Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: References: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> <897ee404-9099-bdca-bfc5-e492e104e611@slackbuilds.org> Message-ID: <2a1e35b4-4948-a2e9-6d15-a215a33aabe2@slackbuilds.org> > I've been using the GUI so I need to learn the CLI. > >>> Two separate issues: python3-PyQt5 has been presented for several weeks. >>> GnuCash upgrade is a new one this week. >> >> In what package? > > Here, gnucash-3.10 was installed. After synchronizing sbopkg with the > repo I > had it search for upgrades. One upgrade was for python3-PyQt5-5.13.2, > noting > that -5.13.2 is installed. Another upgrade was for gnucash-3.10, noting > that -3.10 is installed. Perhaps there's an old queue pending in your setting? use View menu to check it. I'm suspecting that it's a leftover from previous build that you haven't cleared. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri May 22 17:45:38 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 May 2020 00:45:38 +0700 Subject: [Slackbuilds-users] Updates - 20200516.1 In-Reply-To: References: <393b61cf-2721-1dbe-2f5d-5698dd9cf7ed@slackbuilds.org> Message-ID: <12f0e75f-3798-9607-f255-166a04b78c3e@slackbuilds.org> >> development/dbeaver-ce: Updated for version 7.0.4. > > The repo hosts both dbeaver-3.5.8 and dbeaver-ce-7.0.4 with different > maintainers but descriptions that are essentially the same. I've been using > dbeaver for years and would like to learn how the two versions differ. dbaever is now removed -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Fri May 22 17:59:22 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 22 May 2020 10:59:22 -0700 (PDT) Subject: [Slackbuilds-users] Updates - 20200516.1 In-Reply-To: <12f0e75f-3798-9607-f255-166a04b78c3e@slackbuilds.org> References: <393b61cf-2721-1dbe-2f5d-5698dd9cf7ed@slackbuilds.org> <12f0e75f-3798-9607-f255-166a04b78c3e@slackbuilds.org> Message-ID: On Sat, 23 May 2020, Willy Sudiarto Raharjo wrote: > dbeaver is now removed That clears it up, Willy. Thanks, Rich From willysr at slackbuilds.org Fri May 22 19:07:21 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 May 2020 02:07:21 +0700 Subject: [Slackbuilds-users] update openfortivpn In-Reply-To: References: Message-ID: > I want to submit a SlackBuild for NetworkManager-fortisslvpn, but this > requires openfortivpn 1.10+. The latest at the moment is version 1.13.3. > Can you update your SlackBuild to this version or at least 1.10? I have > tested both here on Slackware64 14.2 and -current and they work. > > I see your latest update was in 2016 > > If you are unable to update, I can gladly take over the SlackBuild since > I need both of these for work. Hi Gerardo please take over this script as the script was submitted in 2016 and no updates since then. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Fri May 22 19:38:06 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Fri, 22 May 2020 12:38:06 -0700 Subject: [Slackbuilds-users] aspell6-es Message-ID: <988e9094-69cc-46f5-93cb-9ad85f609c35@www.fastmail.com> Just found out that aspell6-es is redundant since it's already in /extra, so it can be dropped from SBo. -- Dave From willysr at slackbuilds.org Fri May 22 19:43:17 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 May 2020 02:43:17 +0700 Subject: [Slackbuilds-users] aspell6-es In-Reply-To: <988e9094-69cc-46f5-93cb-9ad85f609c35@www.fastmail.com> References: <988e9094-69cc-46f5-93cb-9ad85f609c35@www.fastmail.com> Message-ID: > Just found out that aspell6-es is redundant since it's already in /extra, so it can be dropped from SBo. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat May 23 02:47:46 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 May 2020 09:47:46 +0700 Subject: [Slackbuilds-users] Updates - 20200523.1 Message-ID: <90be1627-5d8b-5ce9-69fc-65ea9d70701b@slackbuilds.org> Sat May 23 02:32:35 UTC 2020 academic/boinc: fix default data location academic/colin: Added (a structural analysis application). academic/muscle: Update script and added manual page. academic/rpy2: Updated for version 3.3.3. academic/tiemu: Added (TI-89/92/V200 emulator for linux) desktop/lumina: Updated for version 1.6.0. desktop/unsaver: Added (deactivate screensaver). development/OpenHantek6022: Added (Hantek6022 oscilloscope software) development/dasht: Updated for version 2.4.0. development/dbeaver-ce: Updated for version 7.0.5. development/dbeaver: Removed (use dbeaver-ce). games/VASSAL: Better desktop support. games/mangband: Fix MD5SUM. games/mgba: Fix typos when copying documents. games/mrboom: Update script. gis/qgis: Updated for version 3.12.3. graphics/tuxpaint: Add missing dep. libraries/aqbanking: Updated for version 6.2.1. libraries/enchant2: Updated for version 2.2.8. libraries/gwenhywfar: Updated for version 5.3.0. libraries/imlib2_loaders: Updated for version 1.6.1. misc/goldencheetah: Added desktop file and icons. misc/protobuf3: Updated for version 3.12.1. multimedia/aom: Added (Open Source Video Codec) multimedia/plexmediaserver: Updated to 1.19.3.2831_181d9145d. multimedia/xawtv: Updated for version 3.107. network/bluejeans: Updated for version 2.2.0. network/dropbox: Updated for version 97.4.467. network/etherape: Updated for version 0.9.19. network/frr: Updated for version 7.3. network/onedrive: Updated for version 2.4.1. network/pCloudDrive: Updated for version 1.8.2. network/prosody-mod-smacks-offline: Removed. network/signal-desktop: Updated for version 1.34.1. network/teamviewer: Updated for version 15.5.6. network/tor: Updated for version 0.4.3.5. network/wireguard-linux-compat: Updated for version 1.0.20200520. network/wireguard-tools: Updated for version 1.0.20200513. network/wireshark: Updated for version 3.2.4. network/zoom-linux: Updated for version 5.0.408598.0517. office/aspell6-es: Removed. office/focuswriter-legacy: Added (distraction-free word processor) office/focuswriter: Updated for version 1.7.6. office/fop2.0: Added (print formatter). office/fop: Updated for version 2.5. office/lumina-calculator: Updated for version 1.6.0. office/lumina-pdf: Updated for version 1.6.0. office/pstoedit: Added configure options. office/timew: Update MD5SUM. perl/perl-Module-Build: Updated README with optional deps.. python/BeautifulSoup4: Updated for v 4.9.1, moved from libraries. python/PyAudio: Updated for version 0.2.11. python/WTForms: Updated for version 2.3.1. python/Yapps2: Added (Yet Another Python Parser System). python/alabaster: Updated for version 0.7.12. python/captcha: Added (A captcha python library) python/cheetah3: Added (template engine and code-generation tool) python/imagesize: Updated for version 1.2.0. python/jaraco-packaging: Added (Tools for packaging). python/jsonpatch: Added (Library to apply JSON Patches) python/python-soupsieve: Updated for version 1.9.6. python/python3-Flask-httpauth: Added (Extension for Python3-Flask) python/python3-multidict: Updated for version 4.7.6. python/python3-soupsieve: Updated for version 2.0.1. python/rst-linker: Added (routine for adding links). python/rst: Added (Python module). ruby/ruby-build: Updated for version 20200520. system/epson-inkjet-printer-escpr2: Updated for version 1.1.12. system/fd: Updated for version 8.1.0. system/gnu-unifont: Updated for version 13.0.02. system/kitchen-sync: Updated for version 2.3. system/slack-osquery: Added (osquery extensions for slackware). system/ttf-ipaex: Updated for version 004.01. system/vagrant: Updated md5sum. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From gerardo.zamudio at linux.com Sat May 23 08:36:40 2020 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sat, 23 May 2020 03:36:40 -0500 Subject: [Slackbuilds-users] update openfortivpn In-Reply-To: References: Message-ID: <56b10d34c76ec34f3eefb9e79d696658@linux.com> On 2020-05-22 02:07 PM, Willy Sudiarto Raharjo wrote: >> I want to submit a SlackBuild for NetworkManager-fortisslvpn, but this >> requires openfortivpn 1.10+. The latest at the moment is version >> 1.13.3. >> Can you update your SlackBuild to this version or at least 1.10? I >> have >> tested both here on Slackware64 14.2 and -current and they work. >> >> I see your latest update was in 2016 >> >> If you are unable to update, I can gladly take over the SlackBuild >> since >> I need both of these for work. > > Hi Gerardo > > please take over this script as the script was submitted in 2016 and no > updates since then. > > I submitted both SlackBuilds today. I made a mistake in NetworkManager-fortisslvpn. The tag is incorrect. Can you please change the tag to SBo before merging? Thanks, Gerardo Zamudio From jebrhansen+SBo at gmail.com Sat May 23 09:06:45 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 23 May 2020 03:06:45 -0600 Subject: [Slackbuilds-users] sbopkg issues In-Reply-To: References: <5fee804f-2990-b0ed-b78d-2e6951cb8929@slackbuilds.org> <897ee404-9099-bdca-bfc5-e492e104e611@slackbuilds.org> Message-ID: On Wed, May 20, 2020, 12:00 PM Rich Shepard wrote: > On Thu, 21 May 2020, Willy Sudiarto Raharjo wrote: > > > queue file need to be updated manually if there's a chance in the > > repository after public update. It's always a good practice to run sqg -a > > on every public update after running sbopkg -r > > Willy, > > I've been using the GUI so I need to learn the CLI. > > >> Two separate issues: python3-PyQt5 has been presented for several weeks. > >> GnuCash upgrade is a new one this week. > > > > In what package? > > Here, gnucash-3.10 was installed. After synchronizing sbopkg with the repo > I > had it search for upgrades. One upgrade was for python3-PyQt5-5.13.2, > noting > that -5.13.2 is installed. Another upgrade was for gnucash-3.10, noting > that -3.10 is installed. > gnucash had it's build number bumped 7 days ago to add a patch for boost. https://git.slackbuilds.org/slackbuilds/commit/office/gnucash?h=14.2&id=9c270f89fd886c80e031ff3930f3c923a9f6abb4 python3-PyQt5 had it's build number bumped at the end of April to change how the python version is determined. https://git.slackbuilds.org/slackbuilds/commit/libraries/python3-PyQt5?h=14.2&id=47f31d21c7b44346917fd1048f5a6dc31ef7f545 This is why sbopkg presented these as updates. You can always check the changelog link on the SBo page for that package to see what the latest change was. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.david.strong at gmail.com Sat May 23 10:00:18 2020 From: andrew.david.strong at gmail.com (andrew) Date: Sat, 23 May 2020 20:00:18 +1000 Subject: [Slackbuilds-users] Remove libaom... Message-ID: <20200523100018.GA3148@ilium.andrews-corner.org> Hi, The new 'aom' is the replacement / update for 'libaom', could libaom be removed from SBo? Thanks, Andrew -- You think that's air you're breathing now? From dave at slackbuilds.org Sat May 23 12:18:39 2020 From: dave at slackbuilds.org (D Woodfall) Date: Sat, 23 May 2020 13:18:39 +0100 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: <20200523100018.GA3148@ilium.andrews-corner.org> References: <20200523100018.GA3148@ilium.andrews-corner.org> Message-ID: <20200523121839.GA27315@blackswan.r0t.uk> On 23/05/20 20:00, andrew put forth the proposition: > Hi, > > The new 'aom' is the replacement / update for 'libaom', could libaom > be removed from SBo? > > Thanks, > > Andrew Done. -- Dave -------------- 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 May 23 18:10:24 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 23 May 2020 18:10:24 +0000 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: <20200523121839.GA27315@blackswan.r0t.uk> References: <20200523100018.GA3148@ilium.andrews-corner.org> <20200523121839.GA27315@blackswan.r0t.uk> Message-ID: <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> On Sat, 23 May 2020, at 12:18 PM, D Woodfall wrote: > On 23/05/20 20:00, > andrew put forth the proposition: > > > > The new 'aom' is the replacement / update for 'libaom', could libaom > > be removed from SBo? > > >From aom.info: https://aomedia.googlesource.com/aom/+archive/bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz 0b6d82f4b0f56c198e400ad829b27bba md5sum fails here. -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat May 23 18:32:47 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 May 2020 01:32:47 +0700 Subject: [Slackbuilds-users] update openfortivpn In-Reply-To: <56b10d34c76ec34f3eefb9e79d696658@linux.com> References: <56b10d34c76ec34f3eefb9e79d696658@linux.com> Message-ID: <8b3aa6ab-8983-fb34-b990-abe962109745@slackbuilds.org> > I submitted both SlackBuilds today. > > I made a mistake in NetworkManager-fortisslvpn. The tag is incorrect. > > Can you please change the tag to SBo before merging? you can always remove it using the code that was sent to your mail after submitting. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From skaendo at linuxmail.org Sat May 23 21:20:26 2020 From: skaendo at linuxmail.org (Ska Endo) Date: Sat, 23 May 2020 23:20:26 +0200 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> References: <20200523100018.GA3148@ilium.andrews-corner.org> <20200523121839.GA27315@blackswan.r0t.uk> <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> Message-ID: An HTML attachment was scrubbed... URL: From andrew.david.strong at gmail.com Sat May 23 23:30:27 2020 From: andrew.david.strong at gmail.com (andrew) Date: Sun, 24 May 2020 09:30:27 +1000 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> References: <20200523100018.GA3148@ilium.andrews-corner.org> <20200523121839.GA27315@blackswan.r0t.uk> <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> Message-ID: <20200523233027.GA4250@ilium.andrews-corner.org> Hi Dave, Thanks for your email: > From aom.info: > > https://aomedia.googlesource.com/aom/+archive/ > bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz > 0b6d82f4b0f56c198e400ad829b27bba > > md5sum fails here. The issue seems to be if you download using wget this gives the md5sum found in the info file: 0b6d82f4b0f56c198e400ad829b27bba bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz However a browser download gives a different filename and md5sum: ebca14bf0ef8843cf89fb8cbbab7b6ef aom-bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz I have worked around the different filenames in the script but I am not entirely sure what to do with 2 md5sums. I gave the wget md5sum because I believed that the semi-automated tools used to download and build from SBo would use wget. All the best, Andrew -- You think that's air you're breathing now? From yalhcru at gmail.com Sat May 23 23:53:27 2020 From: yalhcru at gmail.com (B Watson) Date: Sat, 23 May 2020 19:53:27 -0400 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: <20200523233027.GA4250@ilium.andrews-corner.org> References: <20200523100018.GA3148@ilium.andrews-corner.org> <20200523121839.GA27315@blackswan.r0t.uk> <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> <20200523233027.GA4250@ilium.andrews-corner.org> Message-ID: On 5/23/20, andrew wrote: > > The issue seems to be if you download using wget this gives the > md5sum found in the info file: It's worse than that. I downloaded it twice in a row with wget and got 2 different md5sums, neither of which matches the one in the .info file. I even can tell you why: the server you're downloading from, is creating the tarball on the fly for every download. And gzipped tarballs (or any gzipped files) have a timestamp in the gzip header, which is the date/time that the file was compressed. The source is going to have to be hosted somehwhere else. Unless of course it's released under a license that doesn't allow that. Your README says it's open source, so presumably mirroring the source is fine. Behold: downloading the file 3 times in a row, with a 60-second pause between, results in "gzip -v -l" showing 3 different timestamps, and md5sum shows us 3 different md5sums. $ for i in 1 2 3; do wget https://aomedia.googlesource.com/aom/+archive/bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz; md5sum bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz; gzip -v -l bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz; rm bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz; echo; sleep 60; done --2020-05-23 19:47:04-- https://aomedia.googlesource.com/aom/+archive/bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz Resolving aomedia.googlesource.com... 2607:f8b0:4002:c03::52, 173.194.219.82 Connecting to aomedia.googlesource.com|2607:f8b0:4002:c03::52|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: ???bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz??? bb35ba9148543f22ba7d8 [ <=> ] 3.33M 191KB/s in 19s 2020-05-23 19:47:27 (179 KB/s) - ???bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz??? saved [3497415] 3c21fb351f527fef823646ce7c9c0ce7 bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz method crc date time compressed uncompressed ratio uncompressed_name defla a42a6dcc May 23 19:47 3497415 21942272 84.1% bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar --2020-05-23 19:48:27-- https://aomedia.googlesource.com/aom/+archive/bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz Resolving aomedia.googlesource.com... 2607:f8b0:4002:c07::52, 173.194.219.82 Connecting to aomedia.googlesource.com|2607:f8b0:4002:c07::52|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: ???bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz??? bb35ba9148543f22ba7d8 [ <=> ] 3.33M 1.92MB/s in 1.7s 2020-05-23 19:48:29 (1.92 MB/s) - ???bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz??? saved [3497416] cdea23e631fa7466eeb28ae1f7fcfb3f bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz method crc date time compressed uncompressed ratio uncompressed_name defla fbd51f2b May 23 19:48 3497416 21942272 84.1% bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar --2020-05-23 19:49:29-- https://aomedia.googlesource.com/aom/+archive/bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz Resolving aomedia.googlesource.com... 2607:f8b0:4002:c03::52, 64.233.185.82 Connecting to aomedia.googlesource.com|2607:f8b0:4002:c03::52|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: ???bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz??? bb35ba9148543f22ba7d8 [ <=> ] 3.33M 1.57MB/s in 2.1s 2020-05-23 19:49:32 (1.57 MB/s) - ???bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz??? saved [3497349] 7aa10626ce0f4eb79c7caa4a7b279cc8 bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz method crc date time compressed uncompressed ratio uncompressed_name defla 6c5799b1 May 23 19:49 3497349 21942272 84.1% bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar From andrew.david.strong at gmail.com Sun May 24 00:14:22 2020 From: andrew.david.strong at gmail.com (andrew) Date: Sun, 24 May 2020 10:14:22 +1000 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: References: <20200523100018.GA3148@ilium.andrews-corner.org> <20200523121839.GA27315@blackswan.r0t.uk> <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> <20200523233027.GA4250@ilium.andrews-corner.org> Message-ID: <20200524001422.GA10160@ilium.andrews-corner.org> Hi Dave, Your detective work is amazing! As to your suggestion: On Sat, May 23, 2020 at 07:53:27PM -0400, B Watson wrote: > The source is going to have to be hosted somehwhere else. Unless of > course it's released under a license that doesn't allow that. Your > README says it's open source, so presumably mirroring the source is > fine. I have previously been hosting the git snapshots for libaom on my own web site so I can again host the 'release' snapshot there and this should get around this annoying issue. I am working over the weekend unfortunately but I should be able to upload the tarball and reorganise the script hopefully tomorrow evening. This would leave the tarball here: http://www.andrews-corner.org/downloads/aom-bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz Thanks for looking at this, Andrew -- You think that's air you're breathing now? From jebrhansen+SBo at gmail.com Sun May 24 02:00:26 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 23 May 2020 20:00:26 -0600 Subject: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo Message-ID: Hey All, I have a project I'm wanting to add to SBo. This project has a lot of dependencies that aren't on SBo, so I've been working my way through them and creating SlackBuilds for those. However, I came across one that is a python project but doesn't have setup.py. Instead, it has a pyproject.toml file. Based on reading, it seems that you use pip to install this, but I haven't found anything on how to package it. The project I'm running into this problem with is tinydb. https://github.com/msiemens/tinydb Can anyone provide me with a website covering how to build and package these types of projects or the code on how to build it and prep it for packaging? Thanks, Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Sun May 24 05:11:17 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Sun, 24 May 2020 05:11:17 +0000 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: <20200524001422.GA10160@ilium.andrews-corner.org> References: <20200523100018.GA3148@ilium.andrews-corner.org> <20200523121839.GA27315@blackswan.r0t.uk> <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> <20200523233027.GA4250@ilium.andrews-corner.org> <20200524001422.GA10160@ilium.andrews-corner.org> Message-ID: On Sun, 24 May 2020, at 12:14 AM, andrew wrote: > Hi Dave, > > Your detective work is amazing! As to your suggestion: B Watson gets the credit for that! But I can't believe they create the archive on the fly, what exactly is the point of it? O_o -- Dave From willysr at slackbuilds.org Sun May 24 05:48:54 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 May 2020 12:48:54 +0700 Subject: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo In-Reply-To: References: Message-ID: > The project I'm running into this problem with is tinydb. > > https://github.com/msiemens/tinydb > > Can anyone provide me with a website covering how to build and package > these types of projects or the code on how to build it and prep it for > packaging? they provide tarball releases. probably start with that? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From jebrhansen+SBo at gmail.com Sun May 24 05:56:32 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 23 May 2020 23:56:32 -0600 Subject: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo In-Reply-To: References: Message-ID: On Sat, May 23, 2020, 11:49 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > > The project I'm running into this problem with is tinydb. > > > > https://github.com/msiemens/tinydb > > > > Can anyone provide me with a website covering how to build and package > > these types of projects or the code on how to build it and prep it for > > packaging? > > they provide tarball releases. > probably start with that? > As far as I can tell, that's just a tarball of the source code. How do I build that source code into a package in a tmp directory? The instructions say to use "pip install .", but I can't find anything like "python setup.py install --root=$PKG" option. I checked AUR, but they're using an older version of tinydb that still had a setup.py and the program needing tinydb requires a newer version (which doesn't have setup.py). To clarify, the developer removed the ability to build this using a setup.py, so where do I go from there within the SlackBuild? Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Sun May 24 09:05:19 2020 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 24 May 2020 19:05:19 +1000 Subject: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo In-Reply-To: References: Message-ID: On 24/5/20 3:56 pm, Jeremy Hansen wrote: > To clarify, the developer removed the ability to build this using a > setup.py, so where do I go from there within the SlackBuild? > From: pip install --help I see: --root Install everything relative to this alternate root directory. chris From jebrhansen+SBo at gmail.com Sun May 24 09:22:53 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 24 May 2020 03:22:53 -0600 Subject: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo In-Reply-To: References: Message-ID: On Sun, May 24, 2020, 3:05 AM Christoph Willing wrote: > On 24/5/20 3:56 pm, Jeremy Hansen wrote: > > > To clarify, the developer removed the ability to build this using a > > setup.py, so where do I go from there within the SlackBuild? > > > > From: > pip install --help > > I see: > --root Install everything relative to this alternate root > directory. > > > chris > Thanks! I just did man pip and didn't notice anything about a root directory. I didn't realize I could run hello against pip install. I'll give this a shot tomorrow. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Sun May 24 17:08:31 2020 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 24 May 2020 10:08:31 -0700 Subject: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo In-Reply-To: References: Message-ID: Easier solution is just download the tarball from pypi.python.org. It has the setup.py file. https://pypi.python.org/packages/source/t/tinydb/tinydb-4.1.1.tar.gz --Larry On Sun, May 24, 2020 at 2:23 AM Jeremy Hansen wrote: > On Sun, May 24, 2020, 3:05 AM Christoph Willing > wrote: > >> On 24/5/20 3:56 pm, Jeremy Hansen wrote: >> >> > To clarify, the developer removed the ability to build this using a >> > setup.py, so where do I go from there within the SlackBuild? >> > >> >> From: >> pip install --help >> >> I see: >> --root Install everything relative to this alternate root >> directory. >> >> >> chris >> > > Thanks! I just did man pip and didn't notice anything about a root > directory. I didn't realize I could run hello against pip install. I'll > give this a shot tomorrow. > > Jeremy > >> _______________________________________________ > 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 Mon May 25 01:05:03 2020 From: yalhcru at gmail.com (B Watson) Date: Sun, 24 May 2020 21:05:03 -0400 Subject: [Slackbuilds-users] xview Message-ID: Does anyone use xview? I got the urge to revisit the olvwm experience of the early 90s, and noticed xview's maintainer has been silent since 2014. Sent him an email, he's no longer maintaining it, so it's up for grabs. I don't actually want it, I think it should go to someone who uses it. Which means someone who uses 32-bit or maybe multilib: it doesn't support 64-bit and never will (according to its upstream). Any takers? The same maintainer's other build, fvwm95, is spoken for. From andrew.david.strong at gmail.com Mon May 25 08:34:26 2020 From: andrew.david.strong at gmail.com (andrew) Date: Mon, 25 May 2020 18:34:26 +1000 Subject: [Slackbuilds-users] Remove libaom... In-Reply-To: <20200524001422.GA10160@ilium.andrews-corner.org> References: <20200523100018.GA3148@ilium.andrews-corner.org> <20200523121839.GA27315@blackswan.r0t.uk> <1b6aa8e6-3ee9-4a5d-a9a7-889497aecc25@www.fastmail.com> <20200523233027.GA4250@ilium.andrews-corner.org> <20200524001422.GA10160@ilium.andrews-corner.org> Message-ID: <20200525083426.GA12663@ilium.andrews-corner.org> On Sun, May 24, 2020 at 10:14:26AM +1000, andrew wrote: > I have previously been hosting the git snapshots for libaom on my > own web site so I can again host the 'release' snapshot there and > this should get around this annoying issue. I am working over the > weekend unfortunately but I should be able to upload the tarball and > reorganise the script hopefully tomorrow evening. OK so that is all done and now sitting on the SBo server awaiting scrutiny and merging. Thanks to all who have helped me build a better slackbuild :) Andrew -- You think that's air you're breathing now? From dickson.tim at googlemail.com Mon May 25 16:51:07 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 25 May 2020 17:51:07 +0100 Subject: [Slackbuilds-users] cmake too old issues Message-ID: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> One of the slackbuilds I look after has switched from waf to cmake. Unfortunately they have targetted cmake v 3.11 and have used features which are not available, or are broken in cmake 3.5.2 (the version that comes with slackware 14.2) Can anyone point me towards a way to include a newer local version of cmake, just for the slackbuild, or if they have other suggestions, as I have not managed to get the build to work. upstream have made heavy use of IMPORTED_TARGET in pkg_check_modules statements, and in a custom cmake Find module I can bypass the custom Find module and revert to pkgconfig, but I don't know how to do the equivalent of > pkg_check_modules(Gnome REQUIRED IMPORTED_TARGET > ? "atk" > ? "cairo" > ? "gdk-3.0" > ? "gdk-pixbuf-2.0" > ? "gio-2.0" > ? "gobject-2.0" > ? "libsoup-2.4" > ? "pango" > ? "minizip" > ? "zlib" > ? "libxml-2.0>=2.7.8" > ? ) for example, without the "IMPORTED_TARGET" bit. unfortunately, just removing IMPORTED_TARGET text from the dependencies file does not work. the slackbuild in question is xiphos for which I'm trying to get 4.2.1 to build. ( https://github.com/crosswire/xiphos? ) Thanks, Tim --- This email has been checked for viruses by AVG. https://www.avg.com From rellis at dp100.com Mon May 25 16:59:01 2020 From: rellis at dp100.com (Richard Ellis) Date: Mon, 25 May 2020 12:59:01 -0400 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> References: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> Message-ID: <20200525165901.GT28464@d820.dp100.com> On Mon, May 25, 2020 at 05:51:07PM +0100, Tim Dickson via SlackBuilds-users wrote: >One of the slackbuilds I look after has switched from waf to cmake. >Unfortunately they have targetted cmake v 3.11 and have used >features which are not available, or are broken in cmake 3.5.2 (the >version that comes with slackware 14.2) >Can anyone point me towards a way to include a newer local version of >cmake, just for the slackbuild, or if they have other suggestions, Here (32-bit): https://mirrors.slackware.com/slackware/slackware-current/source/d/cmake/ or here (64-bit): https://mirrors.slackware.com/slackware/slackware64-current/source/d/cmake/ Just build the cmake from -current from source, and 'upgradepkg' with the result. If -current's cmake requires some other package(s) that is(are) not new enough in 14.2, then repeat the process with those other packages. From yalhcru at gmail.com Mon May 25 17:21:11 2020 From: yalhcru at gmail.com (B Watson) Date: Mon, 25 May 2020 13:21:11 -0400 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> References: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> Message-ID: On 5/25/20, Tim Dickson via SlackBuilds-users wrote: > Can anyone point me towards a way to include a newer local version of > cmake, just for the slackbuild, or if they have other suggestions, > as I have not managed to get the build to work. One thing you could do: include the source to your newer cmake as a DOWNLOAD in the .info file. First thing your script does is unpack and compile cmake, and install it to $TMP/$PRGNAM/cmake or similar. Then export PATH=$TMP/$PRGNAM/cmake/bin (or wherever the cmake binary ends up). Pat's cmake slackbuild at http://slackware.uk/slackware/slackware64-current/source/d/cmake/ might give you some hints on how to build it. You'll want --prefix=$TMP/$PRGNAM/cmake and you might need --enable-static and --disable-shared if they're supported. You *won't* need --qt-gui, should probably say --no-qt-gui. From yalhcru at gmail.com Mon May 25 17:24:35 2020 From: yalhcru at gmail.com (B Watson) Date: Mon, 25 May 2020 13:24:35 -0400 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: <20200525165901.GT28464@d820.dp100.com> References: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> <20200525165901.GT28464@d820.dp100.com> Message-ID: On 5/25/20, Richard Ellis via SlackBuilds-users wrote: > > Just build the cmake from -current from source, and 'upgradepkg' with > the result. > > If -current's cmake requires some other package(s) that is(are) not new > enough in 14.2, then repeat the process with those other packages. *Ugh*, no. This advice would be OK for someone to do on their own personal system, but it's not going to fly in a SBo script. We wouldn't accept a build that included "replace a bunch of Slackware's core packages with custom built ones" in its instructions. From rellis at dp100.com Mon May 25 18:05:42 2020 From: rellis at dp100.com (Richard Ellis) Date: Mon, 25 May 2020 14:05:42 -0400 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: References: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> <20200525165901.GT28464@d820.dp100.com> Message-ID: <20200525180542.GV28464@d820.dp100.com> On Mon, May 25, 2020 at 01:24:35PM -0400, B Watson wrote: >On 5/25/20, Richard Ellis via SlackBuilds-users > wrote: >> >> Just build the cmake from -current from source, and 'upgradepkg' with >> the result. >> >> If -current's cmake requires some other package(s) that is(are) not new >> enough in 14.2, then repeat the process with those other packages. > >*Ugh*, no. This advice would be OK for someone to do on their own personal >system, but it's not going to fly in a SBo script. We wouldn't accept a >build that included "replace a bunch of Slackware's core packages with >custom built ones" in its instructions. Oops, sorry, yes you are right. I completely miss-understood the request as "build something myself that needs newer cmake than 14.2's version" instead of the intended "as part of an SBo script". From dpross1100 at msn.com Mon May 25 18:45:01 2020 From: dpross1100 at msn.com (dpross1100 at msn.com) Date: Mon, 25 May 2020 14:45:01 -0400 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> Message-ID: An HTML attachment was scrubbed... URL: From chris.willing at linux.com Mon May 25 22:03:12 2020 From: chris.willing at linux.com (Christoph Willing) Date: Tue, 26 May 2020 08:03:12 +1000 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: References: Message-ID: On 26/5/20 4:45 am, dpross1100 at msn.com wrote: > Does it need to be updated? This seems like a perfect example of a > script that should stick with the present version until Slackware 15 > comes out, unless something else requires it to be updated. > Good point. Five of the SlackBuilds I maintain have this "cmake too old" problem. I've been making a note in their READMEs that the existing version will be the last for 14.2. I guess if any really do become urgent then B Watson's suggestion to make a newer cmake part of the build is doable. I've seen other SlackBuilds do similar things e.g. Arduino seems to create a completely new toolchain to do its stuff. chris From dickson.tim at googlemail.com Mon May 25 22:35:09 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 25 May 2020 23:35:09 +0100 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: <20200525165901.GT28464@d820.dp100.com> References: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> <20200525165901.GT28464@d820.dp100.com> Message-ID: <1b47b9a7-96c2-e971-955b-3374e29742fa@googlemail.com> Thanks for the suggestion B.Watson, I'll give it a go. I'm cautious that I don't pollute a "clean" system, but hopefully that should work. If it does, I could always document it, so other people with the same issue could use the same method in their scripts. I agree that the other method suggested would be problematic, especially as it would be hard to add to REQUIRES I have patched other build packages that were forcing an cmake update, but this one was proving too problematic. I would like to wait for slackware 15 as well, but I don't want to wait indefinitely. Hopefully Pat can sort out his distribution model, and gets happy enough with current to do a release soon. "when it's ready" :-) Although I appreciate the stability of slackware release version, I wouldn't want it to be so old that It won't run current common software, or hardware, but (almost as an oxymoron) I wouldn't want to move to "current", because the base changes too much, and my? internet data allowance is restricted. Hence I try to "do my bit" to keep software I use current on my favourite distro. Regards, Tim --- This email has been checked for viruses by AVG. https://www.avg.com From dickson.tim at googlemail.com Wed May 27 15:03:21 2020 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 27 May 2020 16:03:21 +0100 Subject: [Slackbuilds-users] cmake too old issues In-Reply-To: References: <95459447-8ef8-db87-93b9-7b4efe838e6f@googlemail.com> Message-ID: Just a note to say I was successful in adding a private version of cmake to the script for details in case anyone else has the same problem, I posted the steps in the answer to my own query on linuxquestions.org https://www.linuxquestions.org/questions/slackware-14/problem-with-newer-cmake-options-run-on-slackware-cmake-3-5-2-a-4175674772/ Regards, Tim On 25/05/2020 18:21, B Watson wrote: > On 5/25/20, Tim Dickson via SlackBuilds-users > wrote: >> Can anyone point me towards a way to include a newer local version of >> cmake, just for the slackbuild, or if they have other suggestions, >> as I have not managed to get the build to work. > One thing you could do: include the source to your newer cmake as > a DOWNLOAD in the .info file. First thing your script does is > unpack and compile cmake, and install it to $TMP/$PRGNAM/cmake or > similar. Then export PATH=$TMP/$PRGNAM/cmake/bin (or wherever the > cmake binary ends up). > > Pat's cmake slackbuild at > http://slackware.uk/slackware/slackware64-current/source/d/cmake/ > might give you some hints on how to build it. You'll want > --prefix=$TMP/$PRGNAM/cmake and you might need --enable-static and > --disable-shared if they're supported. You *won't* need --qt-gui, should > probably say --no-qt-gui. > _______________________________________________ > 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 mnrwest at gmail.com Fri May 29 19:54:26 2020 From: mnrwest at gmail.com (Mark West) Date: Fri, 29 May 2020 15:54:26 -0400 Subject: [Slackbuilds-users] GSlapt? Message-ID: Does Slackware 14.2 make use of GSlapt? From didier at slint.fr Fri May 29 22:06:31 2020 From: didier at slint.fr (Didier Spaier) Date: Sat, 30 May 2020 00:06:31 +0200 Subject: [Slackbuilds-users] GSlapt? In-Reply-To: References: Message-ID: <8b5ac035-2142-7e39-5f48-b8fe6902a8d0@slint.fr> Le 29/05/2020 ? 21:54, Mark West a ?crit : >Does Slackware 14.2 make use of GSlapt? Hi, Slackware no indeed, but some Slackware users yes, as well as several distributions based on Slackware. Some third party packages repositories do include the information needed by slapt-get to manage dependencies as e.G. sbrepos thanks to Eric Hameleers. If you want to submit a SlackBuild for it @ SBo you'll have to do that also for slapt-get of which GSlapt is a graphical front-end. But I am not sure why you asked that, so if I misunderstood your question please elaborate. Cheers, Didier From rshepard at appl-ecosys.com Fri May 29 22:14:16 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 29 May 2020 15:14:16 -0700 (PDT) Subject: [Slackbuilds-users] Google chrome? Message-ID: I thought SBo provided Google's chrome browser but am not finding it. I did find a linuxquestions thread from 2012 (version -13.37) that suggested it had been available. I'm making a video conference presentation the week after next hosted on a site that's a subset of Zoom. A test connection today failed using the latest firefox and opera and only partially succeeded with the latest chromium. The cloud software site had support for linux but Slackware (of course) was under "other linux" and could not download a library it wanted nor open a necessary web page. Sigh. The conference organizers suggested I try Google's chrome. Going to google's chrome download page I see they have .deb and .rpm packages for download and installation; I don't know that I can download only. They have another page for other linux distributions and for Slackware they point to Alien BOB's chromium. I have the SBo chromium installed. If I can't get something to work here I'll need to drive about 65 miles each way to another city where they have a studio set up to run the entire conference. I'd prefer to avoid that travel if I can present from here. I'm open to suggestions. Rich From yalhcru at gmail.com Fri May 29 22:18:52 2020 From: yalhcru at gmail.com (B Watson) Date: Fri, 29 May 2020 18:18:52 -0400 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On 5/29/20, Rich Shepard wrote: > I thought SBo provided Google's chrome browser but am not finding it. I did > find a linuxquestions thread from 2012 (version -13.37) that suggested it > had been available. It probably disappeared from SBo back then because Pat added it to Slackware: http://slackware.uk/slackware/slackware64-14.2/extra/google-chrome/ Hope that helps. From rshepard at appl-ecosys.com Fri May 29 22:34:09 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 29 May 2020 15:34:09 -0700 (PDT) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Fri, 29 May 2020, B Watson wrote: > It probably disappeared from SBo back then because Pat added it > to Slackware: > http://slackware.uk/slackware/slackware64-14.2/extra/google-chrome/ B. I wondered about that but didn't see it installed and didn't think of looking in /extra. > Hope that helps. Yep. It certainly does! Thanks, and carpe weekend, Rich From klaatu at member.fsf.org Fri May 29 23:44:39 2020 From: klaatu at member.fsf.org (Klaatu) Date: Sat, 30 May 2020 11:44:39 +1200 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: <9092653.ZNxSOz6IVZ@beast> On Friday, May 29, 2020 03:14:16 PM Rich Shepard wrote: > I thought SBo provided Google's chrome browser but am not finding it. I did > find a linuxquestions thread from 2012 (version -13.37) that suggested it > had been available. > > I'm making a video conference presentation the week after next hosted on a > site that's a subset of Zoom. A test connection today failed using the > latest firefox and opera and only partially succeeded with the latest > chromium. The cloud software site had support for linux but Slackware (of > course) was under "other linux" and could not download a library it wanted > nor open a necessary web page. Sigh. > > The conference organizers suggested I try Google's chrome. Going to google's > chrome download page I see they have .deb and .rpm packages for download > and installation; I don't know that I can download only. They have another > page for other linux distributions and for Slackware they point to Alien > BOB's chromium. I have the SBo chromium installed. > > If I can't get something to work here I'll need to drive about 65 miles each > way to another city where they have a studio set up to run the entire > conference. I'd prefer to avoid that travel if I can present from here. > > I'm open to suggestions. > > Rich > _______________________________________________ > 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/ For what it's worth, I've found using AlienBob's build of Chromium pretty useful. He keeps it pretty up to date, and I've never noticed any difference between it and Chrome in terms of compatibility with Chrom*-based tech. http://www.slackware.com/~alien/slackbuilds/chromium/ - klaatu -------------- 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 rshepard at appl-ecosys.com Sat May 30 00:10:51 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 29 May 2020 17:10:51 -0700 (PDT) Subject: [Slackbuilds-users] Google chrome? [ISSUE RESOLVED] In-Reply-To: <9092653.ZNxSOz6IVZ@beast> References: <9092653.ZNxSOz6IVZ@beast> Message-ID: On Sat, 30 May 2020, Klaatu wrote: > For what it's worth, I've found using AlienBob's build of Chromium pretty > useful. He keeps it pretty up to date, and I've never noticed any > difference between it and Chrome in terms of compatibility with > Chrom*-based tech. Klaatu, I've had that installed and updated for several years. It's been my last-resort browser, but could not allow me to download xdg-open because it did not find the URL. So, I built and installed Google Chrome from the transformed .deb source. Then it turned out that Chrome also could not find the URL it wanted to apply to xdg-open. While firefox could not connect with ringcentral.com (apparently a sub-set of Zoom), none of Opera, Chromium, or Chrome could find the URL it wanted. So, ... I tried the option of using the browser, but that also failed. As the last step I followed the link to download the ringcentral client application. Of course, the choice for 'other linux os' had nothing. I downloaded the fedora .rpm, ran it through rpm2tgz, installed the .tgz package and it works. I should have done this from Opera, but was on the phone with the conference managers at the time. Now I can invoke ringcentral, enter the meeting ID, and I'm in. No browser needed. PITA all of this. Had I known there was a self-contained application I could make work on Slackware I would have saved a couple of hours of time and effort. Stay well and enjoy your weekend, Rich From lramos.prof at yahoo.com.br Sat May 30 00:45:56 2020 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Fri, 29 May 2020 21:45:56 -0300 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: <20200530004555.GB384@giustizia.org> Rich, On Fri, May 29, 2020 at 03:14:16PM -0700, Rich Shepard wrote: > The conference organizers suggested I try Google's chrome. Going to google's To add a suggestion, you may try Vivaldi, which is in SBo repository. I've been using it for some time and I'm pretty sure it has a recent version of Google Chrome under the hoods. Hope it helps, Luiz Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br From lramos.prof at yahoo.com.br Sat May 30 00:45:56 2020 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Fri, 29 May 2020 21:45:56 -0300 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: <20200530004555.GB384@giustizia.org> Rich, On Fri, May 29, 2020 at 03:14:16PM -0700, Rich Shepard wrote: > The conference organizers suggested I try Google's chrome. Going to google's To add a suggestion, you may try Vivaldi, which is in SBo repository. I've been using it for some time and I'm pretty sure it has a recent version of Google Chrome under the hoods. Hope it helps, Luiz Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br From phalange at komputermatrix.com Sat May 30 01:19:27 2020 From: phalange at komputermatrix.com (Andrew Payne) Date: Fri, 29 May 2020 21:19:27 -0400 (EDT) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: Hi Rich, I maintain Brave which tracks Chromium. No dependencies and no compiling, so you might want to test it as a Chromium substitute. On Fri, 29 May 2020, Rich Shepard wrote: > I thought SBo provided Google's chrome browser but am not finding it. I did > find a linuxquestions thread from 2012 (version -13.37) that suggested it > had been available. > > I'm making a video conference presentation the week after next hosted on a > site that's a subset of Zoom. A test connection today failed using the > latest firefox and opera and only partially succeeded with the latest > chromium. The cloud software site had support for linux but Slackware (of > course) was under "other linux" and could not download a library it wanted > nor open a necessary web page. Sigh. > > The conference organizers suggested I try Google's chrome. Going to google's > chrome download page I see they have .deb and .rpm packages for download and > installation; I don't know that I can download only. They have another page > for other linux distributions and for Slackware they point to Alien BOB's > chromium. I have the SBo chromium installed. > > If I can't get something to work here I'll need to drive about 65 miles each > way to another city where they have a studio set up to run the entire > conference. I'd prefer to avoid that travel if I can present from here. > > I'm open to suggestions. > > Rich > _______________________________________________ > 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 jebrhansen+SBo at gmail.com Sat May 30 03:23:19 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 29 May 2020 21:23:19 -0600 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Fri, May 29, 2020, 4:14 PM Rich Shepard wrote: > The conference organizers suggested I try Google's chrome. Going to google's > chrome download page I see they have .deb and .rpm packages for download > and > installation; I don't know that I can download only. > I know you already got your answer, but I've found the best way to install an up-to-date chrome is to use ruario's latest-chrome script. https://gist.github.com/ruario/9672759 Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Sat May 30 03:36:50 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 29 May 2020 21:36:50 -0600 Subject: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo In-Reply-To: References: Message-ID: On Sun, May 24, 2020 at 11:08 AM Larry Hajali wrote: > Easier solution is just download the tarball from pypi.python.org. It > has the setup.py file. > > https://pypi.python.org/packages/source/t/tinydb/tinydb-4.1.1.tar.gz > > --Larry > Oops, this message was sitting in my drafts folder. I apparently forgot to finish it. Thanks Larry, that is indeed the easiest method without doing extra legwork (and without requiring pip3). However, I did look into Christoph's hint about pip3 install --help and it seems the following should, but it seems to still grab the deps (at least there's output showing its getting dependencies). pip3 install \ --no-deps \ --prefix=/usr/ \ --root=$PKG \ . I'm not too worried about this since Larry was able to find me a good tarball. Thanks again! Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerardo.zamudio at linux.com Sat May 30 04:00:11 2020 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Fri, 29 May 2020 23:00:11 -0500 Subject: [Slackbuilds-users] update openfortivpn In-Reply-To: <8b3aa6ab-8983-fb34-b990-abe962109745@slackbuilds.org> References: <56b10d34c76ec34f3eefb9e79d696658@linux.com> <8b3aa6ab-8983-fb34-b990-abe962109745@slackbuilds.org> Message-ID: <0409b40f427aefeda53b5d134c238b84@linux.com> On 2020-05-23 01:32 PM, Willy Sudiarto Raharjo wrote: >> I submitted both SlackBuilds today. >> >> I made a mistake in NetworkManager-fortisslvpn. The tag is incorrect. >> >> Can you please change the tag to SBo before merging? > > you can always remove it using the code that was sent to your mail > after > submitting. > I never received an email with a code. I see the SlackBuild was accepted already. Can I submit another .tar.gz with the correct tag? -- Gerardo Zamudio From didier at slint.fr Sat May 30 04:49:33 2020 From: didier at slint.fr (Didier Spaier) Date: Sat, 30 May 2020 06:49:33 +0200 Subject: [Slackbuilds-users] GSlapt? In-Reply-To: <9d2e1233-9142-1999-f21b-485d02912b0e@gmail.com> References: <8b5ac035-2142-7e39-5f48-b8fe6902a8d0@slint.fr> <9d2e1233-9142-1999-f21b-485d02912b0e@gmail.com> Message-ID: <018a215a-5cf9-6a0e-8dab-8457c5f63f31@slint.fr> Hi, Forwarding to the list as you answered privately to my first response. The dependencies management optional feature of slapt-get/gslapt can help only people having done a partial Slackware as if they did a full one all dependencies are already met. Further, this needs a reliable source of information about dependencies included in PACKAGES.TXT. For your information I maintain a distribution based on Slackware and using slapt-get, called Slint. In slapt-getrc we include as source of packages for Slackware this repository: SOURCE=https://slackware.uk/salix/x86_64/slackware-14.2/:DEFAULT which has the dependencies documented in PACKAGES.TXT, courtesy of the Salix project. However Slint can do without this information for Slackware packages as long as none is removed, as based on a full Slackware (only the KDE series is optional). Further some packages are modified for Slint but keep the same base and have priority over the genuine Slackware ones. Additionally we do not support a partial Slint installation, so the dependency information for Slint users only matters for packages that are added to the Slint repository after the ISO has been published. Slint users are advised if using build material from SBo to write a build queue typing: sqg -p and using it to build and install the packages and its dependencies but always with the "keep" option: sbopkg -k -i I also slightly modified sbopkg so that its "keep" option skips the installed dependencies even if the full package name does not end in SBo as we include several packages for which a SlackBuild is available @ SBo but not at the same version or with the same content. Python3 comes to mind: we ship version 3.5.9 but SBo currently has version 3.7.2 which can lead to issues if /usr/bin/python3 links to a version that differ from the one a given package that you try to run was built against. All this rant to remind that the main difficulty with dependencies is the accuracy of the list, which among many factors is context dependent, the context including the build options for the packages and their dependencies, their versions, and the installed software at time of building the list. Cheers, Didier Le 30/05/2020 ? 02:01, Mark West a ?crit?: > I asked because Vector Linux uses it i order to automate their packaging installation procedure and I think it would help to get more people interested in using Slackware 14.2 once they realize that they won't have to struggle trying to correctly install packages any more. > > On 5/29/20 6:06 PM, Didier Spaier wrote: >> Le 29/05/2020 ? 21:54, Mark West a ?crit : >>> Does Slackware 14.2 make use of GSlapt? >> Hi, >> >> Slackware no indeed, but some Slackware users yes, as well as several >> distributions based on Slackware. Some third party packages repositories >> do include the information needed by slapt-get to manage dependencies as >> e.G. sbrepos thanks to Eric Hameleers. >> >> If you want to submit a SlackBuild for it @ SBo you'll have to do that >> also for slapt-get of which GSlapt is a graphical front-end. >> >> But I am not sure why you asked that, so if I misunderstood your >> question please elaborate. >> >> Cheers, >> Didier From willysr at slackbuilds.org Sat May 30 05:14:54 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 30 May 2020 12:14:54 +0700 Subject: [Slackbuilds-users] update openfortivpn In-Reply-To: <0409b40f427aefeda53b5d134c238b84@linux.com> References: <56b10d34c76ec34f3eefb9e79d696658@linux.com> <8b3aa6ab-8983-fb34-b990-abe962109745@slackbuilds.org> <0409b40f427aefeda53b5d134c238b84@linux.com> Message-ID: <557c16b8-780a-cdd7-6d1c-32da86930495@slackbuilds.org> > I never received an email with a code. I see the SlackBuild was accepted > already. Can I submit another .tar.gz with the correct tag? you can send another update after public update, but if it's just a tag, keep it until you have a new update coming or just tell me the new tag, i can directly update it in the db -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat May 30 05:17:31 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 30 May 2020 12:17:31 +0700 Subject: [Slackbuilds-users] GSlapt? In-Reply-To: <018a215a-5cf9-6a0e-8dab-8457c5f63f31@slint.fr> References: <8b5ac035-2142-7e39-5f48-b8fe6902a8d0@slint.fr> <9d2e1233-9142-1999-f21b-485d02912b0e@gmail.com> <018a215a-5cf9-6a0e-8dab-8457c5f63f31@slint.fr> Message-ID: > I also slightly modified sbopkg so that its "keep" option skips the > installed dependencies even if the full package name does not end in SBo > as we include several packages for which a SlackBuild is available @ SBo > but not at the same version or with the same content. Python3 comes to > mind: we ship version 3.5.9 but SBo currently has version 3.7.2 which > can lead to issues if /usr/bin/python3 links to a version that differ > from the one a given package that you try to run was built against. Hi Didier, If you can push that as a PR, i would gladly review it and possibly pushed it to master branch as well. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sat May 30 12:30:30 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 30 May 2020 05:30:30 -0700 (PDT) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: <20200530004555.GB384@giustizia.org> References: <20200530004555.GB384@giustizia.org> Message-ID: On Fri, 29 May 2020, Luiz Carlos Ramos wrote: > To add a suggestion, you may try Vivaldi, which is in SBo repository. I've > been using it for some time and I'm pretty sure it has a recent version of > Google Chrome under the hoods. Luiz, Thank you for the suggestion. I installed chrome from /extra and it had the same issue as opera and chromium: the first thing ringcentral's web page did was try to access a web page using xdg-open, but it could not find that URL. A coding error by ringcentral. The application provides a link to download a client so I went that route. Of course, Slackware was not among the choices, including 'other OS.' I downloaded the fedora *.rpm, ran it through rpm2tgz, and installed the client. This worked and allowed me to access the planning meeting even though the other two participants and also long since left it. I'll use the downloaded ringcentral client for my presentation; no browser needed. Stay well, Rich From alik at ejik.org Sat May 30 12:32:22 2020 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 30 May 2020 15:32:22 +0300 (MSK) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Fri, 29 May 2020, Jeremy Hansen wrote: > I know you already got your answer, but I've found the best way to > install an up-to-date chrome is to use ruario's latest-chrome script. > > https://gist.github.com/ruario/9672759 I think this is equivalent to the SlackBuild from extra, both install the last stable version. Best regards, Alexander From rshepard at appl-ecosys.com Sat May 30 12:34:36 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 30 May 2020 05:34:36 -0700 (PDT) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Fri, 29 May 2020, Andrew Payne wrote: > Hi Rich, I maintain Brave which tracks Chromium. No dependencies and no > compiling, so you might want to test it as a Chromium substitute. Andrew, Thanks very much for the offer but four browsers (firefox, opera. chromium, chrome) are more than sufficient. :-) As I wrote earlier, the problem wasn't the browser (except for the applicaion's non-support for firefox). While the other three browsers could access the main ringcentral page it needed to access another site/page but xdg-open could not find the desired URL. Their direct access client works. Regards, Rich From rshepard at appl-ecosys.com Sat May 30 12:38:24 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 30 May 2020 05:38:24 -0700 (PDT) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Fri, 29 May 2020, Jeremy Hansen wrote: > I know you already got your answer, but I've found the best way to install > an up-to-date chrome is to use ruario's latest-chrome script. > https://gist.github.com/ruario/9672759 Jeremy, That's good to know. I use firefox as my everyday browser; opera when a site doesn't support it. Chromium has worked fine the few times I used it as a last resort. I'm still deciding whether to let Chrome stey installed or remove it wasn't a solution to the immediate need. Best regards, Rich From jebrhansen+SBo at gmail.com Sat May 30 15:00:53 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 30 May 2020 09:00:53 -0600 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Sat, May 30, 2020, 6:32 AM Alexander Verbovetsky wrote: > On Fri, 29 May 2020, Jeremy Hansen wrote: > > > I know you already got your answer, but I've found the best way to > > install an up-to-date chrome is to use ruario's latest-chrome script. > > > > https://gist.github.com/ruario/9672759 > > I think this is equivalent to the SlackBuild from extra, both install > the last stable version. > > Best regards, > Alexander > It's close, but ruario's script will check online for the latest version and download it (and optionally install/upgrade it automatically when finished). The one from extra/ requires you to go and download the latest .deb from Chrome's site and save it in the same folder as the SlackBuild. Both give you the same package at the end, but ruario's requires much less effort on your end. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Sat May 30 16:24:14 2020 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 30 May 2020 19:24:14 +0300 (MSK) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Sat, 30 May 2020, Jeremy Hansen wrote: > On Sat, May 30, 2020, 6:32 AM Alexander Verbovetsky wrote: > > On Fri, 29 May 2020, Jeremy Hansen wrote: > > > > I know you already got your answer, but I've found the best way to > > > install an up-to-date chrome is to use ruario's latest-chrome > > > script. > > > > > > https://gist.github.com/ruario/9672759 > > I think this is equivalent to the SlackBuild from extra, both install > > the last stable version. > > It's close, but ruario's script will check online for the latest > version and download it (and optionally install/upgrade it > automatically when finished). The one from extra/ requires you to go > and download the latest .deb from Chrome's site and save it in the > same folder as the SlackBuild. > > Both give you the same package at the end, but ruario's requires much > less effort on your end. I suppose that every user of SBo has a convenient workflow for running SlackBuilds. With a trivial google-chrome.info, for example ----- PRGNAM="google-chrome" VERSION="10.0.648.151" HOMEPAGE="http://www.google.com/chrome" DOWNLOAD="" MD5SUM="" DOWNLOAD_x86_64="https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb" MD5SUM_x86_64="" REQUIRES="" MAINTAINER="Patrick Volkerding" EMAIL="volkerdi at slackware.com" ----- one can use the same workflow. BTW, I also read the rss https://feeds.feedburner.com/GoogleChromeReleases to know about new versions. Best regards, Alexander From jebrhansen+SBo at gmail.com Sat May 30 17:26:26 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 30 May 2020 11:26:26 -0600 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: Message-ID: On Sat, May 30, 2020, 10:24 AM Alexander Verbovetsky wrote: > On Sat, 30 May 2020, Jeremy Hansen wrote: > > On Sat, May 30, 2020, 6:32 AM Alexander Verbovetsky > wrote: > > > On Fri, 29 May 2020, Jeremy Hansen wrote: > > > > > > I know you already got your answer, but I've found the best way to > > > > install an up-to-date chrome is to use ruario's latest-chrome > > > > script. > > > > > > > > https://gist.github.com/ruario/9672759 > > > > I think this is equivalent to the SlackBuild from extra, both install > > > the last stable version. > > > > It's close, but ruario's script will check online for the latest > > version and download it (and optionally install/upgrade it > > automatically when finished). The one from extra/ requires you to go > > and download the latest .deb from Chrome's site and save it in the > > same folder as the SlackBuild. > > > > Both give you the same package at the end, but ruario's requires much > > less effort on your end. > > I suppose that every user of SBo has a convenient workflow for running > SlackBuilds. With a trivial google-chrome.info, for example > ----- > PRGNAM="google-chrome" > VERSION="10.0.648.151" > HOMEPAGE="http://www.google.com/chrome" > DOWNLOAD="" > MD5SUM="" > DOWNLOAD_x86_64=" > https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb" > MD5SUM_x86_64="" > REQUIRES="" > MAINTAINER="Patrick Volkerding" > EMAIL="volkerdi at slackware.com" > ----- > one can use the same workflow. > > BTW, I also read the rss > https://feeds.feedburner.com/GoogleChromeReleases > to know about new versions. > > Best regards, > Alexander > Very true. Everyone has their own way of doing things. Your method does require manually changing the version in the .info and downloading the .deb, whereas the latest-chrome script will check for a newer release than the one you're running, if there is one, it'll download it and repackage it into a .tgz automatically. If you pass the -i option to the script, it'll even install/upgrade it. I don't keep up with releases at all, but every few weeks, I'll just run latest-chrome.sh -i as root and it'll update my installed chrome if needed. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Sat May 30 22:51:26 2020 From: didier at slint.fr (Didier Spaier) Date: Sun, 31 May 2020 00:51:26 +0200 Subject: [Slackbuilds-users] GSlapt? In-Reply-To: References: <8b5ac035-2142-7e39-5f48-b8fe6902a8d0@slint.fr> <9d2e1233-9142-1999-f21b-485d02912b0e@gmail.com> <018a215a-5cf9-6a0e-8dab-8457c5f63f31@slint.fr> Message-ID: <6f2c977c-b8da-7722-6c05-df1b8dfbc607@slint.fr> Hi Willy > If you can push that as a PR, i would gladly review it and possibly > pushed it to master branch as well. Done. Please bear with me, this is the first time I use this feature. Cheers, Didier From gerardo.zamudio at linux.com Sun May 31 19:25:18 2020 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sun, 31 May 2020 14:25:18 -0500 Subject: [Slackbuilds-users] update openfortivpn In-Reply-To: <557c16b8-780a-cdd7-6d1c-32da86930495@slackbuilds.org> References: <56b10d34c76ec34f3eefb9e79d696658@linux.com> <8b3aa6ab-8983-fb34-b990-abe962109745@slackbuilds.org> <0409b40f427aefeda53b5d134c238b84@linux.com> <557c16b8-780a-cdd7-6d1c-32da86930495@slackbuilds.org> Message-ID: On 2020-05-30 12:14 AM, Willy Sudiarto Raharjo wrote: >> I never received an email with a code. I see the SlackBuild was >> accepted >> already. Can I submit another .tar.gz with the correct tag? > > you can send another update after public update, but if it's just a > tag, > keep it until you have a new update coming or just tell me the new tag, > i can directly update it in the db The tag should be SBo in the SlackBuild and the build directory /tmp/SBo From poprocks at gmail.com Sun May 31 20:29:57 2020 From: poprocks at gmail.com (Logan Rathbone) Date: Sun, 31 May 2020 16:29:57 -0400 Subject: [Slackbuilds-users] Google chrome? In-Reply-To: References: <20200530004555.GB384@giustizia.org> Message-ID: <20200531202957.GB10102@darkstar.example.net> On Sat, May 30, 2020 at 05:30:30AM -0700, Rich Shepard wrote: > On Fri, 29 May 2020, Luiz Carlos Ramos wrote: > > > To add a suggestion, you may try Vivaldi, which is in SBo repository. I've > > been using it for some time and I'm pretty sure it has a recent version of > > Google Chrome under the hoods. > > Luiz, > > Thank you for the suggestion. I installed chrome from /extra and it had the > same issue as opera and chromium: the first thing ringcentral's web page did > was try to access a web page using xdg-open, but it could not find that URL. > A coding error by ringcentral. > > The application provides a link to download a client so I went that route. > Of course, Slackware was not among the choices, including 'other OS.' I > downloaded the fedora *.rpm, ran it through rpm2tgz, and installed the > client. This worked and allowed me to access the planning meeting even > though the other two participants and also long since left it. > > I'll use the downloaded ringcentral client for my presentation; no browser > needed. That's probably the best approach in any event. If ringcentral is anything like Zoom (I believe you said previously it was an offshoot), then the person hosting the conference has to actually enable a specific option to allow users to join via browser as an alternative to downloading the app. The checkbox you need to check off to enable that is surprisingly hard to find, and I've definitely encountered some hosts who have not checked it off, making it so that participants are required to download the app. Even when I as a host have checked that checkbox, I've noticed that on Firefox you can only join the conference through your browser for the video portion, and to join by audio you have to call the toll-free number of the service. I don't understand this at all. Isn't the whole point of implementing these technologies in HTML5 to avoid these kinds of interoperability issues? -Poprocks From rshepard at appl-ecosys.com Sun May 31 20:55:14 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 31 May 2020 13:55:14 -0700 (PDT) Subject: [Slackbuilds-users] Google chrome? In-Reply-To: <20200531202957.GB10102@darkstar.example.net> References: <20200530004555.GB384@giustizia.org> <20200531202957.GB10102@darkstar.example.net> Message-ID: On Sun, 31 May 2020, Logan Rathbone wrote: > That's probably the best approach in any event. If ringcentral is > anything like Zoom (I believe you said previously it was an offshoot), Logan, I must have mis-understood what the organization's tech said. RingCentral is a business cloud-based phone system that also offers video and audio conferencing. Zoom is also cloud based and offers webinars as well as video and audio conferencing; fewer options than RingCentral. As far as I'm concerned as a video conference presented the platform used is of no concern as long as it supports Slackware linux. > Even when I as a host have checked that checkbox, I've noticed that on > Firefox you can only join the conference through your browser for the > video portion, and to join by audio you have to call the toll-free number > of the service. Interesting. I just looked on the web for 'browser market share' and was surprised to see that Chrome has a 68.06% share while firefox is in second place with only a 8.21% share. While I suppose that I shouldn't be surprised, I am. > I don't understand this at all. Isn't the whole point of implementing > these technologies in HTML5 to avoid these kinds of interoperability > issues? I've asked this same question. If it's on the web who cares what browser running on what OS is used to host or participate in activities? Seems analagous to a gas station providing fuel to only Ford F-150s because they're the most popular vehicle. Their gasolene won't run any other engine. Thanks for your insights. Stay well, Rich