On 20 Mar 2018, at 00:34, Ryan Schmidt wrote:
> Error: Unable to determine location of a macOS SDK.
Could it instead be a warning?
I can't tell if this is a bug in MacPorts, or if I have simply
misconfigured something.
When I start up `ipython notebook`, with python-2.7 as my selected
python, everything works fine, but I get a complaint echoed to the
shell:
```
[TerminalIPythonApp] WARNING | Subcommand `ipython notebook
I just posted a ticket for this very issue:
https://trac.macports.org/ticket/56111
> On Mar 20, 2018, at 1:19 PM, Robert Goldman wrote:
>
> I can't tell if this is a bug in MacPorts, or if I have simply misconfigured
> something.
>
> When I start up ipython notebook, with python-2.7 as my sel
So I installed gcc6 on my 10.5 G5 PowerMac a few days ago and it was a breeze.
It took just a few minutes. It looked like the installer just grabbed the
binaries
and installed them. No big deal at all.
Now I am trying to install gcc6 on my 10.4 G4 Mac Mini and it seems to build
everything from
On 10.5 you installed a prebuilt binary.
gcc6 takes 12 to 24 hrs to build on a PPC machine.
I should make my premade binaries available.
K
> On Mar 20, 2018, at 14:32, Andreas Falkenhahn wrote:
>
>
>
> So I installed gcc6 on my 10.5 G5 PowerMac a few days ago and it was a breeze.
> It took
On 20.03.2018 at 21:35 Ken Cunningham wrote:
> On 10.5 you installed a prebuilt binary.
> gcc6 takes 12 to 24 hrs to build on a PPC machine.
Oh my, that's too much for me, I've just hit CTRL-C. Of course this might leave
me with a corrupt installation but I'm just too paranoid about Mac Ports
k
On Mar 20, 2018, at 4:43 PM, Andreas Falkenhahn wrote:
> IMHO there really should be prebuilt binaries for 10.4. It's a waste of
> energy and resources to have everybody build this on his own...
IMHO we shouldn't do anything to support Mac OS versions that aren't getting
security patches from A
On 2018-03-20 21:43, Andreas Falkenhahn wrote:
> On 20.03.2018 at 21:35 Ken Cunningham wrote:
>
>> On 10.5 you installed a prebuilt binary.
>> gcc6 takes 12 to 24 hrs to build on a PPC machine.
>
> Oh my, that's too much for me, I've just hit CTRL-C. Of course this might
> leave me with a corrup
On 20.03.2018 at 21:58 Rainer Müller 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 popular because it's the
last Mac OS capable of ru
+1.
Uli
> On Mar 20, 2018, at 4:27 PM, Andreas Falkenhahn
> wrote:
>
> On 20.03.2018 at 21:58 Rainer Müller 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
> On Mar 19, 2018, at 4:34 PM, Ryan Schmidt wrote:
>
> Ok, I've figured out that the reason why I'm not seeing the "Unable to
> determine location of a macOS SDK" message is that I was running MacPorts
> 2.4.2 and the message is new for MacPorts 2.5. MacPorts 2.5 considers it an
> error when
On Mar 20, 2018, at 17:22, Jeremy Huddleston Sequoia wrote:
> On Mar 19, 2018, at 4:34 PM, Ryan Schmidt wrote:
>
>> Ok, I've figured out that the reason why I'm not seeing the "Unable to
>> determine location of a macOS SDK" message is that I was running MacPorts
>> 2.4.2 and the message is ne
On Mar 20, 2018, at 08:29, db wrote:
> On 20 Mar 2018, at 00:34, Ryan Schmidt wrote:
>> Error: Unable to determine location of a macOS SDK.
>
> Could it instead be a warning?
If a port specifies that it requires an SDK, and the SDK does not exist, it is
proper for MacPorts to exit with an erro
On Mar 20, 2018, at 15:32, Andreas Falkenhahn wrote:
> Where does this difference come from? On my 10.5 G5 PowerMac it really was
> just a few minutes and now it's taking hours. Yes, the G5 is faster but
> certainly not that much. To me it looked as if on 10.5 binaries were
> downloaded and insta
> On 20 Mar 2018, at 8:43 pm, Andreas Falkenhahn wrote:
>
>> On 20.03.2018 at 21:35 Ken Cunningham wrote:
>>
>> On 10.5 you installed a prebuilt binary.
>> gcc6 takes 12 to 24 hrs to build on a PPC machine.
>
> Oh my, that's too much for me, I've just hit CTRL-C. Of course this might
> leave
> On 20 Mar 2018, at 8:48 pm, Daniel J. Luke wrote:
>
>> On Mar 20, 2018, at 4:43 PM, Andreas Falkenhahn
>> wrote:
>> IMHO there really should be prebuilt binaries for 10.4. It's a waste of
>> energy and resources to have everybody build this on his own...
>
> IMHO we shouldn't do anything
> On 20 Mar 2018, at 9:27 pm, Andreas Falkenhahn wrote:
>
>> On 20.03.2018 at 21:58 Rainer Müller 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
Hi,
Chris Jones wrote:
IMHO we shouldn't do anything to support Mac OS versions that aren't getting
security patches from Apple anymore (since it's a dis-service to the rest of
the people who use the internet when we make it easier for people to keep
unpatched machines connected to that share
On 2018-03-20, at 4:22 PM, Jeremy Huddleston Sequoia wrote:
>
> I cringe at trying to get an older Xcode's toolchain to work with a newer
> SDK.
>
>
Perhaps I shouldn't even say it, but here's what I do:
symlink into the Xcode SDK the following toolchain bits from current MacPorts
installs
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 before the build.
David
On Tue, Mar 20, 2018 at 4:13
20 matches
Mail list logo
