Make sure you have all the source (do another svn co into the same directory just to be sure - i’ve seen it fail for no reason).
What OS/machine? - I’ve not seen 4 hours of building the Haiku image - even on my PIII 600
Success. I svn’d again and got:
U haiku/src/servers/app/Jamfile
U haiku/src/kits/interface/MenuBar.cpp
U haiku/data/system/boot/Netscript
Checked out revision 19434.
This built successfully. I 'time’d it this time:
real 179m24.523s
user 0m23.580s
sys 32m25.390s
So, three hours. I guess I exaggerated a bit.
My system is an AMD Thunderbird 900, 256 Meg ram, 300 meg swap running R5 Pro.
‘…skipped haiku.image for lack of <HaikuImage>haiku.image-copy-files…’
Hmm… for some reason I’ve started to get this error every time I build!!
For the life of me, I can’t understand what has gone awry with my setup. For weeks I have been building Haiku images without problem and now I have this one.
Am trying to build the latest revision, as I tried to do last night also to no avail.
'...skipped haiku.image for lack of <HaikuImage>haiku.image-copy-files...'
Hmm… for some reason I’ve started to get this error every time I build!!
For the life of me, I can’t understand what has gone awry with my setup. For weeks I have been building Haiku images without problem and now I have this one.
Am trying to build the latest revision, as I tried to do last night also to no avail.
Any pointers please
Maybe some of you noticed, but HaikuHost wasn’t building for about a week… I was getting the same error. I did my usual clean wipe and starting over trick, but even that didn’t work. After days of doing whatever I could think of, it finally worked.
It seemed to stop building around December 13th all of a sudden. This is a automated build, mind you, so there’s no reason on my end why it should’ve started failing. I don’t think anything was changed in the build system to cause it to fail, either.
Definitely a mystery. My advice is to post to the mailing list, or start from scratch. With some luck, you can get it building again.
This happened to me last night also (it had been a couple weeks since I last built)…
First build went awry, but when i did a second build using jam -q haiku-image it worked.
I noticed that the second time i built it, some extra targets got built that were missed during the first build - so I’m guessing there had been a missing dependency the first time.