Resolved.
I still don't know what caused the issue...
I closed down everything I had open, and took the opportunity to upgrade
OS X to 10.10.2...during the reboot I cleared PRAM x3.
This time I started the compile by just compiling kde4-runtime, and for
some reason it worked this time. Follo
On Tuesday January 27 2015 23:13:12 Marko Käning wrote:
> > How would I know what application is blocking?
> >
> > My terminal window just shows exactly what I pasted ending with:
> > >> [ 96%] Built target drkonqi
If `top -u` doesn't show an application taking up a lot of resources, there's
Hi Jeff,
On 27 Jan 2015, at 22:47 , Jeff Singleton wrote:
> Yes, I am building KDEnlive, kde4-runtime is a dependency.
yes.
> Command I used this time was: port -vd install kdenlive
Hmm, I wonder why you didn’t get the binaries from one of the MacPorts mirrors…
> How would I know what appl
Yes, I am building KDEnlive, kde4-runtime is a dependency.
Command I used this time was: port -vd install kdenlive
How would I know what application is blocking?
My terminal window just shows exactly what I pasted ending with:
>> [ 96%] Built target drkonqi
In fact, its still hung in t
Gideon Simpson writes:
> On one my machines I still have 10.9 installed and with the recent update to
> dolfin (which works fine on my 10.10 machine), I now get errors during the
> build:
>
> _opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/work/dolf
On one my machines I still have 10.9 installed and with the recent update to
dolfin (which works fine on my 10.10 machine), I now get errors during the
build:
_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/work/dolfin-1.5.0/build/dolfin/swig/modules
On Jan 23, 2015, at 10:32 PM, Joshua Root wrote:
> On 2015-1-24 14:40 , William H. Magill wrote:
>>
>>> On Jan 23, 2015, at 2:36 AM, Joshua Root wrote:
>>>
At 8:42 PM -0600 1/22/15, Ryan Schmidt wrote:
> So launchd is launching apache too early. I believe there are some
> keys o
