Finally solved virtuoso-ose building by disabling temporarily openssl-1.1.x as it has been built on slackware current.
Last difference is on libpthread-stubs.
Enclosed new scripts to achieve this goal.
Qscintilla and the new gnutls versions needed a patch for one (Qscintilla for two pass building) and modify the list4 for the other (gnutls).

Attached Files

	sfs-bootstrap-r9.txt (37.2 KB, 10 views)
	lists_generator_c-r4.txt (13.0 KB, 5 views)
	sfsbuild1-r4.txt (123.7 KB, 7 views)

1 members found this post helpful.

I'm actually not sure if virtuoso is really used for anything in -current. In 14.2 the last remaining use was to migrate to baloo, so it's possible that it's useless in -current unless someone is trying to update from 14.1 or older and actually cares about the semantic desktop database.

If anyone knows for sure I'd like to hear about it and/or see some references.

You heard me say in private that virtuoso-ose is no longer used ;-)
Indeed it was meant just for KDE4 and no longer needed after migrating the semantic search engine to baloo.
Look at Arch or Fedora, they orphaned the virtuoso package two years ago. And Arch is much alike Slackware in its package content.
Once you ditch KDE4 then virtuoso can go along.

3 members found this post helpful.

Trying to build virtuoso-ose has just been done for the completeness of the building, no prosletysm in favor or against the fact of keeping the package or not. By achieving the project of SFS I just want to learn how slackware works, nothing else. I'm just a hobbyist playing with slackware.

3 members found this post helpful.

Well, you (along with worsel and others) are hobbyists who have helped the project a great deal to get our source code in order. So thanks!

6 members found this post helpful.

Well, you (along with ...) are the pros who have made the project (slackware) great to get all your supporters happy. So thanks!

2 members found this post helpful.

I agree with nobodino. Thanks!

1 members found this post helpful.

Okay, I'm a little behind on this, but you youngsters are a bit fast for me:

I've finished going through Nobodino's programs of 20180708. Attached are some diffs
of the scripts, mostly just small tweaks. The file sorted.txt shows the difference between
a full build and what I obtained. Somewhere, somehow, I got something wrong in the setup
of SFS and a number of programs complained of not recognizing the xterm. Firefox and
Thunderbird didn't build but I'm not going back on this unless it shows up with the next
version of scripts.

Good job, Nobodino!

Attached Files

	lists_generator_c.patch.txt (515 Bytes, 10 views)
	sfs-bootstrap.patch.txt (9.3 KB, 11 views)
	sfsbuild1.patch.txt (2.5 KB, 9 views)
	sorted.txt (882 Bytes, 9 views)

Well, could you make the diff with the 24/07/2018 scripts which is my new reference now and your own scripts?
I'll see what I can do for the changes you propose.
--------------
# Known problems
____ adwaita-icon-theme-3.28.0-noarch-2
____ snownews-1.5.13_20180507-x86_64-1
____ virtuoso-ose-6.1.8-x86_64-9
____ xf86-video-s3virge-1.10.7-x86_64-4
____ xf86-video-tseng-1.2.5-x86_64-10
They are no more problems for now.
--------------
# Did not compile because it could not recognize the xterm.
____ mozilla-firefox-60.1.0esr-x86_64-1
____ mozilla-thunderbird-52.8.0-x86_64-1
it goes to the end only in kconsole
--------------
# Bash-completion is from extra
# jdk or jre is needed during compilation, normally from extra.
bash-completion-2.8-noarch-1
jdk-8u172-x86_64-1
I will make them appear in the diff
---------------
# Differ by download dates
kernel-firmware-20180717_8d69bab-noarch-1 kernel-firmware-20180606_d114732-noarch-1
Should be solved by building last current version.
---------------
# This is mislabeled
libpthread-stubs-0.4-x86_64-2 libpthread-stubs-0.4-noarch-2
If PV rebuilds that package it will be renamed as it should : libpthread-stubs-0.4-x86_64-2
---------------
I'll update list1 according to your suggestion (but I've not got that problem?)

Working on it. As soon as I'm sure it'll run, I'll send them. Transfering from your machine to mine
is always harder than it looks

great work, but I am still wondering why you do not put this stuff into a git repo and share it
it is nearly impossible to follow the patches / scripts you exchange in between.
not to mention all other stuff, like having no history, no others that can take a look at it, .....

1 members found this post helpful.

Sorry, but I don't know how to put it on a git repo, I'm not enough competent to do it.

if you need help for such a task, this can be done
it is not very complicated, has a lot of advantages, and once you know how easy it works you will ask yourself why not more eraly

Well, how do you want to proceed?

Remember, I'm not an informatician, I'm a hobbyist playing with SFS.

The most I know is:
- bash, but don't understand subtilities of some complex scripts,
- can clone a git repo and keep it update (git pull)
- can't create a new git project and keep it up to date...

I'll have some time till september 2018, after that till may 2019 I'll work far from home and won't have much time for the project.

Well, go to GitHub, register on it, then create a repository.

Then clone this (empty) repository locally, where you go "git add" for adding files and finally "git push" to publish your changes.

That's all in a nutshell. GitHub has great tutorials how to use GIT and their repositories, BTW...

PS. That GitHub is just my preferred platform. I worked since today with over 100 (private) repositories on GitHub. True, no one related to Slackware.