SBo scripts not building on current (read 1st post, pls)

ponce · 01-08-2019, 03:17 PM

Quote:

Originally Posted by giomat

perhaps i should just email the mantainer since the build failure is not really related to -current.

yes, please email him, thanks!

RadicalDreamer · 01-12-2019, 10:12 AM

ngspice-30 says docs aren't found so I commented out

Code:

#rm -rf $PRGNAM-doc-$VERSION
#tar xvf $CWD/$PRGNAM-doc-$VERSION.tar.gz
#(cd $PRGNAM-doc-$VERSION
#    chown -R root:root .
#    find -L . \
#    \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 5
11 \) \
#    -exec chmod 755 {} \; -o \
#    \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
#    -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
#)

to get it to build.

ponce · 01-12-2019, 10:31 AM

Quote:

Originally Posted by RadicalDreamer

ngspice-30 says docs aren't found so I commented out

Code:

#rm -rf $PRGNAM-doc-$VERSION
#tar xvf $CWD/$PRGNAM-doc-$VERSION.tar.gz
#(cd $PRGNAM-doc-$VERSION
#    chown -R root:root .
#    find -L . \
#    \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 5
11 \) \
#    -exec chmod 755 {} \; -o \
#    \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
#    -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
#)

to get it to build.

this is not current specific: it has been reported on the slackbuilds-users mailing list

https://lists.slackbuilds.org/piperm...ry/022598.html

and the maintainer has already submitted a fix that will most probably go in the next public update.

sombragris · 01-12-2019, 11:24 AM

Regarding the new gambas3:

