> On Oct 2, 2017, at 01:50, Jeremy Huddleston Sequoia
> wrote:
>
>
>
>> On Oct 1, 2017, at 22:55, Ryan Schmidt wrote:
>>
>>
>> On Oct 2, 2017, at 00:39, Leonardo Brondani Schenkel wrote:
>>
>>> On 2017-09-29 13:30, Ryan Schmidt wrote:
I don't know if I'm the author of the mail you're
On 2017-10-2 18:19 , Leonardo Brondani Schenkel wrote:
On 2017-10-02 08:50, Jeremy Huddleston Sequoia wrote:
If you have mismatched SDK/host versions *AND* you do not have the
DevSDK installed, we err out.
You mean that's the intent moving forward? Because I fit into this
description and MacP
On 2017-10-02 08:50, Jeremy Huddleston Sequoia wrote:
If you have mismatched SDK/host versions *AND* you do not have the DevSDK
installed, we err out.
You mean that's the intent moving forward? Because I fit into this
description and MacPorts *does not* error out today.
I know I'm entering
> On Oct 1, 2017, at 22:55, Ryan Schmidt wrote:
>
>
> On Oct 2, 2017, at 00:39, Leonardo Brondani Schenkel wrote:
>
>> On 2017-09-29 13:30, Ryan Schmidt wrote:
>>> I don't know if I'm the author of the mail you're thinking of, but I've
>>> surely commented on this matter before. It's Jeremy
On Oct 2, 2017, at 00:39, Leonardo Brondani Schenkel wrote:
> On 2017-09-29 13:30, Ryan Schmidt wrote:
>> I don't know if I'm the author of the mail you're thinking of, but I've
>> surely commented on this matter before. It's Jeremy Huddleston Sequoia's
>> work on master I was referring to.
>>
On 2017-09-29 13:30, Ryan Schmidt wrote:
I don't know if I'm the author of the mail you're thinking of, but I've surely
commented on this matter before. It's Jeremy Huddleston Sequoia's work on
master I was referring to.
I haven't tested that work. But at least with MacPorts 2.4.1 I perceived
On Sep 29, 2017, at 05:08, Leonardo Brondani Schenkel wrote:
> On 2017-09-29 12:02, Joshua Root wrote:
>> Well, our installation instructions say to install the Command Line Tools,
>> which avoids this problem. I guess we could try setting
>> MAC_OS_X_VERSION_MAX_ALLOWED explicitly, but unlike
On 2017-09-29 12:02, Joshua Root wrote:
Well, our installation instructions say to install the Command Line
Tools, which avoids this problem. I guess we could try setting
MAC_OS_X_VERSION_MAX_ALLOWED explicitly, but unlike
MACOSX_DEPLOYMENT_TARGET, it isn't picked up from the environment by the
On 2017-9-29 18:48 , Leonardo Brondani Schenkel wrote:
On 2017-09-29 10:23, Joshua Root wrote:
On 2017-9-29 18:14 , Leonardo Brondani Schenkel wrote:
This seems to be an issue in XCode 9 to me, since I believe that when
setting the deployment target to 10.12 or earlier it should not be
exposin
On 2017-09-29 10:23, Joshua Root wrote:
On 2017-9-29 18:14 , Leonardo Brondani Schenkel wrote:
This seems to be an issue in XCode 9 to me, since I believe that when
setting the deployment target to 10.12 or earlier it should not be
exposing symbols that are not available at runtime.
It is wor
On 2017-9-29 18:14 , Leonardo Brondani Schenkel wrote:
This seems to be an issue in XCode 9 to me, since I believe that when
setting the deployment target to 10.12 or earlier it should not be
exposing symbols that are not available at runtime.
It is working correctly as far as it goes; autocon
Hi all,
I have been bitten by this when building Python [1] but I noticed that
many other ports [2][3][4][5] have been affected by the following:
- You have macOS 10.12 or earlier
- You don't have the command line tools installed
- You update all apps from App Store and end up upgrading Xcode
12 matches
Mail list logo
