Re: jupyter-2.7 vs. ipython

Marius, I just installed py27-jupyter today, checked the py27-future presence but it crashes in a similar way to what Bob reported below : py27-futures @3.2.0_0 (active) py27-tornado @5.0.1_1 (active) NICER>jupyter-2.7 notebook Traceback (most recent call last): File

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

On 2018-03-20, at 2:27 PM, Andreas Falkenhahn wrote: >> >> Personally, I do not understand why you are still running such an old >> machine with macOS. > > It's retro, there doesn't have to be a rational reason for it :-) > Besides, in the retro scene 10.4 is quite

Re: jupyter-2.7 vs. ipython

In my experience, “jupyter notebook” is the correct startup command. Here is what I do, using Python 2.7: Install pyenv (https://github.com/pyenv/pyenv) pyenv install 2.7.14 sudo port install py27-virtualenv mkdir jupyter cd jupyter pyenv virtualenv 2.7.14 jupyter echo "jupyter" >

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

On 21 Mar 2018, at 14:23, miniupnp wrote: On the other hand, it is also fun to read message about someone afraid of his hardware burned by a hours long macports build  :) This is a serious concern. I've had 3 Macs (Cube, G5 iMac, MacBook) that got worse at heat dissipation over time to the

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

On 20.03.2018 at 23:51 Ryan Schmidt wrote: > There is not a great deal of interest in Tiger anymore, but I > understand that the computers that are still running Tiger are slow > and are thus the ones that might most benefit from the existence of binaries. Definitely. Having binaries would be a

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

Le 21.03.2018 à 19:29, Daniel J. Luke a écrit : > On Mar 21, 2018, at 2:23 PM, miniupnp wrote: >> It's quite fun to read exhortations to use upgrade to a more recent >> system. I'm trying to imagine which hacker could spend time to exploit >> Mac PPC machines to include them in

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

On Mar 21, 2018, at 2:23 PM, miniupnp wrote: > It's quite fun to read exhortations to use upgrade to a more recent > system. I'm trying to imagine which hacker could spend time to exploit > Mac PPC machines to include them in a bitcoin mining botnet ;) or DDOS or SPAM or other

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

I'm one of the guys who run a 10.4 G4 "just because I can". Some call it retro computing :) I'm glad macports still supports it and try to help to fix things when a port is not building on it. but I'm not expecting the project to spend resources in building binaries for this kind of system. When

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

On 21.03.2018 at 00:34 David Strubbe wrote: > For the record, you can always stop a build by typing CTRL-C, and > it will not corrupt anything. Only at the install stage are any > files permanently changed. If you do "port clean" after stopping the > build, you will be right back where you were

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

On 20.03.2018 at 23:59 Chris Jones wrote: > You can call these OSes ‘retro’ if you want, to make it sound good, > but all they really are, are outdated and insecure. I've always preferred freedom over security. And by the way, I have a feeling that with each new Mac OS version the system becomes

Re: Trouble compiling with gcc 4.8 on 10.5 PowerPC

On 2018-03-18, at 8:44 AM, Kenneth F. Cunningham wrote: >> There's just one little problem remaining: I cannot use gcc-ar-mp-6 because >> it reports the following error: "Cannot find plugin liblto_plugin.so". > Looks like this is just broken on all MacPorts versions of gcc, for example on