On Sep 26, 2019, at 00:04, Mojca Miklavec wrote:
> On Thu, 26 Sep 2019 at 06:26, Ryan Schmidt wrote:
>
>> On Sep 25, 2019, at 00:43, Mojca Miklavec wrote:
>>
>>> I already mentioned this in the past, but I would like to repeat.
>>> When someone opens our homepage and wants to download
On Thu, 26 Sep 2019 at 06:26, Ryan Schmidt wrote:
>
>
>
> On Sep 25, 2019, at 00:43, Mojca Miklavec wrote:
>
> > I already mentioned this in the past, but I would like to repeat.
> > When someone opens our homepage and wants to download MacPorts using
> > Safari on, say, 10.6, the download link
On Sep 25, 2019, at 00:43, Mojca Miklavec wrote:
> I already mentioned this in the past, but I would like to repeat.
> When someone opens our homepage and wants to download MacPorts using
> Safari on, say, 10.6, the download link from GitHub doesn't work, and
> it's not trivial for users to
For purposes of testing newer libc++ versions, and as there are some new
features in newer libc++ (filesystem, eg) releases that will soon become
attractive, it would be desirable if we could find a way to build software
against a different libc++ than the one in the system's lib directory.
I
Beyond the /usr/include issue, Xcode 11 should be problematic when its
bundled 10.15 SDK is used under either Mojave or Catalina due to the
enforced use of the availability attribute in the headers.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
On Wed, Sep 25, 2019 at 5:46 AM Chris Jones
(*) The package to add back /usr/include currently does not exist in
10.15 beta, so unless it reappears come final release this is going to
be more of a problem there….
This package is not going to be coming back:
