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
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 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 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 20 Mar 2018, at 00:34, Ryan Schmidt wrote:
> Error: Unable to determine location of a macOS SDK.
Could it instead be a warning?
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 it can't find an SDK. MacPorts 2.4.x and earlier just returned t
On 19 Mar 2018, at 17:39, Ryan Schmidt wrote:
> xcode-select -p
$ xcode-select --print-path
/Applications/Xcode.app/Contents/Developer
On Mar 19, 2018, at 11:21, db wrote:
> On 19 Mar 2018, at 16:56, Ryan Schmidt wrote:
>> Probably an unintended consequence of one of my changes last month.
>> What version of macOS and what version of Xcode are you using?
>
> OS X 10.8.5, Xcode 5.1.1.
Hmm. I can't reproduce the problem on OS X
On 19 Mar 2018, at 16:56, Ryan Schmidt wrote:
> Probably an unintended consequence of one of my changes last month.
> What version of macOS and what version of Xcode are you using?
OS X 10.8.5, Xcode 5.1.1.
On Mar 19, 2018, at 10:00, db wrote:
> Today I tried syncing and it failed, see log below. It succeeded when I moved
> the portfile away. Base is from source.
>
>
> $ sudo port -v sync
> ---> Updating the ports tree
> Synchronizing local ports tree from file:///opt/local/myports
> Creating po
Today I tried syncing and it failed, see log below. It succeeded when I moved
the portfile away. Base is from source.
$ sudo port -v sync
---> Updating the ports tree
Synchronizing local ports tree from file:///opt/local/myports
Creating port index in /opt/local/myports
Total number of ports p
11 matches
Mail list logo
