Haiku won't build!

1

A few days ago, I was happily downloading the latest Haiku Revisions from SVN and building them on my Athlon XP 2000+ BeOS box with abandon. And I was a happy camper.

But that has ceased. Now, when I attempt to build, I get a spew of “Failed…” and “Skipped…” error mesages. This can’t be found and that can’t be compiled… etc. On and on and on it goes, right to the end.

It ends, telling me that it either couldn’t create the “haiku.image” file (if I use “jam haiku-image”) or install to my Haiku partition (if I use “jam install-haiku”).

I have tried deleting the entire trunk directory (gah, that takes forever in BeOS!) and downloaded the entire tree afresh. I have started with a known working revision of Haiku that I built on and it still built fine and downloaded the latest files on top of it. Neither work.

"Failed…" this or "Skipped…" that. Scattered throughout the "Jam session" (as I call it)

The “Jam” that Haiku, Inc. has (or links to) on their site doesn’t work anymore (at least for me), as it quits with some weird error message before it finishes the build. I downloaded the only other “newer” Jam I coulds find (has “2005” in the filename) and that has worked find til the last few days.

It appears that they (Haiku, Inc.), themselves, are having build problems, as shown in their Build Factory "Jam log". So this appears to not be an isolated incident.

Yet, people like Sikosis and Jon have the near-to-latest revisions of Haiku available for download. What is up with that? They can build, but I can’t?

No fair! :smiley:

If anyone can offer any insight to this situation, I’d be greatly appreciative.

I am running BeOS R5 PE (WIND distro) on an Athlon XP 2000+ with 512Mb of DDR SDRAM, a GeForce3 Ti500 video card (Asus V8200/T5), built-in audio, 30Gb Maxtor HD, 3Com Ethernet card, etc.

If that helps.

Does anyone have the very, VERY, V E R Y most recent build of JAM? What is the version GCC I’m supposed to be using (assuming anything has changed in that last couple weeks that could cause this problem)?

Could something be corrupted in BeOS? Should I reinstall BeOS R5 PE and start over fresh?

Is my Jam too old (ewww, mold! (grin))?

