[openbeos] Re: Developer Edition Vmware Image
- From: DarkWyrm <darkwyrm@xxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 07 Apr 2008 20:16:19 -0400
Ryan Leavengood wrote:
On Mon, Apr 7, 2008 at 5:50 PM, scott mc <scottmc2@xxxxxxxxx> wrote:
One more tip, the vmware player defaulted to 256M RAM for me and I
kept getting an error after about 25 lines of "patience", sometime it
would say segment fault. I changed the memory given to VMWARE player
to give it 1GB of RAM and it seems to be happier now. It's still
compiling at least. Not sure what the magic number is but it seems to
need more than 256M?
Jam alone can consume 200MB or more recursively processing all the
Jamfiles in our tree (look at top or similar on Linux when building
with the cross compilers.) People building on BeOS machines with 256MB
of RAM (like Stephan at one point) also had this problem. I would
expect 512MB would be enough as long as you aren't doing much else on
the machine.
It's been quite a while since I did any building under R5, but the last
time I did it, 384 did the job with some room to spare.
--DarkWyrm
- References:
- [openbeos] Re: Developer Edition Vmware Image
- From: Axel Dörfler
- [openbeos] Re: Developer Edition Vmware Image
- From: François Revol
- [openbeos] Re: Developer Edition Vmware Image
- From: scott mc
- [openbeos] Re: Developer Edition Vmware Image
- From: Ryan Leavengood
Other related posts:
- » [openbeos] Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
- » [openbeos] Re: Developer Edition Vmware Image
On Mon, Apr 7, 2008 at 5:50 PM, scott mc <scottmc2@xxxxxxxxx> wrote:
One more tip, the vmware player defaulted to 256M RAM for me and I kept getting an error after about 25 lines of "patience", sometime it would say segment fault. I changed the memory given to VMWARE player to give it 1GB of RAM and it seems to be happier now. It's still compiling at least. Not sure what the magic number is but it seems to need more than 256M?
Jam alone can consume 200MB or more recursively processing all the Jamfiles in our tree (look at top or similar on Linux when building with the cross compilers.) People building on BeOS machines with 256MB of RAM (like Stephan at one point) also had this problem. I would expect 512MB would be enough as long as you aren't doing much else on the machine.
- [openbeos] Re: Developer Edition Vmware Image
- From: Axel Dörfler
- [openbeos] Re: Developer Edition Vmware Image
- From: François Revol
- [openbeos] Re: Developer Edition Vmware Image
- From: scott mc
- [openbeos] Re: Developer Edition Vmware Image
- From: Ryan Leavengood