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.
Trying to build qt5 in -current x86_64 VM (fully updated this morning) fails during configuration with:
ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && libs.openssl' failed.
ERROR: Feature 'openssl' was enabled, but the pre-condition '!features.securetransport && (features.openssl-linked || libs.openssl_headers)' failed.
Seems the issue with boost and cmake is finally fixed in current now and -DBoost_NO_BOOST_CMAKE=ON can be removed from the many build scripts it has been added to.
Seems the issue with boost and cmake is finally fixed in current now and -DBoost_NO_BOOST_CMAKE=ON can be removed from the many build scripts it has been added to.
seems like this is true only for some of the build scripts: innoextract, for example, still needs it.
could it be you are not using the SlackBuild version that is in the repository?
because Ole-André Rodlie contributed to it a patch to have openssl-1.1.x support in qt-5.9.8
could it be you are not using the SlackBuild version that is in the repository?
because Ole-André Rodlie contributed to it a patch to have openssl-1.1.x support in qt-5.9.8
Yes, that was the problem. I had a remote to your repo OK but had master checked out instead of current. I just fixed that and tried again and it has now proceeded well past configuration and is compiling away.
Hi to all, cant build m64py (alongside other python-dependent slackbuilds) on my x86-64 -current, it fails with this output:
Code:
m64py-0.2.2/src/m64py/core/defs.py
m64py-0.2.2/src/m64py/core/vidext.py
running install
running build
running build_qt
Traceback (most recent call last):
File "setup.py", line 322, in <module>
("share/applications", ["xdg/m64py.desktop"]),
File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib64/python2.7/distutils/command/install.py", line 563, in run
self.run_command('build')
File "/usr/lib64/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "setup.py", line 287, in run
self.run_command("build_qt")
File "/usr/lib64/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "setup.py", line 62, in run
self.compile_ui(join(dirpath, filename))
File "setup.py", line 38, in compile_ui
uic.compileUi(ui_file, fp, from_imports = True)
File "/usr/lib64/python2.7/site-packages/PyQt4/uic/__init__.py", line 173, in compileUi
winfo = compiler.UICompiler().compileUi(uifile, pyfile, from_imports, resource_suffix)
File "/usr/lib64/python2.7/site-packages/PyQt4/uic/Compiler/compiler.py", line 55, in __init__
CompilerCreatorPolicy())
File "/usr/lib64/python2.7/site-packages/PyQt4/uic/uiparser.py", line 183, in __init__
self.factory = QObjectCreator(creatorPolicy)
File "/usr/lib64/python2.7/site-packages/PyQt4/uic/objcreator.py", line 97, in __init__
self._cwFilters.append(plugin_locals["getFilter"]())
File "<string>", line 22, in getFilter
ValueError: PyCapsule_GetPointer called with incorrect name
As a side note, python3-sip which is required by it (and, by my very limited "make" expirience seems to cause the fail) doesn't exist in the ponce-git sbo repo
As a side note, python3-sip which is required by it (and, by my very limited "make" expirience seems to cause the fail) doesn't exist in the ponce-git sbo repo
these errors, differently by the first thing you reported, are probably caused by your "frankestein" installation that you described also in the other topic you opened, as everything builds fine here.
I suggest you keep your discussion there as this topic is not the proper place to debug this: please read the first post of this topic, in particular this part
Quote:
Originally Posted by ponce
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.
these errors, differently by the first thing you reported, are probably caused by your "frankestein" installation that you described also in the other topic you opened, as everything builds fine here.
I suggest you keep your discussion there as this topic is not the proper place to debug this: please read the first post of this topic, in particular this part
...that is clearly not the installation you got.
? what do you mean by frankinstain-build?
it is just
slackware64-current +
kernel 5.2.10 + (after the original mistake of building it before multilib, I've rebuild it, fixing all kernel-build related problems)
multilib +
sbotools (removed sbopkg and rebuilt/reinstalled ALL Sbo packages)
I highly doubt that's far away to what most people have in this day and age, no?
Do you mean that on this thread only PURE slackware64 (without multilib) is considered?
please, I invite you again to read the first post of the topic: this topic is dedicated to packages that doesn't build on current for everyone that use it in its standard installation, issues present on custom installations (including kernels and multilib) shouldn't be reported in this topic at all if they are not verified first on a clean and full installation of the latest Slackware current.
Quote:
Originally Posted by the first post
SBo supports building its own scripts on clean slackware full installation: we would go crazy trying to support any setup out there that we have not tested ourself for everyone of our 5000+ scripts.
this policy applies also on this humble, unofficial, attempt to let SBo things build on current.
following this it should be obvious that issues related to custom installs shouldn't belong in this thread: please open another one to discuss such things, also if you are not sure if the error you got is related but you are aware that your setup is a non-standard one.
describe your problem here only if you are absolutely sure that it has nothing to do with your custom setup.
FYI (but unrelated to this thread: please discuss this elsewhere, I won't reply about it again here, sorry), vhba-module and clamav build fine here on a slackware64-current multilib with kernel 5.2.x, so I suppose there's also something else different in your setup.
but yes, multilib isn't officially supported by SBo (see FAQ #18).
the suggestion I can give is to create a virtual machine/container/chroot (you can use any method you prefer, I use qemu here) with a pristine Slackware current installation, build your packages there (you can also do one for 64bit and another for 32bit, if you need to build 32bit packages too), and see if the errors you got are replicated there: if they are not just use the packages you build on your virtual machines also on your physical ones.
please, I invite you again to read the first post of the topic: this topic is dedicated to packages that doesn't build on current for everyone that use it in its standard installation, issues present on custom installations (including kernels and multilib) shouldn't be reported in this topic at all if they are not verified first on a clean and full installation of the latest Slackware current.
FYI (but unrelated to this thread: please discuss this elsewhere, I won't reply about it again here, sorry), vhba-module and clamav build fine here on a slackware64-current multilib with kernel 5.2.x, so I suppose there's also something else different in your setup.
So, only stock slackware, with no modification at all, on this thread, I missed that, sorry.
FWIW the module-compiling problems have been solved, as I said, by recompiling the kernel with multilib-gcc, it was failing before because I compiled it in pure64 then installed multilib after, that was the problem, but it has been solved, vhba and steamos-xpad compiled fine afterwards
My only real problems are ncurses and python, both of which ships with the default slackware installation...
Quote:
but yes, multilib isn't officially supported by SBo (see FAQ #18).
the suggestion I can give is to create a virtual machine/container/chroot (you can use any method you prefer, I use qemu here) with a pristine Slackware current installation, build your packages there (you can also do one for 64bit and another for 32bit, if you need to build 32bit packages too), and see if the errors you got are replicated there: if they are not just use the packages you build on your virtual machines also on your physical ones.
I'll try and report the results, then as a double check, uninstall the package, install multilib and retry compiling it in the virtual enviroment.
In case it's a multilib related problem, however, to whom shall I report?
PS thanks again for all the effort you and the others here put on slackware
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
m64py