1. There is a MD5 sum mismatch (reported at the SBo mailing list since it's not specific to -current).

2. In my setup, build fails and can be made to successfully finish only when adding --enable-sqlite2=no to the ./configure parameters.

sombragris · 01-15-2019, 03:41 PM

aegisub cannot be built on -current. Last part of build:

Code:

g++ -MMD -MP -I/tmp/SBo/aegisub-3.2.2/libaegisub/include -I/tmp/SBo/aegisub-3.2.2/ -fPIC -I/usr/include -DBOOST_SYSTEM_NO_DEPRECATED -I/tmp/SBo/aegisub-3.2.2/vendor/luajit/include -O2 -fPIC -Wall -Wextra -Wno-unused-parameter -fno-strict-aliasing -pipe -g -std=c++11 -Wno-c++11-narrowing -Wno-unused-local-typedefs -O3  -include /tmp/SBo/aegisub-3.2.2/libaegisub/lagi_pre.h   -c -o /tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.o /tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp
/tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp: In lambda function:
/tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp:39:12: error: ‘BreakIterator’ has not been declared
   bi.reset(BreakIterator::createCharacterInstance(Locale::getDefault(), status));
            ^~~~~~~~~~~~~
/tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp:39:51: error: ‘Locale’ has not been declared
   bi.reset(BreakIterator::createCharacterInstance(Locale::getDefault(), status));
                                                   ^~~~~~
/tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp: In function ‘size_t {anonymous}::count_in_range(Iterator, Iterator, int)’:
/tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp:61:46: error: ‘BreakIterator’ has not been declared
  for (auto end = character_bi.next(); end != BreakIterator::DONE; pos = end, end = character_bi.next()) {
                                              ^~~~~~~~~~~~~
/tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp: In function ‘size_t agi::IndexOfCharacter(const string&, size_t)’:
/tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.cpp:146:14: error: ‘BreakIterator’ has not been declared
   if (end == BreakIterator::DONE)
              ^~~~~~~~~~~~~
At global scope:
cc1plus: warning: unrecognized command line option ‘-Wno-c++11-narrowing’
make: *** [Makefile.target:100: /tmp/SBo/aegisub-3.2.2/libaegisub/common/character_count.o] Error 1

willysr · 01-15-2019, 04:33 PM

Quote:

Originally Posted by sombragris

aegisub cannot be built on -current. Last part of build:

Try this commit

I had to add another patch for latest boost and some changes for ICU as well

sombragris · 01-16-2019, 06:49 AM

Quote:

Originally Posted by willysr

Try this commit

I had to add another patch for latest boost and some changes for ICU as well

Thanks willy! It worked. Now it builds OK.

qunying · 01-17-2019, 01:29 PM

xml-security-c does not compiled due to the patch is not compatible.
After removing the patch, it compiled fine.

Then I look at the upstream http://santuario.apache.org/cindex.html, it seems the current version in repo will cause application crash, it is better to upgrade to latest 2.0.2.

ponce · 01-17-2019, 02:15 PM

Quote:

Originally Posted by qunying

xml-security-c does not compiled due to the patch is not compatible.
After removing the patch, it compiled fine.

thanks for reporting it!

Quote:

Then I look at the upstream http://santuario.apache.org/cindex.html, it seems the current version in repo will cause application crash, it is better to upgrade to latest 2.0.2.

you better write about this to the maintainer...

av2zeal · 01-22-2019, 08:29 PM

Hello,

Can anyone confirm that the -current discord SBo works? The recent update (0.0.8) requires a new package. I was able to version bump Jeremy's SBo, which incidentally is the same SBo as ponce's repo. Everything seems to build properly, but it hangs at "starting". I have tried both via GUI and CLI, with neither showing any errors. I emailed Jeremy and he has a local build for 14.2, but not -current. He suggested that I post here and request help. I know that -current supports libc++ through the most recent versions of glibc, and a quick search for dependencies turned up the AUR. I have tried clearing my discord folder from .config and I am unable to locate anything discord related in .cache. I am able to use the web app in the meantime, but this has drawbacks. Any help is appreciated.

Slackware64-current
4.19.13
Xfce

ponce · 01-23-2019, 12:43 AM

Quote:

Originally Posted by av2zeal

Hello,

Can anyone confirm that the -current discord SBo works? The recent update (0.0.8) requires a new package. I was able to version bump Jeremy's SBo, which incidentally is the same SBo as ponce's repo. Everything seems to build properly, but it hangs at "starting". I have tried both via GUI and CLI, with neither showing any errors. I emailed Jeremy and he has a local build for 14.2, but not -current. He suggested that I post here and request help. I know that -current supports libc++ through the most recent versions of glibc, and a quick search for dependencies turned up the AUR. I have tried clearing my discord folder from .config and I am unable to locate anything discord related in .cache. I am able to use the web app in the meantime, but this has drawbacks. Any help is appreciated.

Slackware64-current
4.19.13
Xfce

I just tested it and what happens here doesn't seem to be current-specific, it should happen also on stable: when you launch discord it just want to be updated to 0.0.8 or it won't start (report this to the maintainer), should happen the same also on stable as this is a binary repackaging.
when I version-bump the SlackBuild to 0.0.8 it starts fine, it spits just an error when the GUI is loaded but it seems to function neverthless.
I'm not sure what's happening there, libc++ shouldn't matter as now is included in llvm shipped with current.

bassmadrigal · 01-23-2019, 10:29 AM

Quote:

Originally Posted by ponce

I just tested it and what happens here doesn't seem to be current-specific, it should happen also on stable: when you launch discord it just want to be updated to 0.0.8 or it won't start (report this to the maintainer), should happen the same also on stable as this is a binary repackaging.
when I version-bump the SlackBuild to 0.0.8 it starts fine, it spits just an error when the GUI is loaded but it seems to function neverthless.
I'm not sure what's happening there, libc++ shouldn't matter as now is included in llvm shipped with current.

I am the maintainer of discord and 0.0.8 works fine for me on 14.2. I'm not seeing the same issues that av2zeal mentioned when running -current. I was able to log in and have my chats come up. I sent in a PR on GitHub for the version bump to 0.0.8 and it was merged a few hours ago (simple version bump).

I didn't see any error messages on AUR either, although from AUR's changelog, discord did update from gtk2 to gtk3, but Slackware should be unaffected with that since we ship both.

av2zeal · 01-23-2019, 11:45 AM

Thank you for confirming ponce and bassmadrigal! It must be somethig on my end then. I'm going to do a clean 64-current install of my system.

qunying · 01-23-2019, 06:54 PM

SimGear compile error on current. Got same error with 2018.3.1

/tmp/SBo/simgear-2018.2.2/simgear/nasal/cppbind/NasalHash.hxx:290:69: required from here
/usr/include/boost/iterator/iterator_facade.hpp:901:3: error: no type named ‘type’ in ‘struct boost::iterators::detail::enable_if_interoperable<nasal::Hash::Iterator<true>, nasal::Hash::Iterator<false>, bool>’
make[2]: *** [simgear/CMakeFiles/SimGearCore.dir/build.make:1480: simgear/CMakeFiles/SimGearCore.dir/nasal/cppbind/NasalContext.cxx.o] Error 1

https://forum.flightgear.org/viewtopic.php?p=339977
Upstream reply with back out of boost 1.69

mralk3 · 01-24-2019, 06:27 PM

arc-theme fails to build on the latest -current. I believe a version bump is all that is required.

Code:

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: creating directory build-aux
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:12: installing 'build-aux/install-sh'
configure.ac:12: installing 'build-aux/missing'
autoreconf: Leaving directory `.'
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
configure: error: Invalid GNOME version: 3.24

It looks like Debian is using the following repo as upstream:

https://github.com/nicohood/arc-theme