Probably because you have a custom installation?
AlienBOB test that build on pure slackware-current

True. Though the only possible variables are ConsoleKit2, Wayland, Mesa, a rebuilt Xorg, and whatever else I pulled into my Slackworks repository.

Other than that things have been pretty vanilla. I did have to uninstall mono and gtk-sharp for a few packages in /deps.

You're being your vague self again. Talking a lot but nothing to back it up. If you could at least show the errors you would get, that would allow people to think for you and help, right?
On Slackware-current, of all the official KDE packages you would only need to keep (or install if you have no KDE 4.14.3 package at all) libktorrent, the rest is not needed or will be in the way when you compile Plasma 5.
Then it is a matter of building the deps packages, logging out and back in (qt5 installs a profile script), running "./KDE.SlackBuild" and wait a long time.

Of course I work with a full install of Slackware-current.

1 members found this post helpful.

Vague?! Having to wait over 2 hours to get past several libraries then have a failure is vague? All I asked for was the build order so I can check as I go instead of waiting a whole long time for the failure only to have to start all over each failure.

It's hard to be vague when you have little to go on without a build order to break things down to check as you go. I'm not asking for much, but when people have a problem, it's almost like pulling teeth to get an answer sometimes, and no Eric, I'm not being critical of your work, if that was implied.

2 members found this post helpful.

As far as I can tell, "several libraries" definitely sounds vague.

1 members found this post helpful.

Let me try to dumb it down some...

All I asked for was the specific build order so I can control the entire package build to actually find out where it failed and at what exact package.

It that too much to ask?

1 members found this post helpful.

Hi,

As other members have pointed out, the posting of errors will provide a means to map out your requests. No one can know what you have managed to mangle without knowing specifics. Yes, you are vague and expecting others to provide your requested specifics. We can not pull the requested queries from so as to produce results from thin air. One specific point is that you did state that your install is custom but that 'Slackware -current' is the install that Alien_Bob has used to produce a working package. How much of a variant have you made?

Post the results of your attempts or steps that did produce errors that may point to a solution(s). I am sure that Alien_Bob can produce a package but even he needs to decide what is necessary to do from produced errors.

Look at; Vague (pick a definition that I am sure will fit your request(s)). You are from from being a newbie but maybe you should consider reading; How to Ask Questions the Smart Way
Hope this helps.
Have fun & enjoy!

Better yet, nevermind. Forget I asked. All I asked was the specific order everything was built in. Yes it is a custom install but only in a few areas which of thing were mentioned. The rest is vanilla -Current.

I had to do a custom build of the deps using the step by step method because I had it compiling against mono which didn't behave with libappindicator, to which I had to continue the build, but using the script as a walkthrough to know what came next in the process after I removed mono and gtk-sharp and was able to continue.

So yeah just forget it. Sorry I asked such a simple question which somehow became an impossible monstrosity to answer.

1 members found this post helpful.

Eric's answer is quite clear in this regard, so the build order is determined by the SlackBuild. If you take a close look at the SlackBuild itself and the modules folder, especially the mention how to build inidividual modules or even only one application at the top of the SlackBuild you should get going I guess.

In that vague way, I would say yes. "Doctor, there is that error after having done several things. I won't tell you what exactly it felt and where it occured, but please help me. Is that too much to ask?" That is vague. The ouput of configure or make would surely help. I haven't tried to build KDE5, but I've seen some of Eric's SlackBuilds before and if anyone is keen on logging those then he is. There should be some log.

Hi,

If a newbie had made a request of the type you made then they would get similar response(S). You were wanting specifics! You provided nothing but a response with; Apparently not, since you are experiencing errors that you do not know how to fix thus a request for a solution(s) without us knowing the errors produced. You can use these errors to trail through to find the solution. Why can you not provide the lists of errors of the output as you attempt to create a working package? Instead of just flipping off the community by stating;Not a problem except from the member who posted the request without providing details to help that member come to a resolution. Maybe you could look at;KDE 5_15.06 with a few useful fixes to get some in-depth information and guiding by Alien_Bob's Blog.
Hope this helps.
Have fun & enjoy!

He can't provide error logs because the people will learn his Secret Plan to Conquer the World, most probably a combination with OpenPAM and a Secret Sauce based on Wayland...

The sad news (for him) is that KDE5 showed his fangs in this (strange?) build system.

The answer is: This is Slackware and everyone knows slackware doesn't even *have* any dependencies, and thus there is no Build Order. You simply keep going over and over the list of stuff, configuring, compiling and installing until it all works. Then only recompile individual stuff as needed (when it breaks because of upgrading other libs), since it really is a pain to do it without mentioning the 'D' word or having a Build Order from old notes. You do destroy any notes that you keep while doing such projects, right -we wouldn't wanna be caught with anything on our boxes which looks like dependency information, right?

Just a word of advice. If you re-read my original post all I specifically asked for was the order you can individually build every package in. I didn't care about the error, nor my system configuration. All I was asking for was the set of commands used in order if you were to use ./KDE.SlackBuild such as ./KDE.SlackBuild framework:kde-frameworks and so on.

If you want to act childish and poke fun at me go ahead. I'm unsubscribing from this thread, so I won't be reading it. I get the point of who is apparently worthy of help and who are thrown to the wolves.

1 members found this post helpful.

Wow. I'm sorry you feel that being asked to paste in the error message is "being thrown to the wolves".

Look, ReaperX. You should know better than this. Alien Bob (and others) asked you for the error message with the intention of helping you. They would have used the information in that error message to try to figure out where you your build order was wrong for you and what to build first.

The reason no-one posted the "correct" build order was because no-one knew it offhand. If you really want to figure it out, you can take obvious steps such as looking at the Gentoo ebuilds. Insisting that being given the build order was only kind of help you would accept was unproductive.

2 members found this post helpful.