Hi all,

from the last moving of kdevelop and kdev-php from "application-extra" to "applications" (Dec 10th 2021), kdev-php does no more build without the required kdevelop-pg-qt left on "application-extra".

I think we should move kdevelop-pg-qt as well into "applications" and "all-packaged-applications".

Luca

Is that not more, for a plasma forum than a Slackware?

The compilation order for KDE/plasma modules is Slackware-specific, and the last Dec 10th 2021 2 modules (kdevelop and kdev-php) were moved earlier in the list, forgetting to move kdevelop-pg-qt that is needed by kdev-php.

The problem arises only if you build KDE from scratch (as I do for riscv64 Slackware porting). I suppose the issue was not detected because KDE compilation in Slackware is usually "incremental", and on Dec 10th both kdev-php and kdevelop-pg-qt were already compiled to the latest versions (2.2.1 [Feb 9th 2020] and 21.12.0 [Dec 3rd 2021] respectively), so no one could detect the compilation order issue.

2 members found this post helpful.

As @lucabon mentioned. This is Slackware specific, build order is determined in the source/kde build tree.

@lucabon, as I'm the Slackware From Scratch maintainer for x86_64 and x86 follow that link, you may find your answer:

https://raw.githubusercontent.com/no.../kde/build_kde

2 members found this post helpful.

Thanks! From your build script, we can confirm that kdevelop-pg-qt should be built before kdev-php.

I also built Slackware from scratch for some platform (https://bonslack.bonnix.org/bootstrap/), but never really automated it. I prefer to keep as much as possible the original Slackware build scripts, included the KDE module order list.
But your build scripts are really useful to "make-up" the original build scripts. Thanks again!

Luca

2 members found this post helpful.

In the "https://bonslack.bonnix.org/bootstrap/" not see "README" instructions, "bootstrap" can you write a instructions,
thank you

You must have Slackware host system (I used x86-64, but any other system/CPU could be used) with exactly the same Slackware version you want to install, due to gcc/glibc and other libraries dependency.

Then, get the environment for the target processor (e.g., for RISCV64, get envriscv64.sh) and do ". envriscv64.sh".

The - already patched, especially with "*_bootstrap.diff" - Slackware tree should be in the subdir "slackware" (also a link is OK).

Then, simply run "./stage1.sh": it will generate the directory "rootfs<arch>" that should suffice to boot the system.

In "stage 2" (compile packages under running system), you have to follow instructions inside the file "scripts/installation_order.txt". Especially at the beginning, some packages should be manually built, but after you can run "batch_compile2.sh installation_order.txt" to automate the process.

You can find other instructions here (where I download the "stage1.sh" script): https://alien.slackbook.org/blog/archive/armport/

Luca

Ok, thank you
Thank you for your reply