Yes, I decided to fix the problem in a way that didn't require changing
nightly/wrap-nightly-mac.sh, to avoid additional headaches.

I saw the Mac x86 problem but have only just worked out what caused it.

On Wed, 13 May 2020 at 22:21, James Paige <b...@hamsterrepublic.com> wrote:

> Apparently I don't need to manually update that file, because it looks
> like at least the x86_64 build on Mac succeeded after your fix.
>
> The Windows build also succeeded.
>
> Looks like the only remaining breakage is the Mac x86 build.
>
> On Tue, May 12, 2020, 9:07 PM Ralph Versteegen <teeem...@gmail.com> wrote:
>
>> I never doubted that those changes would break something :)
>> It broke my mxe (Windows) cross-compiling script too. What broke that and
>> the Windows nightlies is falling back to gcc if there's no "cc" not working.
>> As for the Mac nightly, I see the problem is that I renamed the GCC
>> envvar to FBCC, so nightly/wrap-nightly-mac.sh needs updating. Do you need
>> to install updates to that manually?
>>
>> On Mon, 11 May 2020 at 22:22, James Paige <b...@hamsterrepublic.com>
>> wrote:
>>
>>> Looks like both the Windows and Mac nightly builds are failing in
>>> different ways.
>>>
>>> Maybe the recent scons refactoring?
>>>
>>> The Linux and Android builds seem fine.
>>>
>>> ---
>>> James
>>> _______________________________________________
>>> Ohrrpgce mailing list
>>> ohrrpgce@lists.motherhamster.org
>>> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
>>>
>> _______________________________________________
>> Ohrrpgce mailing list
>> ohrrpgce@lists.motherhamster.org
>> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
>>
> _______________________________________________
> Ohrrpgce mailing list
> ohrrpgce@lists.motherhamster.org
> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
>
_______________________________________________
Ohrrpgce mailing list
ohrrpgce@lists.motherhamster.org
http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org

Reply via email to