Hi, I'm getting the following error running on a new M1 mac:
[ERROR] Failed to execute goal com.github.warmuuh:libsass-maven-plugin:0.2.10-libsass_3.5.3:compile (default) on project unive-business-cim-extension: Execution default of goal com.github.warmuuh:libsass-maven-plugin:0.2.10-libsass_3.5.3:compile failed: An API incompatibility was encountered while executing com.github.warmuuh:libsass-maven-plugin:0.2.10-libsass_3.5.3:compile: java.lang.UnsatisfiedLinkError: Can't load library: /var/folders/rb/wh4yym_n4yvgvt5g4wlp3y200000gq/T/libjsass-17043604973941698034/libjsass.dylib
I read that this is likely related to mac os tmp directories being mounted with 'noexec', so I've tried changing the temp directory with the TMPDIR environment property and changing the java.io.tmpdir java property values to write to a directory with exec rights, but with no results.
This is a long existing project that builds fine on everyone else's (non-M1) machine. Is this a known problem, or is there a workaround I could use?
mvn -v:
Maven home: /opt/homebrew/Cellar/maven/3.8.6/libexec
Java version: 18.0.2, vendor: Homebrew, runtime: /opt/homebrew/Cellar/openjdk/18.0.2/libexec/openjdk.jdk/Contents/Home
Default locale: en_NL, platform encoding: UTF-8
OS name: "mac os x", version: "12.2.1", arch: "aarch64", family: "mac"
Hi, I'm getting the following error running on a new M1 mac:
[ERROR] Failed to execute goal com.github.warmuuh:libsass-maven-plugin:0.2.10-libsass_3.5.3:compile (default) on project unive-business-cim-extension: Execution default of goal com.github.warmuuh:libsass-maven-plugin:0.2.10-libsass_3.5.3:compile failed: An API incompatibility was encountered while executing com.github.warmuuh:libsass-maven-plugin:0.2.10-libsass_3.5.3:compile: java.lang.UnsatisfiedLinkError: Can't load library: /var/folders/rb/wh4yym_n4yvgvt5g4wlp3y200000gq/T/libjsass-17043604973941698034/libjsass.dylibI read that this is likely related to mac os tmp directories being mounted with 'noexec', so I've tried changing the temp directory with the TMPDIR environment property and changing the java.io.tmpdir java property values to write to a directory with exec rights, but with no results.
This is a long existing project that builds fine on everyone else's (non-M1) machine. Is this a known problem, or is there a workaround I could use?
mvn -v: