kicad-developers team mailing list archive

[Seth Hillbrand <seth@xxxxxxxxxxxxx>]

Ah, so this may have been a tempest in a teapot.

I've only been able to recreate/force an error with the 5.0.0 stable build
under Mojave.  Does not recreate for 5.0.1 nightly build.  And I can't
downgrade to check whether the issue existed under 10.13.  Adam is running
his regression checks to verify nothing has changed.

In the meantime, I'm going to finalize the SEGZONE fix for that last bug
report.  Should be set for tomorrow if we still want to kick this out on
schedule.

-S

Am Sa., 29. Sep. 2018 um 01:11 Uhr schrieb Bernhard Stegmaier <
stegmaier@xxxxxxxxxxxxx>:

> I did switch to Mojave almost all of my machines.
> My (own) old builds run without any problem on all of the Mojave machines.
>
> I just tried the latest nightly and it also works for me.
> Only thing I have is that it sometimes doesn’t work on first start
> (nothing happens) but if I try again.
> But, that’s something that I always had with the official builds… don’t
> know what the issues is here (I guess something with the security settings).
>
> More details on this?
>
>
> Regards
> Bernhard
>
> On 29. Sep 2018, at 03:50, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
>
> I am not 100% up to speed on what's broken yet.
>
> Just for clarifications, we have to compile our nightly builds with the
> oldest SDK we want to support, not the newest.  The issues we've had when
> 10.11, 10.12, and 10.13 came out were all issues where users on the new
> version were unable to compile KiCad without special patches (either to
> KiCad or to the dependencies)
>
> I am surprised we have issues running our old binaries rather than in
> compilation, but in computers, not only do things not work consistently,
> they don't even break consistently! :)
>
>
> On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
>
>> I've been out on business travel this week so I haven't been able to
>> attend to this at all.  This might not be a hard problem to fix, but
>> sometimes it takes a bit as it can be an issue in a dependency.
>>
>> Between Seth and I this weekend I'm pretty sure we can get a good handle
>> on the problem, but solving it might take a few more days.
>>
>> Adam
>>
>> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand <seth@xxxxxxxxxxxxx>
>> wrote:
>>
>>> Hi Devs-
>>>
>>> We currently have an issue where KiCad does not run at all on MacOS
>>> Mojave that was just released.  It may just be a matter of re-running the
>>> full compile using the Mojave SDK but we should get that running on our
>>> nightly builds.
>>>
>>> This normally might not be that big of an issue but the MacOS releases
>>> are free downloads and get pushed pretty hard with pop-ups, so I expect
>>> many users will upgrade soon with no downgrade path.
>>>
>>> I know we were hoping to tag 5.0.1 this weekend but can we see if there
>>> need to be any post-fixes to get the Mac building for Mojave before we do
>>> that?
>>>
>>> Thanks-
>>> Seth
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>