Closed gcatanese closed 3 years ago
@ajthom90 have you seen this error before?
I have not seen that error before. I haven’t used my ARM Mac for development in some time, so I’m not sure how the latest versions of Node are working on Big Sur on M1.
My first instinct is that maybe @gcatanese doesn’t have Rosetta 2 installed? When I did my testing a couple months back, Node ran great under Rosetta, however that was a couple months ago, and maybe later versions of Node are different. I’d suggest maybe trying different versions of Node. I believe the one I had working was 15.4.0, but I can’t remember for sure.
I can try and do some testing, but I’m currently out of town and won’t be back until on Tuesday, so that is the earliest I could try it.
@eirslett @ajthom90 I have installed Rosetta (also upgraded Big Sur but I am not sure it is relevant) and I can now build it.
What was confusing is that (without Rosetta) I was able to run yarn (yarn --version
or yarn build
) without problems (even using the distribution downloaded by the frontend-maven-plugin), but it would not build during the Maven build.
Thank you very much for looking into it, this can be now closed I believe.
I have used version v1.11.2 for some time without problems on Windows but I have now a problem building the same code on the MacBook Pro M1 (Big Sur)
Here is the Maven pom
current behavior When packaging (
mvn package
)the application I get: Bad CPU type in executableSee logs
Steps to reproduce. Run
mvn package
. Here is the POM fileFrontend-maven-plugin and operating system version. Frontend-Maven-Plugin v1.11.2 MacBook Pro M1 BigSur