On May 12, 2010, at 19:42, Liam Groener wrote:
> On May 12, 2010, at 5:00 PM, Ryan Schmidt wrote:
>
>> Did you not update your ports in awhile, or backdate your ports? If so,
>> "sudo port selfupdate" to update them again, then try again.
>
> port -v
> MacPorts 1.8.2
>
> which I believe is th
On May 12, 2010, at 5:00 PM, Ryan Schmidt wrote:
> Did you not update your ports in awhile, or backdate your ports? If so, "sudo
> port selfupdate" to update them again, then try again.
port -v
MacPorts 1.8.2
which I believe is the current version.
> Or, did you create a local port repository
On May 12, 2010, at 17:57, Liam Groener wrote:
> On May 11, 2010, at 11:38 PM, Ryan Schmidt wrote:
>
>> To work around this for now, build with fewer build make jobs, i.e.
>>
>> sudo port clean octave
>> sudo port install octave build.jobs=1
>
> That got me a working copy of octave; thanks. How
On May 11, 2010, at 11:38 PM, Ryan Schmidt wrote:
> To work around this for now, build with fewer build make jobs, i.e.
>
> sudo port clean octave
> sudo port install octave build.jobs=1
That got me a working copy of octave; thanks. However, it just reinstalled
3.2.3, not 3.2.4. I tried follo
On May 11, 2010, at 4:46 PM, Victor Eijkhout wrote:
> Ok, maybe it's not there. Second question: I have a bunch of python packages
> installed. And I have probably 3 different pythons on my system. How do I
> tell the other two where the macports packages are so that they can import
> them?
Y
