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.
@Nille_kungen I'm very sorry, but I think I gave you bad advice by mistake.
Upon testing a compat32 pkg-config package I noticed my "/usr/lib/pkgconfig" directory vanished, I then noticed the doinst.sh in for the compat32 package...
That is unfortunate...I'll have to try to reproduce this later. Since SBo does not officially support multilib I only tested it with clean 32-bit and 64-bit installs before submitting it and missed this problem.
In the meantime you should be able to get it to work with using pkgconf instead of pkg-config which works here at least.
Please make sure to read the README if you follow this route as it replaces the default pkg-config package.
I know that multilib isn't officially supported but this is one of the few packages that is very likely to be used with multilib.
I need to rest my mind a bit from this right now but i might try pkgconf later, it starting to give me a headache.
I'm very pleased for your help.
I agree that this should work, but there are some details I didn't foresee with pkg-config in a multilib environment. On the other hand supporting this with pkgconf was trivial...
Here are the steps I took to build wine-nine-standalone with pkg-config on a multilib system.
Code:
wget http://mirrors.slackware.com/slackware/slackware-current/slackware/d/pkg-config-0.29.2-i586-2.txz
convertpkg -i pkg-config-0.29.2-i586-2.txz
mkdir tmpdir
mv pkg-config-compat32-0.29.2-x86_64-2compat32.txz tmpdir/
cd tmpdir
explodepkg pkg-config-compat32-0.29.2-x86_64-2compat32.txz
rm install/doinst.sh pkg-config-compat32-0.29.2-x86_64-2compat32.txz
mv usr/bin/32/i586-slackware-linux-gnu-pkg-config usr/bin/i586-slackware-linux-gnu-pkg-config
makepkg -l y -c n ../pkg-config-compat32-0.29.2-x86_64-2compat32.txz
installpkg ../pkg-config-compat32-0.29.2-x86_64-2compat32.txz
At this point providing a fixed compat32 pkg-config package is out of my hands and out of scope for this thread. I let Alien Bob know about this in his blog and we'll see what happens.
In the meantime it might be easier to just use pkgconf where a compat32 package is not needed. I personally haven't noticed any regressions in regards to pkg-config and it should be a drop in replacement.
@orbea I uninstalled pkg-config and installed pkgconf then reinstalled multilib to fix what was broken by the bad 32-bit pkg-config then i was able to build wine-nine-standalone-0.4.
pkgconf did the trick for me.
I don't need to export PATH="/usr/bin/32:$PATH" for it to build, it just works.
Last edited by Nille_kungen; 04-27-2019 at 07:22 PM.
Since the upgrade in Slackware64-current to swig-4 (and gcc-9.1), compilation of ViennaRNA still works but the creation of the python-3 module halts and breaks the process (https://github.com/ViennaRNA/ViennaRNA/issues/54)
FreeImage-3.17.0 does not build with either gcc9 or clang8, the newer 3.18.0 builds with the existing script after the patch which does not apply anymore is removed.
FreeImage-3.17.0 does not build with either gcc9 or clang8, the newer 3.18.0 builds with the existing script after the patch which does not apply anymore is removed.
what's wrong with boost in -current? A lot of stuff breaks. For example ncbi-blast+ or the Genome Workbench, for which I am considering to submit a SlackBuild...
it may be that they are just incompatible with the newer 1.70 version: if you try to build ncbi-blast+ you got this in the configure output
Code:
checking Boost version... 1_70
configure: WARNING: Untested Boost version; may prove incompatible.
configure: WARNING: If so, please re-run this script with the flag --without-boost.
so you can try adding that configure flag, it will most probably help.
I've not tested the genome workbench myself but it might be something similar...
yes, ncbi-blast+ builds fine with the --without-boost option. However, it seems that boost is needed for the Genome Workbench GUI...
if I were you I would try to submit a bug report to the gbench developers, as their configure seem to have a "--without-boost" option available: if it doesn't work/won't build with the newer boost, it's better if they are aware about it...
if I were you I would try to submit a bug report to the gbench developers, as their configure seem to have a "--without-boost" option available: if it doesn't work/won't build with the newer boost, it's better if they are aware about it...
yep
however, i will first try to find time to update my scripts already part of SBo, before I test build/submit anything new
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
