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