|
Something to be avoided.
It is a Linux OS build 'tool'. Buildroot was easy, obvious, it worked, used it a lot. I have touched on Yocto in the past, and now using it in anger, and believe me, it is making me really angry!
|
|
|
|
|
Anything Linux is supposed to make you angry, its designed that way to keep the riff-raff out. Windows 10 is better for those idiots sorry computer users.
|
|
|
|
|
It's for people who should be in the poky.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I did! Just to annoy you! 1-0!
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
As if he needs more things to be annoyed at.
|
|
|
|
|
If - and it is a big if - -9 is a kernel code, than it is a bad file error - probably meaning you have some access error during the build... Try and run it as super user...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
And here is an actual useful reply, who what have thought it, in the Lounge too.
|
|
|
|
|
Yeah, we dont want that here, all we want is splenetic venting!
|
|
|
|
|
|
Do not laugh at me! I have a bad day...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
It isn't that, it is the build trying to do too much at once, spawning processes everywhere. Apparently, and rather ridiculously, it seems to be incapable of adapting dynamically to the resource availability of the host machine!
|
|
|
|
|
Check the member's list - you may find Microsoft there...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
That's a great idea! If you are caught by an access violation, preventing you from destroying data that isn't yours, obtain the rights to do the write so that the other data IS overwritten. If you are lucky, that might bring down your entire system, not just the worker process!
|
|
|
|
|
I always loved negative numbers in error messages. Really adds to the impact that something went "catastrophically" wrong.
|
|
|
|
|
They are not really negative by declaration. It is probably Yocto that try to scare you more
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
especially 9, such an evil bastard 9 is.
|
|
|
|
|
7 is worse. 9 is the victim.
|
|
|
|
|
|
Yep, and those error messages arent covered.
|
|
|
|
|
Are you sure? Might it be that this is just another case that you disagree with what is written in the manual and so choose to visit Code Project to have a rant about it instead.
It could be that error messages are made up there are no error messages, all these people have been wrong about error messages for years, there is evidence to support that error messages are not real and if we all just ignore them everything will be fine in the end.
|
|
|
|
|
I googled the error messages, and the one place I wasnt taken to was the manual.
I did find a comment about checking system resources, so I grew the disk again, and limited the concurent tasks to 6, which has averted that error at least.
Of course now I have new ones....
|
|
|
|
|
My programs (/processes) always have an outermost exception handler catching all otherwise uncaught exceptions. My support library provides a ComeFrom function used by exception handlers to traverse the stack to pick up whatever information is available.
True enough: There is a standard "Print stacktrace" option. But first: Handling the exception programmatically is far easier when the information is provided as a data structure, rather than in console output format. Second, there is often more information available in the binary stack traversal than what is printed on the console.
If the code is not yours, so you cannot insert an exception handler, this option may be unavailable. But in those cases, you often cannot do anything about it anyway. (Our Bamboo build system generates at least a handful of stack traces every day, often 250-300 stack frames deep. We can read the function names, so what? We can do nothing but ignore it. Mailing the stack trace to Atlassian is futile.)
|
|
|
|
|
Without his king, the champion leads descent into darkness (9)
|
|
|
|
|
NIGHTFALL
Champion = Knight -> without king = NIGHT leading descent = FALL
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|