SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The most current linuxsampler-2.2.0 builds, the one in ponce's current-git, 1.7.2, stalls.
Also this needs an update of dependency libgig to version 0.4.3 (now 0.4.2)
tlib/common/object.cxx
[CC] ptlib/common/osutils.cxx
ptlib/common/contain.cxx: In member function ‘void PString::Delete(PINDEX, PINDEX)’:
ptlib/common/contain.cxx:1164:19: warning: ISO C++17 does not allow ‘register’ storage class specifier [-Wregister]
1164 | register PINDEX slen = GetLength();
| ^~~~
ptlib/common/contain.cxx: In member function ‘PString PString::operator()(PINDEX, PINDEX) const’:
ptlib/common/contain.cxx:1181:19: warning: ISO C++17 does not allow ‘register’ storage class specifier [-Wregister]
1181 | register PINDEX len = GetLength();
| ^~~
ptlib/common/contain.cxx: In member function ‘PINDEX PString::Find(char, PINDEX) const’:
ptlib/common/contain.cxx:1317:19: warning: ISO C++17 does not allow ‘register’ storage class specifier [-Wregister]
1317 | register PINDEX len = GetLength();
| ^~~
ptlib/common/contain.cxx: In member function ‘void PString::Splice(const char*, PINDEX, PINDEX)’:
ptlib/common/contain.cxx:1533:19: warning: ISO C++17 does not allow ‘register’ storage class specifier [-Wregister]
1533 | register PINDEX slen = GetLength();
| ^~~~
ptlib/common/object.cxx:953:37: error: ISO C++17 does not allow dynamic exception specifications
953 | void * operator new[](size_t nSize) throw (std::bad_alloc)
| ^~~~~
make[2]: *** [../make/common.mak:96: /tmp/SBo/ptlib-2.10.11/lib_linux_x86_64/obj/object.o] Errore 1
make[2]: *** Attesa per i processi non terminati....
make[2]: uscita dalla directory «/tmp/SBo/ptlib-2.10.11/src»
make[1]: *** [../make/common.mak:292: optshared] Errore 2
make[1]: uscita dalla directory «/tmp/SBo/ptlib-2.10.11/src»
make: *** [Makefile:91: optshared] Errore 2
Upstream is no longer developing this library, so i think it should be removed in the future
Hi Willy, this removal/replacement in the future, can it be done already when we run in outdated packages for which an alternative is available?
For example, I maintain PDFShuffler, which is python2 only. A direct, python3-based replacement, PDF Arranger (plus PikePDF), would preferably take its place in current. I've got build-scripts ready (see my 'some other SlackBuilds' github link). PDFArranger works great at my end..
Hi Willy, this removal/replacement in the future, can it be done already when we run in outdated packages for which an alternative is available?
For example, I maintain PDFShuffler, which is python2 only. A direct, python3-based replacement, PDF Arranger (plus PikePDF), would preferably take its place in current. I've got build-scripts ready (see my 'some other SlackBuilds' github link). PDFArranger works great at my end..
It looks like PDFShuffler is actually Python3 compatible, but it is not maintained any more (last version 0.7)
The non-maintenance was the (main) issue for developing pdfarranger (from their README):
Quote:
PDF Arranger is a fork of Konstantinos Poulios’s pdfshuffler (see Savannah or Sourceforge). It’s a humble attempt to make the project a bit more active.
You're right pdfshuffler (and the library it depends on, pyPDF2) can be build with python3.10, but it does not run:
Quote:
bash-5.1$ pdfshuffler
Traceback (most recent call last):
File "/usr/bin/pdfshuffler", line 30, in <module>
from pdfshuffler.pdfshuffler import main
File "/usr/lib64/python3.10/site-packages/pdfshuffler/pdfshuffler.py", line 104
os.chmod(self.tmp_dir, 0700)
^
SyntaxError: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers
bash-5.1$
And, yes (in my opinion), the python3 compliant pdfarranger seems the way to go.
Hi Willy, this removal/replacement in the future, can it be done already when we run in outdated packages for which an alternative is available?
For example, I maintain PDFShuffler, which is python2 only. A direct, python3-based replacement, PDF Arranger (plus PikePDF), would preferably take its place in current. I've got build-scripts ready (see my 'some other SlackBuilds' github link). PDFArranger works great at my end..
if the package is no longer maintained by upstream nor any volunteer in SBo stepping up to take care of the script (plus it's failing to build), then we should remove it.
Hi Willy, this removal/replacement in the future, can it be done already when we run in outdated packages for which an alternative is available?
For example, I maintain PDFShuffler, which is python2 only. A direct, python3-based replacement, PDF Arranger (plus PikePDF), would preferably take its place in current. I've got build-scripts ready (see my 'some other SlackBuilds' github link). PDFArranger works great at my end..
I switched to pdfarranger Nov 11, 2020 from pdfsuffler. Working great here too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.