Help with a failed build

Forum thread started by gps on Tue, 2006-12-05 16:51

Four hours of building and then this:

...skipped haiku.image for lack of <HaikuImage>haiku.image-copy-files...
...skipped 4 target(s)...
...updated 7184 target(s)...

I don't know what's lacking. haiku.image-copy-files is there, 87506 bytes.

I did a new checkout of the code today. The previous version built fine and boots.
Where do I start with something like this?

Comments

Help with a failed build

by ekdahl - 2006-12-05 17:49

Add "-q" to your jam command, then the build will stop at the first error so it is easier to find what the problem is. Like this:

jam -q haiku-image

Help with a failed build

by gps - 2006-12-05 17:59

I did. I just copied the command from .bash_history to make sure:

jam -q haiku-image

That's one reason I'm so puzzled.

Help with a failed build

by umccullough - 2006-12-05 22:19

gps wrote:

I did. I just copied the command from .bash_history to make sure:

jam -q haiku-image

That's one reason I'm so puzzled.

Strange - I haven't seen that one yet.

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 :P

Help with a failed build

by gps - 2006-12-06 10:54

umccullough wrote:

Strange - I haven't seen that one yet.

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 :P

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.

Now I'm off to do my dd trick.

Thanks for your help.

Help with a failed build

by El-Al - 2006-12-21 20:49

'...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 :cry:

Help with a failed build

by j_freeman - 2006-12-22 15:56

El-Al wrote:

'...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 :cry:

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.

Help with a failed build

by El-Al - 2006-12-23 20:16

Did a clean svn checkout. Sorted! :D

Help with a failed build

by umccullough - 2006-12-27 18:39

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.