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.
Compiz-plugins-extra and experimental fail to build. In extra, build stops at libwallpaper.
...
In experimental build stops at atlantis and libsnowglobe.
...
All other plugins build fine.
Tracked this down to libxml2. Reverting to libxml2-2.10.4 eliminates the build problems. I'm not suggesting a reversion, only that the upstream compiz-plugins sources need upgraded. Not sure if compiz-reloaded is still maintained.
edit: Debian Bookworm solved the problem, but it ships with libxml2-2.9.14, suggesting compiz isn't the only affected system.
Tracked this down to libxml2. Reverting to libxml2-2.10.4 eliminates the build problems. I'm not suggesting a reversion, only that the upstream compiz-plugins sources need upgraded. Not sure if compiz-reloaded is still maintained.
edit: Debian Bookworm solved the problem, but it ships with libxml2-2.9.14, suggesting compiz isn't the only affected system.
df
hy DryFalls,
I'm not sure what's happening there but in this repository I patched compiz-plugins-extra and compiz-plugins-experimental to build with gcc 13.x in current and they build fine, it looks like there are no problems at all (regarding these two scripts) with the newer libxml2 in current...
Linphone 3.12.0 not compiling on -current - but latest version does compile
I hope it's ok to get in touch about this here. I am on Slackware -current 64bits downloaded 25 Dec 2023. Linphone using the scripts from Ponce's Github repo fails to compile with the following error:
Code:
</snip>(5.2.0) from Git and followed the instructions in the README file to compile and build it - and it seems to have worked out just fine on my -current install.
warning: Tag 'DOT_TRANSPARENT' at line 2389 of file 'ortp.doxygen' has become obsolete.
To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"
warning: argument 'a4wide' for option PAPER_TYPE is not a valid enum value
Using the default: a4!
/tmp/SBo/linphone-3.12.0/oRTP/include/ortp/b64.h:292: error: unable to resolve link to 'b64::b64_encode2' for \link command (warning treated as error, aborting now)
make[4]: *** [Makefile:1014: doc/html/index.html] Error 1
make[4]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[3]: *** [Makefile:572: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[2]: *** [Makefile:435: all] Error 2
make[2]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[1]: *** [Makefile:623: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/linphone-3.12.0'
make: *** [Makefile:551: all] Error 2
Failures:
linphone: linphone.SlackBuild return non-zero
I've done a bit of digging, and according to the link below it might be something to do with ortp and a "finicky doxygen configuration" (search for this phrase down the page linked below). There is a patch suggested on that page. I'm a little bit out of my depth as to the significance of all this though.
On the other hand - in case it helps - I tried cloning the latest Linphone from Git and followed the instructions in the README file to compile and build it - and it seems to have worked out just fine on my -current install. Strangely enough, if I download the latest released version (5.2.0) seems to be complaining about some missing directories - so somehow the latest current Linphone code is different than 5.2.0
I hope it's ok to get in touch about this here. I am on Slackware -current 64bits downloaded 25 Dec 2023. Linphone using the scripts from Ponce's Github repo fails to compile with the following error:
Code:
</snip>(5.2.0) from Git and followed the instructions in the README file to compile and build it - and it seems to have worked out just fine on my -current install.
warning: Tag 'DOT_TRANSPARENT' at line 2389 of file 'ortp.doxygen' has become obsolete.
To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"
warning: argument 'a4wide' for option PAPER_TYPE is not a valid enum value
Using the default: a4!
/tmp/SBo/linphone-3.12.0/oRTP/include/ortp/b64.h:292: error: unable to resolve link to 'b64::b64_encode2' for \link command (warning treated as error, aborting now)
make[4]: *** [Makefile:1014: doc/html/index.html] Error 1
make[4]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[3]: *** [Makefile:572: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[2]: *** [Makefile:435: all] Error 2
make[2]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[1]: *** [Makefile:623: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/linphone-3.12.0'
make: *** [Makefile:551: all] Error 2
Failures:
linphone: linphone.SlackBuild return non-zero
I've done a bit of digging, and according to the link below it might be something to do with ortp and a "finicky doxygen configuration" (search for this phrase down the page linked below). There is a patch suggested on that page. I'm a little bit out of my depth as to the significance of all this though.
On the other hand - in case it helps - I tried cloning the latest Linphone from Git and followed the instructions in the README file to compile and build it - and it seems to have worked out just fine on my -current install. Strangely enough, if I download the latest released version (5.2.0) seems to be complaining about some missing directories - so somehow the latest current Linphone code is different than 5.2.0
I think this is actually an issue of maintainer no more active as his latest contributions are from six years ago
in case of broken downloads (that affect also 15.0) you should contact directly the maintainer, and in case he's not responsive after a week, the slackbuilds-users mailing list...
in case of broken downloads (that affect also 15.0) you should contact directly the maintainer, and in case he's not responsive after a week, the slackbuilds-users mailing list...
I've just successfully compiled the amule-2.3.3, but running it yields this:
Code:
bash-5.2$ amule
2023-12-31 14:44:23: Initialising aMule 2.3.3 compiled with wxGTK2 v3.2.3 and Boost 1.84
2023-12-31 14:44:23: Checking if there is an instance already running...
2023-12-31 14:44:23: No other instances are running.
2023-12-31 14:44:23: ListenSocket: Ok.
Trace/breakpoint trap
bash-5.2$
Slackware-64 is current of course, and build script is from you, ponce.
Why is that?
I've just successfully compiled the amule-2.3.3, but running it yields this:
Code:
bash-5.2$ amule
2023-12-31 14:44:23: Initialising aMule 2.3.3 compiled with wxGTK2 v3.2.3 and Boost 1.84
2023-12-31 14:44:23: Checking if there is an instance already running...
2023-12-31 14:44:23: No other instances are running.
2023-12-31 14:44:23: ListenSocket: Ok.
Trace/breakpoint trap
bash-5.2$
Slackware-64 is current of course, and build script is from you, ponce.
Why is that?
hi brodo,
I suppose that happens because you haven't build it against wxGTK3-3.0.5 (that's its dependency on SBo).
Doubleconversion:
Doubleconversion actually builds ok but only provides the static library/archive. Problem is 2geom requires the shared lib resulting in failure to build inkscape.
Code:
[ 87%] Linking CXX executable ../bin/inkscape
/usr/bin/ld: warning: libdouble-conversion.so.3, needed by /usr/lib64/lib2geom.so.1.3.0, not found (try using -rpath or -rpath-link)
Erik's (alienbob) slackbuild produces a shared lib but no static. Substituting his recipe (modified for version) results in a clean build. Thing is, the README supplied in the source tarball suggests using scons which should produce both the shared and static libraries.
Doubleconversion:
Doubleconversion actually builds ok but only provides the static library/archive. Problem is 2geom requires the shared lib resulting in failure to build inkscape.
Code:
[ 87%] Linking CXX executable ../bin/inkscape
/usr/bin/ld: warning: libdouble-conversion.so.3, needed by /usr/lib64/lib2geom.so.1.3.0, not found (try using -rpath or -rpath-link)
no such problem here, as lib2geom.so.1.3.0 doesn't link against a shared libdouble-conversion: you can try removing the 2geom package from your system and rebuild it against a double-conversion package built from the script from SBo, then try against the inkscape build.
One test failure was fatal to the build.
Slipped in Erik's (alienbob) slackbuild (modified for version) and it built fine.
I cannot reproduce this too, here GraphicsMagick builds fine with no failed perl tests...
Code:
"/usr/bin/perl5.38.2" -MExtUtils::Command::MM -e 'cp_nonempty' -- Magick.bs blib/arch/auto/Graphics/Magick/Magick.bs 644
PERL_DL_NONLAZY=1 "/usr/bin/perl5.38.2" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/bzlib/*.t t/jng/*.t t/jp2/*.t t/jpeg/*.t t/png/*.t t/ps/*.t t/tiff/*.t t/ttf/*.t t/wmf/*.t t/x/*.t t/xfig/*.t t/zlib/*.t
t/blob.t .......... ok
t/bzlib/read.t .... ok
t/bzlib/write.t ... ok
t/composite.t ..... ok
t/filter.t ........ ok
t/getattribute.t .. ok
t/jng/read.t ...... ok
t/jng/write.t ..... ok
warning: skipping unknown tag type
warning: skipping unknown tag type
warning: skipping unknown tag type
warning: skipping unknown tag type
warning: skipping unknown tag type
warning: skipping unknown tag type
t/jp2/read.t ...... ok
t/jpeg/read.t ..... ok
t/jpeg/write.t .... ok
t/montage.t ....... ok
t/ping.t .......... ok
t/png/read-16.t ... ok
t/png/read.t ...... ok
t/png/write-16.t .. ok
t/png/write.t ..... ok
t/ps/read.t ....... ok
t/ps/write.t ...... ok
t/read.t .......... ok
t/setattribute.t .. ok
t/tiff/read.t ..... ok
t/tiff/write.t .... ok
t/ttf/read.t ...... ok
t/wmf/read.t ...... ok
t/write.t ......... ok
t/x/read.t ........ ok
t/x/write.t ....... ok
t/xfig/read.t ..... ok
t/zlib/read.t ..... ok
t/zlib/write.t .... ok
All tests successful.
Files=31, Tests=423, 3 wallclock secs ( 0.19 usr 0.07 sys + 8.11 cusr 0.97 csys = 9.34 CPU)
Result: PASS
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.