Ok, I went to /buildtools/jam and typed “make” and then “sudo ./jam0 install” and it still is telling me that I need to use Haiku’s Jam, when I go to the generated.x86_64 directory and try to run Jam. Do I need to reboot? If not, what am I missing? I’m reading that page and I see NOTHING I haven’t already done! Except some “setfattr” thing that the ./configure command is telling me isn’t found. Is THAT what is missing?
Not sure how to do that, but even if I do, I’m still stuck with:
Command ‘jam’ not found, but can be installed with:
sudo apt install ftjam
sudo apt install jam
So, HOW do I build the Haiku version of Jam, if the way I’ve tried is not working? Or are the two versions (one that I sudo’d and the other one which I "make"d) now conflicting with each other? And removing the one will release the other, to function correctly?
No need for a new computer. My AMD FX (Vishera) system, with Ubuntu “Bionic Beaver” (what a crazy name!) is PERFECTLY fine!
I downloaded both /buildtools and /haiku within MINUTES, at 5-7Mbytes/sec, not the glacial 350Kbytes/sec in Haiku x86_64. How on EARTH is Haiku’s networking that slow? Is Ubuntu using some proprietary code that unleashes extra bandwidth or something? If Haiku is using BSD implementation of networking, is BSD that slow also?
Of course, with Haiku’s inability to handle more than two cores on my AMD FX (Vishera), it’s kind of a pointless venture to use Haiku to build Haiku on this system, so it’s nice to find out that Ubuntu unleashes all the potential I can’t get otherwise.
And Jam completed a fresh (1st time) build of Haiku x86_64 in a shocking 8 minutes!!!
It’s a beta version of Haiku, the kernel is built in debug mode, we have not even started to optimize anything. We’ll do that someday. It’s not BSD fault, Netflix servers run BSD and I’m fairly sure they do need the network to perform… reasonably well?