Re: Ruby gaining weight?
Man try portupgrade -P as a cure. It's not 100% solution, but it's better that stabbing your machines to death. Else build the package on another host and update your machines with it. For piggy questions - cannot answer. Sorry Cheers, 2006/10/2, Pete Slagle [EMAIL PROTECTED]: Recent versions of ruby18 seem to take more than 145 MB of virtual memory to build with portupgrade or make install clean. I have several classic boxes running bind and a mail MTA on 4.11 that are memory-limited, but otherwise work well. The main boards are maxed out at 64 MB of RAM, and they have 128 MB of swap. The ruby build fails as swap space becomes exhausted. Sure, I could reorganize the hard drives on these boxes to add more swap, but nothing else needs more that a few KB. Moreover, rebuilding the hard drives is to be avoided since these machines are part of a basic infrastructure that has been stable for years. Is ruby really that piggy, or do I just have a configuration issue? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Димитър Василев Dimitar Vassilev GnuPG key ID: 0x4B8DB525 Keyserver: pgp.mit.edu Key fingerprint: D88A 3B92 DED5 917E 341E D62F 8C51 5FC4 4B8D B525 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ruby gaining weight? [RESOLVED]
Alex Zbyslaw wrote: Pete Slagle wrote: Recent versions of ruby18 seem to take more than 145 MB of virtual memory to build with portupgrade or make install clean. Karol Kwiatkowski wrote less than a week ago: # cd /usr/ports/lang/ruby18 # make -DNOPORTDOCS install That put me on the right track, thanks! Karol's example works well for the initial installation of ruby. When upgrading, this invocation: portupgrade -m '-DNOPORTDOCS' ruby does the equivalent thing. Both save a tremendous amount of time and disk activity. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ruby gaining weight? [RESOLVED]
On 03/10/2006 11:37, Pete Slagle wrote: Alex Zbyslaw wrote: Pete Slagle wrote: Recent versions of ruby18 seem to take more than 145 MB of virtual memory to build with portupgrade or make install clean. Karol Kwiatkowski wrote less than a week ago: # cd /usr/ports/lang/ruby18 # make -DNOPORTDOCS install That put me on the right track, thanks! Karol's example works well for the initial installation of ruby. When upgrading, this invocation: portupgrade -m '-DNOPORTDOCS' ruby does the equivalent thing. Both save a tremendous amount of time and disk activity. Just for the record, the last update[1] to ruby18 port brought us a brand new knob 'WITHOUT_RDOC' :) Cheers, Karol [1] http://www.freebsd.org/cgi/getmsg.cgi?fetch=129223+0+current/cvs-ports -- Karol Kwiatkowski freebsd at orchid dot homeunix dot org OpenPGP: http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc signature.asc Description: OpenPGP digital signature
Ruby gaining weight?
Recent versions of ruby18 seem to take more than 145 MB of virtual memory to build with portupgrade or make install clean. I have several classic boxes running bind and a mail MTA on 4.11 that are memory-limited, but otherwise work well. The main boards are maxed out at 64 MB of RAM, and they have 128 MB of swap. The ruby build fails as swap space becomes exhausted. Sure, I could reorganize the hard drives on these boxes to add more swap, but nothing else needs more that a few KB. Moreover, rebuilding the hard drives is to be avoided since these machines are part of a basic infrastructure that has been stable for years. Is ruby really that piggy, or do I just have a configuration issue? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ruby gaining weight?
Pete Slagle wrote: Recent versions of ruby18 seem to take more than 145 MB of virtual memory to build with portupgrade or make install clean. I have several classic boxes running bind and a mail MTA on 4.11 that are memory-limited, but otherwise work well. The main boards are maxed out at 64 MB of RAM, and they have 128 MB of swap. The ruby build fails as swap space becomes exhausted. Sure, I could reorganize the hard drives on these boxes to add more swap, but nothing else needs more that a few KB. Moreover, rebuilding the hard drives is to be avoided since these machines are part of a basic infrastructure that has been stable for years. Is ruby really that piggy, or do I just have a configuration issue? Karol Kwiatkowski wrote less than a week ago: Just some thoughts as others already identified the problem: here's similar thread with some workarounds: http://lists.freebsd.org/pipermail/freebsd-questions/2006-September/131328.html In the meantime I've found NOPORTDOCS variable - if you don't need ruby docs just disable them (docs are generated during install part) # cd /usr/ports/lang/ruby18 # make -DNOPORTDOCS install The install part without docs takes about 30 seconds on 400Mhz/96MB machine (it would take hours otherwise). HTH, Karol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
