Now, I had this in the past, and I remember a discussion on the mailing list about it and the fact that it only seems to affect those running Zeta. I also know that there’s some solution or work around for this problem, but I don’t remember what it is. Can anyone let me know? Thanks!
Now, I had this in the past, and I remember a discussion on the mailing list about it and the fact that it only seems to affect those running Zeta. I also know that there’s some solution or work around for this problem, but I don’t remember what it is. Can anyone let me know? Thanks!
Adam
Did this cause a problem? - i seem to always get a “waif child found” message when the haiku image is created using “jam haiku.image” - but I believe that’s normal…
I remember someone complaining about the abouthaiku resource being problematic on Linux though - but I thought that had been fixed.
Now, I had this in the past, and I remember a discussion on the mailing list about it and the fact that it only seems to affect those running Zeta. I also know that there’s some solution or work around for this problem, but I don’t remember what it is. Can anyone let me know? Thanks!
Adam
Did this cause a problem? - i seem to always get a “waif child found” message when the haiku image is created using “jam haiku.image” - but I believe that’s normal…
I remember someone complaining about the abouthaiku resource being problematic on Linux though - but I thought that had been fixed.
It definitely causes a problem as the build stops dead in its tracks. I’m not doing a “jam haiku.image”, just a “jam haiku” and then a “jam install-haiku” to install the compiled distribution onto the appropriate mounted partition.
Now, I had this in the past, and I remember a discussion on the mailing list about it and the fact that it only seems to affect those running Zeta. I also know that there’s some solution or work around for this problem, but I don’t remember what it is. Can anyone let me know? Thanks!
Adam
Did this cause a problem? - i seem to always get a “waif child found” message when the haiku image is created using “jam haiku.image” - but I believe that’s normal…
I remember someone complaining about the abouthaiku resource being problematic on Linux though - but I thought that had been fixed.
It definitely causes a problem as the build stops dead in its tracks. I’m not doing a “jam haiku.image”, just a “jam haiku” and then a “jam install-haiku” to install the compiled distribution onto the appropriate mounted partition.
Adam
what does “jam haiku” do? I didn’t realize there was a “haiku” target.
you should only have to do a "jam install-haiku" (which I do often also)
It definitely causes a problem as the build stops dead in its tracks. I'm not doing a "jam haiku.image", just a "jam haiku" and then a "jam install-haiku" to install the compiled distribution onto the appropriate mounted partition.
Adam
what does “jam haiku” do? I didn’t realize there was a “haiku” target.
you should only have to do a "jam install-haiku" (which I do often also)
Sorry, instead of "jam haiku" I only do a "jam", wait for it to finish and then do a "jam install-haiku". As described at:
If I just do a "jam install-haiku" it fails with the same error at the same point.
Adam
Ah, ok - you don’t have to run jam by itself - in fact, you shouldn’t bother as there are many targets in the tree that won’t build.
jam install-haiku or jam haiku.image will only build the targets necessary for Haiku to be installed/run based on the currently defined "HaikuImage" jam rules.
my guess is that simply running:
jam abouthaiku
will throw the error you’re seeing - and you can probably debug it further that way… best bet is to pop into #haiku and ask some of the senior devs there if they know what causes it and how to fix it on your zeta system.
edit: I think the only reason to jam anything prior to “install-haiku” or “haiku.image” is to get rc built… if I recall, this isn’t automatically done and you have to “jam rc” first before building the image and what-not.
edit: I think the only reason to jam anything prior to "install-haiku" or "haiku.image" is to get rc built... if I recall, this isn't automatically done and you have to "jam rc" first before building the image and what-not.
IN FACT… maybe that’s the problem… - try a “jam rc” - or navigate to the tools/rc folder and run “jam” there - maybe you don’t have the right version of rc to process the rsrc file or something.
I’ve completey deleted my source tree, checked everything out, rebuilt jam from the tools directory, and built ‘rc’ from the tools directory first as well.
I then tried a "jam install-haiku" and it failed at the same point with "waif child found!".
I’ve completey deleted my source tree, checked everything out, rebuilt jam from the tools directory, and built ‘rc’ from the tools directory first as well.
I then tried a "jam install-haiku" and it failed at the same point with "waif child found!".
Any other ideas?
I’m not much help beyond there - I think you can remove the abouthaiku target from the HaikuImage and then build successfully until you figure out the problem… (in the build/jam folder I think)
As mentioned earlier, I suspect someone in #haiku would be more help.