yoyo@home auf macOS Catalina (10.15.2)

[dhh]

Mit ogr und ecm habe ich es ausprobiert, aber es brechen unter macOS Catalina (10.15.2) derzeit alle Jobs mit derselben Fehlermeldung (boinc stderr out)) ab:

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 255 (0xff, -1)</message>
<stderr_txt>
Process creation (../../projects/www.rechenkraft.net_yoyo/ecmwrapper_705.01_x86_64-apple-darwin) failed: Bad CPU type in executable (errno = -1)

</stderr_txt>
]]>

Gibt's noch generelle Probleme mit yoyo unter macOS in seiner aktuellen Version?

[JeromeC]

Hi

I find this old thread (with no answer) by searching "Bad CPU type in executable" : I have the exact same error under macOS 13.3.1 on a late 2020 Intel iMac

<core_client_version>7.20.7</core_client_version>
<![CDATA[
<message>
process exited with code 255 (0xff, -1)</message>
<stderr_txt>
Process creation (../../projects/www.rechenkraft.net_yoyo/ecmwrapper_705.02_x86_64-apple-darwin) failed: Bad CPU type in executable (errno = -1)

</stderr_txt>
]]>

Do we know the issue and the solution ?

Thanks.

[Olli-NUX]

Hi,

I think the ecmwrapper_705.02_x86_64-apple-darwin binary is not "x86_64-apple-darwin":

lipo -i ecmwrapper_705.02_x86_64-apple-darwin
Architectures in the fat file: ecmwrapper_705.02_x86_64-apple-darwin are: i386 ppc

and produces this error: bad CPU type in executable: ./ecmwrapper_705.02_x86_64-apple-darwin

The ecm-7.0.4-x86_64-apple-darwin binary looks good:
lipo -i ./ecm-7.0.4-x86_64-apple-darwin
Architectures in the fat file: ./ecm-7.0.4-x86_64-apple-darwin are: x86_64 arm64

I hope that helps the Rechenkraft Developer Team to solve this problem.

[Olli-NUX]

double posting, sry.

[Michael H.W. Weber]

No double postings please...
Not sure which one to keep - so, please correct what is okay and delete the other post or I will have to delete one of them.

Michael.

[JeromeC]

So does this mean that someone at yoyo can have a look at this problem considering the information provided by Olli-NUX ?