libvpx: virtual memory exhausted

[Scott Webster]

On Wed, Aug 4, 2010 at 10:57 AM,  <tome at qx.net> wrote:
> The below ticket was closed telling me to use macport gmake.  I just went
> through this gmake thing a week or so ago.  At the time I was told to
> reinstall Xcode 2.5 (  i.e. gmake 3.80 in /usr/bin ) and to sudo port -d
> selfupdate, which puts gmake 3,81 in /opt/local/bin, and that is the way
> things stand now.  If I did sudo port install libpvx, why would macport use
> the /usr/bin/gmake?
> Guidance please.  Thanks, Tom
>

I'm not sure if I'm really answering your question, but things were
updated 11 hours ago such that if you now:
sudo port selfupdate
sudo port clean libvpx
sudo port install libvpx

It should use the macports port gmake (which provides
/opt/local/bin/gmake) and not anything in /usr/bin

Scott