Code failed to build on Mac M1

Question

Code failed to build on Mac M1

testn opened this issue a year ago · comments

testn commented a year ago

It seems to refer to the older version of Eclipse which does not support Mac M1

Guillaume Toison · Answer 1 · Wed Aug 16 2023 02:58:43 GMT+0800 (China Standard Time)

This should be fixed according to #2507

Jeremy Landis · Answer 2 · Wed Aug 16 2023 07:13:16 GMT+0800 (China Standard Time)

closing as addressed. Further we expect after this next release to start raising our jdk requirements so we can then bring eclipse up much further. it is true its stuck in time but we are aware of the issues and working on it. As noted this was fixed already on master with changes I did earlier. The PR noted will show multi platform usage. If still an issue after this next release, please reopen but as noted we will fast track moving up to newer releases.

Patrik Süli · Answer 3 · Fri Oct 06 2023 17:48:30 GMT+0800 (China Standard Time)

Hello! I still have this kind of problem. I'm on an Apple Mac M2 with Sonoma 14.0.
On a ./gradlew clean bulld I get the following message:

Execution failed for task ':eclipsePlugin:compileJava'.
> Could not resolve all files for configuration ':eclipsePlugin:compileClasspath'.
   > Could not find org.eclipse.platform:org.eclipse.swt.cocoa.macosx.aarch64:3.113.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/eclipse/platform/org.eclipse.swt.cocoa.macosx.aarch64/3.113.0/org.eclipse.swt.cocoa.macosx.aarch64-3.113.0.pom
     Required by:
         project :eclipsePlugin > org.eclipse.platform:org.eclipse.swt:3.113.0

Currently the only way, is a workaround: I exclude these modules from the build process:

./gradlew clean build -x :eclipsePlugin:compileJava -x :eclipsePlugin-junit:compileTestJava -x :eclipsePlugin-test:compileJava -x :eclipsePlugin-test:checkstyleMain

Judit Knoll · Answer 4 · Fri Oct 06 2023 19:30:37 GMT+0800 (China Standard Time)

It seems like, this issue is still relevant.
It looks like the macos-latest in the GitHub Action is using Intel architecture, not the arm64 (M1) one, that's why it didn't have this problem. There are M1 macOS runners (see actions/runner-images#8439), but it's not available for opensource projects for free.

Jeremy Landis · Answer 5 · Sat Oct 07 2023 05:16:01 GMT+0800 (China Standard Time)

Are you building from latest master? The version you listed is older than our current master and latest eclipse supports the arm module at least per eclipse github. The 3.113 version is from 2019. I think if you rebase it may work. Clearly 2019 eclipse would not support that arch type 😉 Now even if that solves it for you, we are going to slightly move back to eclipse 4.25 release so you may want to check existing recent pull request I raised a few days ago to check it as well. Thanks for work around in any case as it may help other contributors. Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Judit Knoll ***@***.***> Sent: Friday, October 6, 2023 7:30:47 AM To: spotbugs/spotbugs ***@***.***> Cc: Jeremy Landis ***@***.***>; Assign ***@***.***> Subject: Re: [spotbugs/spotbugs] Code failed to build on Mac M1 (Issue #2280) It seems like, this issue is still relevant. It looks like the macos-latest in the GitHub Action is using Intel architecture, not the arm64 one, that's why it didn't have this problem. There are M1 macOS runners (see actions/runner-images#8439<actions/runner-images#8439>), but it's not available for opensource project for free. — Reply to this email directly, view it on GitHub<#2280 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHODI7Q2CODVQQJHKMXPJDX57TWPAVCNFSM6AAAAAAS7OSUX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJQGQ3TEMZTGI>. You are receiving this because you were assigned.Message ID: ***@***.***>

Patrik Süli · Answer 6 · Sat Oct 07 2023 15:25:03 GMT+0800 (China Standard Time)

@hazendaz I built from the head of the master branch, so it's up to date. I get the following dependency tree:
dependencies.zip

I tried to run ./gradlew clean --refresh-dependencies but I still have the same result.

If I change the https://github.com/spotbugs/spotbugs/blob/master/buildSrc/src/main/kotlin/eclipse-convention.gradle.kts#L10 version to newer, like 4.29.0, it's compile. So maybe we should simply update this version.

Jeremy Landis · Answer 7 · Sat Oct 07 2023 22:48:26 GMT+0800 (China Standard Time)

Thanks I see your pull request. I simply had missed that one. Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Patrik Süli ***@***.***> Sent: Saturday, October 7, 2023 3:25:14 AM To: spotbugs/spotbugs ***@***.***> Cc: Jeremy Landis ***@***.***>; Mention ***@***.***> Subject: Re: [spotbugs/spotbugs] Code failed to build on Mac M1 (Issue #2280) @hazendaz<https://github.com/hazendaz> I built from the head of the master branch, so it's up to date. I get the following dependency tree: dependencies.zip<https://github.com/spotbugs/spotbugs/files/12837061/dependencies.zip> I tried to ./gradlew clean --refresh-dependencies but I still have the same result. If I change the https://github.com/spotbugs/spotbugs/blob/master/buildSrc/src/main/kotlin/eclipse-convention.gradle.kts#L10 version to newer, like 4.29.0, it's compile. So maybe we should simply update this version. — Reply to this email directly, view it on GitHub<#2280 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHODI6PW54XELQ6ICOYL6LX6D7VVAVCNFSM6AAAAAAS7OSUX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGYZTGNZTGI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

Judit Knoll · Answer 8 · Mon Oct 09 2023 15:32:11 GMT+0800 (China Standard Time)

Since #2611 got merged, closing this issue. Thank you for checking and the PR, @Spatrik95 !