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.
I don't use SBO but this may be useful to those building podofo. I upgraded podofo to 0.9.8, my last build was with 0.9.7 on April 18, 2022, it was successful.
My build attempts all failed with 0.9.8 and also 0.9.7.
I don't use SBO but this may be useful to those building podofo. I upgraded podofo to 0.9.8, my last build was with 0.9.7 on April 18, 2022, it was successful.
My build attempts all failed with 0.9.8 and also 0.9.7.
Hi, this is a recurrent issue in ITK when GCC is updated to a new major/minor release. The current slackbuild does not support versions more recent than 11.x, so in current we have to edit the internal patch.
This is the updated patch that adds the support to GCC 12.0 and 12.1 (tested just now):
configure: error: Package requirements (lowdown >= 0.9.0) were not met:
No package 'lowdown' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LOWDOWN_CFLAGS
and LOWDOWN_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Failures:
nix: nix.SlackBuild return non-zero
rootcosmos:~# ls -l /var/log/packages/lowdown-0.11.2-x86_64-1_SBo
-rw-r--r-- 1 root root 1072 Jul 24 18:25 /var/log/packages/lowdown-0.11.2-x86_64-1_SBo
Pouria Rezaei wrote on 2022-7-28:
Quote:
Oh, huh
Thanks for letting me know
I'll check it soon
Lately same result in Slackware64 15.1-current chroot with nothing but build tools and SlackBuilds/dependencies I try (built in chroot if available).
Lately same result in Slackware64 15.1-current chroot with nothing but build tools and SlackBuilds/dependencies I try (built in chroot if available).
Hi David,
the issue you are reporting applies also to Slackware 15.0 so you shouldn't report it in this topic but just to the maintainer (like you have already done): I'll quote from the first post (please follow what's written there)
Quote:
Originally Posted by ponce
so, what is this thread for?
risking to be repetitive, report issues here only if you have already tried the scripts from our repository and they won't build on a clean and full installation of Slackware current.
also, if you want to report a problem that applies also to Slackware stable this is not the right place, this topic is current-specific.
if you think a script on SBo shows issues (broken download, not building, etc.) on such platform write to the maintainer and wait some days for an answer (a week should be fine): if the maintainer isn't responsive after this time please post the same thing by mail to the slackbuilds-users mailing list putting the maintainer in cc
to be clear this means that before reporting issues in this topic you should test whatever you are about to report on Slackware stable too: if you are not sure that what you are reporting applies to Slackware stable or not (because, for example, you have no way to test it for one reason or another) please don't report in this topic and open a new one instead, thanks.
the reasoning behind this is simple: there's nothing to fix in this repository if something is already broken on SBo (of which this repository is just a fork), so the issue should be handled there.
sbopkg -s pdftk
NOTE: Starting with Slackware 15.0, pdftk compilation requires SBo
gcc-5 because gcc-java was dropped from the GNU Compiler Collection
as of gcc-7. Don't forget to source /etc/profile.d/gcc5.sh before
starting to build this, like:
. /etc/profile.d/gcc5.sh
I got this notice, but /etc/profile.d/gcc5.sh does not exist. I assumed (maybe a "wrong assumption") this could be done somewhere during compilation process, so I continue with:
Code:
sqg -p pdftk
sbopkg -i pdftk
and after a very long compilation process, I got:
Code:
In file included from /usr/include/linux/fs.h:19:0,
from ../../../../gcc-5.5.0/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:63:
/usr/include/linux/mount.h:95:6: error: multiple definition of ‘enum fsconfig_command’
enum fsconfig_command {
^
In file included from ../../../../gcc-5.5.0/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:51:0:
/usr/include/sys/mount.h:189:6: note: previous definition here
enum fsconfig_command
^
In file included from /usr/include/linux/fs.h:19:0,
from ../../../../gcc-5.5.0/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:63:
/usr/include/linux/mount.h:129:8: error: redefinition of ‘struct mount_attr’
struct mount_attr {
^
In file included from ../../../../gcc-5.5.0/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:51:0:
/usr/include/sys/mount.h:161:8: error: previous definition of ‘struct mount_attr’
struct mount_attr
^
make[4]: *** [Makefile:449: sanitizer_platform_limits_posix.lo] Error 1
make[4]: Leaving directory '/tmp/SBo/gcc.build.lnx/x86_64-slackware-linux/libsanitizer/sanitizer_common'
make[3]: *** [Makefile:437: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/gcc.build.lnx/x86_64-slackware-linux/libsanitizer'
make[2]: *** [Makefile:307: all] Error 2
make[2]: Leaving directory '/tmp/SBo/gcc.build.lnx/x86_64-slackware-linux/libsanitizer'
make[1]: *** [Makefile:13534: all-target-libsanitizer] Error 2
make[1]: Leaving directory '/tmp/SBo/gcc.build.lnx'
make: *** [Makefile:21415: bootstrap] Error 2
ln: failed to create symbolic link '/tmp/SBo/package-gcc5/usr/lib64/': No such file or directory
gcc5:
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.
I discovered qpdf on my -current install, so I can live without pdftk.
Anyway I reported this in order to know your comments and advice.
Thanks in advance for your traditional and kind help.
the file to source (/etc/profile.d/gcc5.sh) will be there only once you have installed the dependency gcc5 on your system, not before: this means that, if you are using sbopkg, you have to build and install gcc5, source the interested file and then build pdftk, in two different sbopkg invocations.
but, as you have discovered yourself, there's a problem building gcc5 because of the new glibc-2.36 in current: I just patched in git, it will go in at the next update
the file to source (/etc/profile.d/gcc5.sh) will be there only once you have installed the dependency gcc5 on your system, not before: this means that, if you are using sbopkg, you have to build and install gcc5, source the interested file and then build pdftk, in two different sbopkg invocations.
but, as you have discovered yourself, there's a problem building gcc5 because of the new glibc-2.36 in current: I just patched in git, it will go in at the next update
just build the latest revision of the Version15x svn branch, it already contains all the needed patches for the latest poppler: you can clone it yourself from their svn
Code:
svn co svn://scribus.net/branches/Version15x/Scribus svn-scribus15x
...
Compiling with new poppler works with latest svn version (r25140) of scribus:
Quote:
Package scribus-r25087-x86_64-1ponce upgraded with new package /tmp/scribus-r25140-x86_64-1_SBo.tgz
For inkscape this is available:
Code:
# patchfile is saved-as https://gitlab.com/inkscape/inkscape/-/merge_requests/4719.diff
# see https://gitlab.com/inkscape/inkscape/-/merge_requests/4719
patch -p1 < $CWD/poppler-2209_4719.diff.txt
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
nix?