Is my GCC (that whole "routine" I have to go through, to set up everything correctly in BeOS (change c++ to c++.old and this file to that name and create a link to that folder, etc.) munged up?

There simply MUST be a logical explanation! And I wanna know what it is! :slight_smile:

Latre!

Luposian

2

Lupo, I started to have problems building lately as well. I still haven’t found a reason why, though.

Sikosis manages the Build Factory’s build machine, and I (err, Jon, lol) simply mirror his image. (Don’t ask me how he keeps on cranking images out–I’d like to know myself.) I’ve yet to successfully build Haiku on BeOS, but I have been able to on Linux lately.

3
Luposian wrote:
A few days ago, I was happily downloading the latest Haiku Revisions from SVN and building them on my Athlon XP 2000+ BeOS box with abandon. And I was a happy camper.

But that has ceased. Now, when I attempt to build, I get a spew of "Failed…" and "Skipped…" error mesages. This can’t be found and that can’t be compiled… etc. On and on and on it goes, right to the end.

It ends, telling me that it either couldn’t create the "haiku.image" file (if I use "jam haiku-image") or install to my Haiku partition (if I use "jam install-haiku").

I have tried deleting the entire trunk directory (gah, that takes forever in BeOS!) and downloaded the entire tree afresh. I have started with a known working revision of Haiku that I built on and it still built fine and downloaded the latest files on top of it. Neither work.

"Failed…" this or "Skipped…" that. Scattered throughout the "Jam session" (as I call it)

The "Jam" that Haiku, Inc. has (or links to) on their site doesn’t work anymore (at least for me), as it quits with some weird error message before it finishes the build. I downloaded the only other "newer" Jam I coulds find (has "2005" in the filename) and that has worked find til the last few days.

It appears that they (Haiku, Inc.), themselves, are having build problems, as shown in their Build Factory "Jam log". So this appears to not be an isolated incident.

Yet, people like Sikosis and Jon have the near-to-latest revisions of Haiku available for download. What is up with that? They can build, but I can’t?

No fair! :smiley:

If anyone can offer any insight to this situation, I’d be greatly appreciative.

I am running BeOS R5 PE (WIND distro) on an Athlon XP 2000+ with 512Mb of DDR SDRAM, a GeForce3 Ti500 video card (Asus V8200/T5), built-in audio, 30Gb Maxtor HD, 3Com Ethernet card, etc.

If that helps.

Does anyone have the very, VERY, V E R Y most recent build of JAM? What is the version GCC I’m supposed to be using (assuming anything has changed in that last couple weeks that could cause this problem)?

Could something be corrupted in BeOS? Should I reinstall BeOS R5 PE and start over fresh?

Is my Jam too old (ewww, mold! (grin))?

Is my GCC (that whole "routine" I have to go through, to set up everything correctly in BeOS (change c++ to c++.old and this file to that name and create a link to that folder, etc.) munged up?

There simply MUST be a logical explanation! And I wanna know what it is! :slight_smile:

Latre!

Luposian

Many of the failed/skipped targets you see in the jam log on the factory are not included in the image anyway, so that should not be a problem.

Check and make sure you’re using the same gcc and jam version posted on the wiki (I helped someone last night with build problems, and these versions worked for him):

http://www.haiku-os.org/wiki/index.php?title=GetHaikuSVN

Follow the installation instructions for GCC that are included in the zip - there are only a few steps to work with.

You might also want to re-install the BeOS R5 Dev tools before re-installing the newer GCC - i don’t know how much that matters much.

Once everything is installed, go to the Haiku trunk and run:

./configure --target=haiku

then run (for the heck of it)

jam clean

then maybe also delete the entire "generated" directory just to be sure

finally, just do:

jam -q haiku-image

and whatever it dies on, post the error here for us to look at.

4
j_freeman wrote:
Lupo, I started to have problems building lately as well. I still haven't found a reason why, though.

Sikosis manages the Build Factory’s build machine, and I (err, Jon, lol) simply mirror his image. (Don’t ask me how he keeps on cranking images out–I’d like to know myself.) I’ve yet to successfully build Haiku on BeOS, but I have been able to on Linux lately.

I just realized - maybe you’re not totally sync’d with svn or something…

try running:

svn stat

it should tell you anything that doesn’t match the SVN server - if you have modified any files, they should display here… you can then revert them with svn revert I believe.

5

I decided to just do a "fix-all" format (init) and reinstall of BeOS R5 PE (WIND distro). And then go through the usual headache of setting up the BeOS Dev. Tools and GCC and Subversion, etc.

And then download the latest Haiku revision (about 1 to 1.5 hours) and then finally jam the whole deal together (1 hour)…

And… IT WORKED! I have an 80Mb haiku.image ("waif child found!"; whatever that means) now!

So, if nothing else works, just start over from scratch (reformat (init)/reinstall everything) and that should fix it!

It may not be the most desirable way to get back up and running, but ya do what’cha gotta do… :smiley: So back up your importants (.zip. .pkg, etc. files) to another partition, scrub the BeOS partition, and…

"START OVER! START OVER, MAN!" (a rephrase of a line from Aliens)

Latre!

Luposian

6

This is what I had to do, Lupo. But my problem was that I had the newer version of GCC installed, instead of 2.9x. :oops: Glad you got yours working, too!

And I also got the “waif child found” message. Never got that on Linux before. Also, I couldn’t mount the image; the program said it was an invalid image file. Haven’t tried mounting from the command line, so I might do that tonight. Have you had trouble using your “waif child” image?

@Urias, I’ll try the stat subversion command tonight, and see what it tells me, though I’m fairly certain I’m completely up-to-date.

7

I use "Mount Image" (the program by the "Supreme Haiku Warrior" programmer, Axel Dorfler) to mount my BeOS-generated haiku.image files. Right-click on the file and select "mount image" from the add-on menu.

If you create your haiku.image in Linux, it seems as though Mount Image doesn’t like that and requires that you not only rename haiku.image to haiku.img, but often spend several minutes trying to mount it over and over, as it continues to insist that something is wrong, before FINALLY letting you mount the image.

So, generate your haiku.image files in BeOS and all will be well and happy.

Haven’t tried the haiku.image made last night, but I know it will work. It always has before. My system was just munged up, that’s all… I think it might be that UDMA133 driver from BeBits, I use. Makes the disk transfers lightning quick, but… I think it messes up the system eventually. I hate to run this slow (disk transfers-wise), but having to reinstall BeOS and everything else every couple weeks is getting a bit annoying. :slight_smile:

Luposian

8
Luposian wrote:
If you create your haiku.image in Linux, it seems as though Mount Image doesn't like that and requires that you not only rename haiku.image to haiku.img, but often spend several minutes trying to mount it over and over, as it continues to insist that something is wrong, before FINALLY letting you mount the image.

So, generate your haiku.image files in BeOS and all will be well and happy.

Actually, my Linux-built images seem to mount just fine. The problem I encountered while mounting was a BeOS-built image, built just minutes before on the same system.

I dunno, I’ve just been having all kinds of weird stuff going on. Maybe I have a BeOS virus? :lol: The program I was using wasn’t Axel’s; it was another bloke’s, but it worked marvelously with the Linux images. Tonight I’ll try Axel’s, and then command line if that doesn’t work.