On 2017-12-8 16:54 , Marcus Calhoun-Lopez wrote:
> On Thu, Dec 7, 2017 at 9:37 PM, Joshua Root wrote:
>> On 2017-12-8 10:01 , Marcus Calhoun-Lopez wrote:
>>> On Mon, Dec 4, 2017 at 10:23 PM, Ryan Schmidt
>>> wrote:
Also, why `global os.major`? It's not used...
>>> os.major is used in l
On Thu, Dec 7, 2017 at 9:37 PM, Joshua Root wrote:
> On 2017-12-8 10:01 , Marcus Calhoun-Lopez wrote:
>> On Mon, Dec 4, 2017 at 10:23 PM, Ryan Schmidt
>> wrote:
>>>
>>> Also, why `global os.major`? It's not used...
>> os.major is used in line 52 [1].
>
> But not inside the register_gcc_dependent
On 2017-12-8 10:01 , Marcus Calhoun-Lopez wrote:
> On Mon, Dec 4, 2017 at 10:23 PM, Ryan Schmidt wrote:
>>
>> Also, why `global os.major`? It's not used...
> os.major is used in line 52 [1].
But not inside the register_gcc_dependents (now cxx11.add_dependencies)
proc.
- Josh
On Mon, Dec 4, 2017 at 10:23 PM, Ryan Schmidt wrote:
>
> On Oct 21, 2017, at 23:10, Marcus Calhoun-Lopez wrote:
>
>> Marcus Calhoun-Lopez (MarcusCalhoun-Lopez) pushed a commit to branch master
>> in repository macports-ports.
>>
>>
>> https://github.com/macports/macports-ports/commit/9ae6b8e85dc53
Ryan,
I’ve addressed all (I hope) your remarks in the new revision, which hopefully
made it through the buildbot :)
Cheers!
Vincent
On 7 Dec 2017, at 14:51, Joshua Root wrote:
> Looks correct to me; the system clang will be used for C++11 on 10.8 with
> libc++ (assuming most recent possible Xcode).
Ok. Out of curiosity, I tried on a 10.8-VM that's not set to build from source,
with CLT, no Xcode — to install highlight and i
On 2017-12-8 00:02 , db wrote:
> On 7 Dec 2017, at 07:29, Ryan Schmidt wrote:
>> They are, if you're running on an OS version where those dependencies are
>> added.
>
> Here's what I see:
>
> $ sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.8.5
> BuildVersion: 12F2560
> $ port rdep
The cmake 1.1 PG is now used by qtkeychain [1].
The cmake 1.1 PG is also now consistent with the cmake 1.0 PG [2].
[1]
https://github.com/macports/macports-ports/commit/56742c7ae2b4e773efe507da209d63aeebc4a84c
[2]
https://github.com/macports/macports-ports/commit/a11893408d88aed1752dfb7566493d8
On 7 Dec 2017, at 07:29, Ryan Schmidt wrote:
> They are, if you're running on an OS version where those dependencies are
> added.
Here's what I see:
$ sw_vers
ProductName:Mac OS X
ProductVersion: 10.8.5
BuildVersion: 12F2560
$ port rdeps highlight
The following ports are dependencies of h
On 7 Dec 2017, at 12:59, Mojca Miklavec wrote:
> Nowadays many ports claim
>Warning: All compilers are either blacklisted or unavailable; defaulting
> to first fallback option
> but do install nevertheless at the end. I would say that this is a bug in
> either the portfiles or portgroups tha
On Dec 7, 2017, at 01:38, Vincent wrote:
> Vincent (Veence) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/b35a0526cd7fb7e0c897d1c92d08ddea6e3232af
>
> The following commit(s) were added to refs/heads/master by this push
On 7 December 2017 at 10:28, Joshua Root wrote:
> On 2017-12-7 17:39 , Ryan Schmidt wrote:
>>
>> On Dec 7, 2017, at 00:37, Joshua Root wrote:
>>
>>> On 2017-12-7 17:29 , Ryan Schmidt wrote:
(I don't know why MacPorts base considers this a warning, rather than an
immediate-exit error.)
>>>
On 2017-12-7 17:39 , Ryan Schmidt wrote:
>
> On Dec 7, 2017, at 00:37, Joshua Root wrote:
>
>> On 2017-12-7 17:29 , Ryan Schmidt wrote:
>>> (I don't know why MacPorts base considers this a warning, rather than an
>>> immediate-exit error.)
>> Because you wouldn't want things like portindex or 'po
13 matches
Mail list logo
