+1 for 20th Oct 1300 UTC
On Fri, Oct 19, 2018 at 1:45 PM Umesh Singla wrote:
> +1 for 20th Oct, 1300 UTC
>
> On Sun, Oct 14, 2018 at 10:59 PM Mojca Miklavec
> wrote:
>
>> Hi,
>>
>> What do you think about another MacPorts online meeting next Saturday
>> (20th) at 13:00 UTC?
>>
>> If you are int
I am unable to find anything from Apple on the specific changes that
have been made to command line app compilation in Mojave.
I think what has been done is that /usr/include has been moved, and longs
and pointers are now 64 bits. Do I have that right?
--
Randolph M. Fritz
Here's a very old list from Apple; anyone care to say if it is still
correct?
https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/64bitPorting/transition/transition.html
--
Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com
On Fri, Oct 19, 2018 at 2:06 PM Randolp
On 2018-10-20 08:06 , Randolph M. Fritz wrote:
> I am unable to find anything from Apple on the specific changes that
> have been made to command line app compilation in Mojave.
>
> I think what has been done is that /usr/include has been moved, and
> longs and pointers are now 64 bits. Do I have
That document is still correct as far as it goes.
- Josh
On 2018-10-20 08:14 , Randolph M. Fritz wrote:
> Here's a very old list from Apple; anyone care to say if it is still
> correct?
>
> https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/64bitPorting/transition/transi
On 2018-10-20 08:39 , Joshua Root wrote:
> On 2018-10-20 08:06 , Randolph M. Fritz wrote:
>> I am unable to find anything from Apple on the specific changes that
>> have been made to command line app compilation in Mojave.
>>
>> I think what has been done is that /usr/include has been moved, and
>>
I have another port that I can't update due to a too-old icu (mozjs60).
I think we're going to have to find some way to update icu. If we need a
non-c++11 version, I guess we'll have to make that as a separate port perhaps.
Ken
On Oct 19, 2018, at 20:02, Ken Cunningham wrote:
> I have another port that I can't update due to a too-old icu (mozjs60).
>
> I think we're going to have to find some way to update icu. If we need a
> non-c++11 version, I guess we'll have to make that as a separate port perhaps.
I don't kno
