protoc-gen-grpc-java not available on apple m1 #7690

reinmind · 2020-12-03T08:42:02Z

What version of gRPC-Java are you using?

1.34.0

What is your environment?

osx 11.0.1

What did you expect to see?

build success

What did you see instead?

[INFO] --- protobuf-maven-plugin:0.6.1:compile (default-cli) @ grpc ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.720 s
[INFO] Finished at: 2020-12-03T16:37:02+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile (default-cli) on project grpc: Unable to resolve artifact: Missing:
[ERROR] ----------
[ERROR] 1) com.google.protobuf:protoc:exe:osx-aarch_64:3.12.0
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=com.google.protobuf -DartifactId=protoc -Dversion=3.12.0 -Dclassifier=osx-aarch_64 -Dpackaging=exe -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=com.google.protobuf -DartifactId=protoc -Dversion=3.12.0 -Dclassifier=osx-aarch_64 -Dpackaging=exe -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) com.reinmind:grpc:jar:1.0-SNAPSHOT
[ERROR]   	2) com.google.protobuf:protoc:exe:osx-aarch_64:3.12.0
[ERROR] 
[ERROR] ----------
[ERROR] 1 required artifact is missing.
[ERROR] 
[ERROR] for artifact: 
[ERROR]   com.reinmind:grpc:jar:1.0-SNAPSHOT
[ERROR] 
[ERROR] from the specified remote repositories:
[ERROR]   aliyunmaven (https://maven.aliyun.com/repository/public, releases=true, snapshots=false)
[ERROR] 
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Steps to reproduce the bug

mvn protobuf:compile

The text was updated successfully, but these errors were encountered:

ejona86 · 2020-12-03T17:56:28Z

Yes, we do not produce binaries for arm64 macs.

Edit: Summary of the long issue: The easiest thing to do as a consumer is to install Rosetta. With it installed, the Intel binary works fine. If you'd like to contribute, see #7690 (comment) . Easiest plan is to build protobuf and the grpc plugin as universal binaries.

ejona86 · 2020-12-03T17:58:43Z

Since this is the grpc repo, I've called out protoc-gen-grpc-java not being available. Although your actual error is protoc itself, which would be part of the protobuf project. If grpc gets to building it first, then we'd need to add support in protobuf as well.

gaurav46 · 2020-12-17T02:39:25Z

Hi @ejona86
Is it possible for any workaround like to set osdetector.arch as x86_64 to get the complication done ?
I tried to set below in gradle.properties but it still looks for osx-aarch_64 binaries from maven.
org.gradle.jvmargs=-Dos.detected.name=osx -Dos.detected.arch=x86_64 -Dos.detected.classifier=osx-x86_64

ejona86 · 2020-12-17T04:25:27Z

To manually specify the classifier, for Gradle:

protobuf {
  protoc {
    artifact = 'com.google.protobuf:protoc:3.14.0:osx-x86_64'
  }
}

I'm less familiar with the Maven plugin, but I think it may be something like:

<protocArtifact>com.google.protobuf:protoc:3.14.0:exe:osx-x86_64</protocArtifact>

You can do the same for protoc-gen-grpc-java.

gaurav46 · 2020-12-17T12:02:01Z

Thanks @ejona86 . That worked out.

zjc17 · 2021-01-14T06:56:53Z

Thanks @ejona86 , But How can I keep other platform like linux-x86_64 when the project being compiled on other platform?

ejona86 · 2021-01-14T17:08:26Z

@Jiachen-Zhang

protobuf {
  protoc {
    if (osdetector.os == "osx") {
      artifact = 'com.google.protobuf:protoc:3.14.0:osx-x86_64'
    } else {
      artifact = 'com.google.protobuf:protoc:3.14.0'
    }
  }
}

You can also use project properties to only change the behavior when explicitly requested.

zjc17 · 2021-01-15T03:20:48Z

@Jiachen-Zhang
protobuf {
  protoc {
    if (osdetector.os == "osx") {
      artifact = 'com.google.protobuf:protoc:3.14.0:osx-x86_64'
    } else {
      artifact = 'com.google.protobuf:protoc:3.14.0'
    }
  }
}
You can also use project properties to only change the behavior when explicitly requested.

Thanks!

Finally, I made it by

// for apple m1, please add protoc_platform=osx-x86_64 in $HOME/.gradle/gradle.properties
if (project.hasProperty('protoc_platform')) {
    artifact = "com.google.protobuf:protoc:3.13.0:${protoc_platform}"
} else {
    artifact = "com.google.protobuf:protoc:3.13.0"
}

hu-chia · 2021-02-03T11:03:44Z

for me, add this to ~/.m2/settings.xml, it worked:

<settings>
  ...
  <activeProfiles>
    <activeProfile>
      apple-silicon
    </activeProfile>
    ...
  </activeProfiles>
  <profiles>
    <profile>
      <id>apple-silicon</id>
      <properties>
        <os.detected.classifier>osx-x86_64</os.detected.classifier>
      </properties>
    </profile>
    ...
  </profiles>
  ...
</settings>

Uditmittal · 2021-02-23T11:19:17Z

Can you share the full setting.xml
I tried it didn't work for me?
I am using M1 with protobuf.

zjc17 · 2021-02-23T14:25:57Z

@Uditmittal
in my build.gradle file

protobuf {
    protoc {
        // for apple m1, please add protoc_platform=osx-x86_64 in $HOME/.gradle/gradle.properties
        if (project.hasProperty('protoc_platform')) {
            artifact = "com.google.protobuf:protoc:3.13.0:${protoc_platform}"
        } else {
            artifact = "com.google.protobuf:protoc:3.13.0"
        }
    }
}

in my ~/.gradle/gradle.properties file

protoc_platform=osx-x86_64

I think you can define and use variables in maven to implement this feature. Good luck

hu-chia · 2021-02-24T08:58:00Z

@Uditmittal My settings.xml is awfully long, the key is using your property overwrite kr.motd.maven:os-maven-plugin detected os classifier, if you share your settings.xml and pom.xml snippet, this may be help.

Uditmittal · 2021-02-24T09:29:15Z

<settings>
  <activeProfiles>
    <activeProfile>
      apple-silicon
    </activeProfile>
  </activeProfiles>
  <profiles>
    <profile>
      <id>apple-silicon</id>
      <properties>
        <os.detected.classifier>osx-x86_64</os.detected.classifier>
      </properties>
    </profile>
  </profiles>
</settings>

@guyeu my seetings.xml file

hu-chia · 2021-02-25T03:43:16Z

@Uditmittal This is my org.xolstice.maven.plugins:protobuf-maven-plugin build plugin configuration, the ${os.detected.classifier} value could read from active profile from settings.xml.

      <configuration>
          <protocArtifact>
              com.google.protobuf:protoc:3.1.0:exe:${os.detected.classifier}
          </protocArtifact>
          <pluginId>grpc-java</pluginId>
          <pluginArtifact>io.grpc:protoc-gen-grpc-java:1.0.0:exe:${os.detected.classifier}</pluginArtifact>
      </configuration>

Uditmittal · 2021-03-03T10:21:33Z

Thanks, it works for me.

bangbang2333 · 2021-04-26T03:32:31Z

谢谢老哥，搞定了

ejona86 · 2021-05-04T00:29:19Z

I'm not at all impressed with how hard it was to find the appropriate flags to pass to clang to make a universal binary, but it appears to be -arch arm64 -arch x86_64. Unclear if cross-compiling is as simple as -arch arm64. We can start by figuring out how to cross-compile/universal binary for protobuf. Afterward we can fight Gradle. The goal would be to let us build M1 binaries from an x86 Mac. But I don't have a Mac which means I can't help much, as develop-via-CI is a form of torture.

Just a workaround. Track grpc/grpc-java#7690 and protocolbuffers/protobuf#8557 for permanent fix

ghost · 2021-05-14T01:31:14Z

@ejona86 Have you had any success building from source for AArch64? I am interested in helping moving this along...

ejona86 · 2021-05-14T16:04:44Z

@jjones-figure, no, as I said, I don't have a Mac, so I can't really help much here. We totally build from source for AArch64 already on Linux. But it is a different toolchain for M1.

ejona86 · 2021-06-02T21:06:49Z

protocolbuffers/protobuf#8557 just went into protobuf based on my suggestion to just copy the current x86 binary to an arm64 name until we have actual M1 support. That doesn't "fix" this, but it does resolve the main user-visible issues and doesn't turn out to be too hacky.

I think that is as simple as making a copy of the "exe" and the hashes/signature in our upload_artifacts.sh script.

vvWantHealthLife · 2024-01-31T03:04:42Z

thanks that's work

martin-traverse · 2024-03-01T18:11:49Z

March 2024. My build started working when I installed Rosetta. I'm using the Gradle protobuf plugin and did not need to change the Gradle build scripts. I echo the comments above, it would be good to have native binaries before the drop-dead date.

Another note, it seems this is already done for the protoc compiler itself, only the gRPC plugin is causing problems. I have three modules using protoc, only one of which also uses the gRPC plugin. The others just use base protoc and they built fine without needing to install Rosetta. Can the same approach that was used for the base protoc be replicated here?

ejona86 · 2024-03-04T16:30:22Z

@martin-traverse, protobuf's release build used to be like ours. But they changed it dramatically and it is now based on Bazel. Looks like they are using --cpu= to build aarch_64 and x86_64 individually. They have quite specific toolchain configuration. On the release, they have three osx binaries: aarch_64, x86_64, and universal_binary. I don't see the code that makes the universal binary.

We are using autotools right now to build protobuf, and then using Gradle to build the plugin. But we've not been able to absorb the absl dependency in newer protobuf versions. I have a change to swap to cmake to build protobuf, but pkg-config is now required and that caused trouble on Windows. More recently pkgconf has taken off, so we might now have a solution there.

Since absl was added to protobuf, I have considered moving the plugin compilation out of Gradle. That could be a stepping-stone to using Bazel. But I think that is too much to depend on here. I still believe this just needs a few flags when building (like #7690 (comment), or the --cpu flags). But that really needs someone with a Mac to figure it out.

Areeb786123 · 2024-03-05T18:25:40Z

@Uditmittal in my build.gradle file

protobuf {
    protoc {
        // for apple m1, please add protoc_platform=osx-x86_64 in $HOME/.gradle/gradle.properties
        if (project.hasProperty('protoc_platform')) {
            artifact = "com.google.protobuf:protoc:3.13.0:${protoc_platform}"
        } else {
            artifact = "com.google.protobuf:protoc:3.13.0"
        }
    }
}

in my ~/.gradle/gradle.properties file

protoc_platform=osx-x86_64

I think you can define and use variables in maven to implement this feature. Good luck

@Jiachen-Zhang
protobuf {
  protoc {
    if (osdetector.os == "osx") {
      artifact = 'com.google.protobuf:protoc:3.14.0:osx-x86_64'
    } else {
      artifact = 'com.google.protobuf:protoc:3.14.0'
    }
  }
}
You can also use project properties to only change the behavior when explicitly requested.

it didn't work for me

gaofeiseu · 2024-03-06T13:10:02Z

in my case, this will works well:
if you have a pom file and use maven plugin to complie the target package, for example:

so, what you need to do is specify a fixed value for the position pointed by the arrow, the fixed value is osx-x86_64 , it's x86 mac os actual value.

amraupward · 2024-04-03T08:25:53Z

com.google.protobuf:protoc:3.14.0:osx-x86_64
Title:
Build fails on macOS M2 with generateProto task error

Body:

Environment
OS: macOS M2
Gradle Version: (Specify your Gradle version here)
Java Version: (Specify your Java version here)
Protobuf Plugin Version: 0.9.4
gRPC Version: 1.62.2
Spring Boot Version: 3.2.3
OpenAPI Generator Version: 7.3.0
Issue Description
When attempting to build my project on a macOS M2 machine using Docker, the build fails during the generateProto task. The failure is related to the Protobuf and gRPC setup in my build.gradle.

Error Log

Steps to Reproduce
Run gradle bootJar -x test --no-daemon inside a Docker container on a macOS M2 machine.

`protobuf {
protoc {
if (osdetector.os == 'osx' && osdetector.arch == 'aarch_64') {
artifact = 'com.google.protobuf:protoc:3.25.3:osx-x86_64'
} else {
artifact = 'com.google.protobuf:protoc:3.25.3'
}
}
plugins {
if (osdetector.os == 'osx'){
grpc {
artifact = 'io.grpc:protoc-gen-grpc-java:1.62.2:osx-x86_64'
}
} else {
grpc {
artifact = 'io.grpc:protoc-gen-grpc-java:1.62.2'
}
}
}
generateProtoTasks {
all()*.plugins {
grpc {}
}
}
}

dependencies {
// gRPC
implementation 'com.google.protobuf:protobuf-java:3.25.3'
implementation 'io.grpc:grpc-protobuf:1.62.2'
implementation 'io.grpc:grpc-stub:1.62.2'
runtimeOnly 'io.grpc:grpc-netty-shaded:1.62.2'
}

plugins {
id 'java'
id 'org.springframework.boot' version '3.2.3'
id 'io.spring.dependency-management' version '1.1.4'
id 'org.openapi.generator' version '7.3.0'
id 'maven-publish'
id 'com.google.protobuf' version '0.9.4'
id "io.github.lognet.grpc-spring-boot" version '5.0.0'
}`

Expected Behavior
The project builds successfully without errors related to the generateProto task.

Actual Behavior
The build fails with an error indicating an issue with executing protoc or the gRPC plugin.

siddhsql · 2024-04-08T23:01:04Z

any update on this issue? everyone is on M1/M2 chips these days.

amraupward · 2024-04-09T01:23:18Z

any update on this issue? everyone is on M1/M2 chips these days.

M2 Macbook Air.

build.gradle

protobuf {
protoc {
artifact = "com.google.protobuf:protoc:3.25.1"
}
plugins {
grpc {
artifact = 'io.grpc:protoc-gen-grpc-java:1.52.1' // <----- this version can build your java
}
}
generateProtoTasks {
all()*.plugins {
grpc {}
}
}
}

if you want to create docker image.

FROM jdk as gradle_cache
RUN mkdir -p /tmp/gradle/cache
ENV GRADLE_USER_HOME /tmp/gradle/cache
ARG GPR_USERNAME
ARG GPR_TOKEN
ENV GPR_USERNAME $GPR_USERNAME
ENV GPR_TOKEN $GPR_TOKEN
ENV GRADLE_OPTS="-Xmx4g -XX:+UseContainerSupport -Dfile.encoding=UTF-8". // <----- this is important
COPY build.gradle /tmp
WORKDIR /tmp/
RUN gradle clean build -i --stacktrace --no-daemon

and

dockerbuild.sh
docker buildx build
--platform linux/amd64 --load \ //<------------ this too.
-t "$LOCAL_TAG"
-t "$AZURE_LOCAL_TAG"
--build-arg GPR_USERNAME=$GPR_USERNAME
--build-arg GPR_TOKEN=$GPR_TOKEN
--quiet=false
--output=type=docker
-f ./docker.dockerfile .

NSKryukov · 2024-05-15T13:09:31Z

  <properties>
    <os.detected.classifier>osx-x86_64</os.detected.classifier>
  </properties>

thx a lot. only one way it worked!

Karm · 2024-05-23T12:35:29Z

Oh, it seems I hit this again, trying to download osx-aarch64 file only to find out it's actually a Mach-0 x86_64 binary: grpc/grpc.io#1296

Ivan-Kurochenko · 2024-05-23T12:38:22Z

protobuf {
    protoc {
        if (osdetector.os == "osx") {
            artifact = 'com.google.protobuf:protoc:3.14.0:osx-x86_64'
        } else {
            artifact = 'com.google.protobuf:protoc:3.14.0'
        }
    }
}

I have pasted this code, and I have received another error.

Execution failed for task ':generateProto'.
> Could not resolve all files for configuration ':protobufToolsLocator_grpc'.
   > Could not find protoc-gen-grpc-java-1.28.1-osx-aarch_64.exe (io.grpc:protoc-gen-grpc-java:1.28.1).
     Searched in the following locations:
         https://repo.maven.apache.org/maven2/io/grpc/protoc-gen-grpc-java/1.28.1/protoc-gen-grpc-java-1.28.1-osx-aarch_64.exe

* Try:

Karm · 2024-05-23T13:02:07Z

@Ivan-Kurochenko There is no such file on that location, is it? See https://repo.maven.apache.org/maven2/io/grpc/protoc-gen-grpc-java/1.28.1/

If you upgrade to e.g. https://repo.maven.apache.org/maven2/io/grpc/protoc-gen-grpc-java/1.64.0/ you can see there is an osx-aarch_64 file now.

The problem is though that it is in fact x86_64 binary and your aarch64 system won't run it:

% file ./protoc-gen-grpc-java-1.64.0-osx-aarch_64.exe
./protoc-gen-grpc-java-1.64.0-osx-aarch_64.exe: Mach-O 64-bit executable x86_64

zsh: bad CPU type in executable: ./protoc-gen-grpc-java-1.64.0-osx-aarch_64.exe

So you'd need to have Rosetta installed so as your Mac OS can translate amd64 machine code do aarch64 machine code...

Ivan-Kurochenko · 2024-05-23T13:57:03Z

@Karm I installed Rosetta.

% lsbom -f /Library/Apple/System/Library/Receipts/com.apple.pkg.RosettaUpdateAuto.bom
./Library/Apple/usr/lib/libRosettaAot.dylib	100755	0/0	320896	219430798
./Library/Apple/usr/libexec/oah/RosettaLinux/rosetta	100755	0/0	16608881085004749
./Library/Apple/usr/libexec/oah/RosettaLinux/rosettad	100755	0/0	298792	794611390
./Library/Apple/usr/libexec/oah/libRosettaRuntime	100755	0/0	381680	959649284
./Library/Apple/usr/share/rosetta/rosetta	100644	0/0	64	1875722922

Ivan-Kurochenko · 2024-05-23T14:00:43Z

@Karm Do you have another idea, of how I can get rid of the protoc.3.13 for arm?

Karm · 2024-06-06T08:31:58Z

@Ivan-Kurochenko I am sorry, I don't understand the question.

huydqdev · 2024-06-07T08:52:26Z

i dont use Rosetta and this one work for me

protobuf {
  protoc {
    artifact = 'com.google.protobuf:protoc:3.14.0'
    path = '/opt/homebrew/bin/protoc'
  }
}

after
brew install protobuf
and find the path
which protoc

yash-brahmkshatriya · 2024-06-19T04:13:13Z

For M1 chip,

I had to install rosetta to make it work.

    <properties>
        <protoc.version>4.27.1</protoc.version>
        <grpc.version>1.64.0</grpc.version>

        <maven.compiler.source>17</maven.compiler.source>
        <maven.compiler.target>17</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>


    <dependencies>
        <dependency>
            <groupId>com.google.protobuf</groupId>
            <artifactId>protobuf-java</artifactId>
            <version>${protoc.version}</version>
        </dependency>
        <dependency>
            <groupId>com.google.protobuf</groupId>
            <artifactId>protobuf-java-util</artifactId>
            <version>${protoc.version}</version>
        </dependency>
        <dependency>
            <groupId>io.grpc</groupId>
            <artifactId>protoc-gen-grpc-java</artifactId>
            <version>${grpc.version}</version>
            <type>pom</type>
        </dependency>
        <dependency>
            <groupId>io.grpc</groupId>
            <artifactId>grpc-stub</artifactId>
            <version>${grpc.version}</version>
        </dependency>
        <dependency>
            <groupId>io.grpc</groupId>
            <artifactId>grpc-protobuf</artifactId>
            <version>${grpc.version}</version>
        </dependency>
        <dependency>
            <groupId>org.apache.tomcat</groupId>
            <artifactId>annotations-api</artifactId>
            <version>6.0.53</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

    <build>
        <extensions>
            <extension>
                <groupId>kr.motd.maven</groupId>
                <artifactId>os-maven-plugin</artifactId>
                <version>1.7.1</version>
            </extension>
        </extensions>
        <plugins>
            <plugin>
                <groupId>org.xolstice.maven.plugins</groupId>
                <artifactId>protobuf-maven-plugin</artifactId>
                <version>0.6.1</version>
                <configuration>
                    <protocArtifact>com.google.protobuf:protoc:${protoc.version}:exe:${os.detected.classifier}</protocArtifact>
                    <pluginId>grpc-java</pluginId>
                    <pluginArtifact>io.grpc:protoc-gen-grpc-java:${grpc.version}:exe:${os.detected.classifier}</pluginArtifact>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>compile</goal>
                            <goal>compile-custom</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>

shalk · 2024-06-25T08:50:10Z

i read https://github.com/grpc/grpc-java/releases/tag/v1.62.2

The protoc plugin no longer supports macOS Big Sur (macOS 11). Binaries are now built using Monterey (macOS 12)

What is the change ?

gharia · 2024-07-16T15:09:40Z

Is there any solution without hack for this? It works adding specific value as mentioned above, os.detected.classifier through settings.xml, but that is not a feasible solution when different team members using different OS.

ejona86 · 2024-07-16T15:19:03Z

@gharia, you don't need to do any os.detected.classifier hacks. Just make sure Rosetta is installed on OS X arm machines and use releases from 2022 or newer.

gharia · 2024-07-16T15:41:44Z

I have Rosetta installed and protoc version is 27.1

hemraj@192 .m2 % if /usr/bin/pgrep -q oahd; then echo 'rosetta installed'; fi
rosetta installed
hemraj@192 .m2 % protoc --version                                            
libprotoc 27.1

gharia · 2024-07-17T08:52:26Z

@ejona86 , could you help with this? Let me know if I am missing anything here

shalk · 2024-07-17T11:30:40Z

For M1 chip,

I had to install rosetta to make it work.

    <properties>
        <protoc.version>4.27.1</protoc.version>
        <grpc.version>1.64.0</grpc.version>

        <maven.compiler.source>17</maven.compiler.source>
        <maven.compiler.target>17</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>


    <dependencies>
        <dependency>
            <groupId>com.google.protobuf</groupId>
            <artifactId>protobuf-java</artifactId>
            <version>${protoc.version}</version>
        </dependency>
        <dependency>
            <groupId>com.google.protobuf</groupId>
            <artifactId>protobuf-java-util</artifactId>
            <version>${protoc.version}</version>
        </dependency>
        <dependency>
            <groupId>io.grpc</groupId>
            <artifactId>protoc-gen-grpc-java</artifactId>
            <version>${grpc.version}</version>
            <type>pom</type>
        </dependency>
        <dependency>
            <groupId>io.grpc</groupId>
            <artifactId>grpc-stub</artifactId>
            <version>${grpc.version}</version>
        </dependency>
        <dependency>
            <groupId>io.grpc</groupId>
            <artifactId>grpc-protobuf</artifactId>
            <version>${grpc.version}</version>
        </dependency>
        <dependency>
            <groupId>org.apache.tomcat</groupId>
            <artifactId>annotations-api</artifactId>
            <version>6.0.53</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

    <build>
        <extensions>
            <extension>
                <groupId>kr.motd.maven</groupId>
                <artifactId>os-maven-plugin</artifactId>
                <version>1.7.1</version>
            </extension>
        </extensions>
        <plugins>
            <plugin>
                <groupId>org.xolstice.maven.plugins</groupId>
                <artifactId>protobuf-maven-plugin</artifactId>
                <version>0.6.1</version>
                <configuration>
                    <protocArtifact>com.google.protobuf:protoc:${protoc.version}:exe:${os.detected.classifier}</protocArtifact>
                    <pluginId>grpc-java</pluginId>
                    <pluginArtifact>io.grpc:protoc-gen-grpc-java:${grpc.version}:exe:${os.detected.classifier}</pluginArtifact>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>compile</goal>
                            <goal>compile-custom</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>

I notice the protobuf 4.x have been supported . It is great!

gharia · 2024-07-17T13:36:31Z

Thanks @shalk those changes worked for. However I am using Protobuf version 3.25.3. I am on M2 chip

ejona86 · 2024-07-17T14:30:55Z

@gharia, you don't say what problem you are experiencing. What error do you get?

Our examples work on Rosetta-available OS X ARM64 systems. Try the Quick Start. It uses configuration essentially the same as shalk posted, but with protobuf 3.25.3. It's also essentially the same configuration as our main README.md.

@shalk, protobuf 4 still has an issue: protocolbuffers/protobuf#17247

gharia · 2024-07-17T16:55:11Z

@ejona86 , I was using older version of Protobuf release (before 2022 as you mentioned) in pom.xml

Below is my working pom.xml

<protobuf.version>3.25.3</protobuf.version>
<io.grpc.version>1.65.1</io.grpc.version>
<os72.version>3.11.4</os72.version>

<build>
        <plugins>
            <plugin>
                <groupId>com.github.os72</groupId>
                <artifactId>protoc-jar-maven-plugin</artifactId>
                <version>${os72.version}</version>
                <executions>
                    <execution>
                        <phase>generate-sources</phase>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <configuration>
                            <protocArtifact>com.google.protobuf:protoc:${protobuf.version}</protocArtifact>
                            <inputDirectories>
                                <include>src/main/resources/protobuf</include>
                            </inputDirectories>
                            <outputTargets>
                                <outputTarget>
                                    <type>java</type>
                                </outputTarget>
                                <outputTarget>
                                    <type>grpc-java</type>
                                    <pluginArtifact>io.grpc:protoc-gen-grpc-java:${io.grpc.version}</pluginArtifact>
                                </outputTarget>
                            </outputTargets>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
</build>

ejona86 added the enhancement label Dec 3, 2020

ejona86 changed the title ~~compile protobuf failed on apple m1~~ protoc-gen-grpc-java not available on apple m1 Dec 3, 2020

ejona86 added this to the Next milestone Dec 3, 2020

coolbeevip mentioned this issue Feb 26, 2021

[SCB-813] Fix the pack-contract-grpc build issue on macOSX apache/servicecomb-pack#240

Merged

1 task

michalmac mentioned this issue Apr 10, 2021

Build error in "hybridsim" and "protobuf" matsim-org/matsim-code-examples#546

Open

yuzawa-san mentioned this issue May 3, 2021

Support for Apple M1 processors google/protobuf-gradle-plugin#492

Closed

yuzawa-san mentioned this issue May 4, 2021

protoc maven artifacts: reuse osx-x86_64 for osx-aarch_64 protocolbuffers/protobuf#8557

Merged

KevinRoebert added a commit to drasyl/drasyl that referenced this issue May 6, 2021

Added workaround for protoc on Apple Silicon

a741e70

Just a workaround. Track grpc/grpc-java#7690 and protocolbuffers/protobuf#8557 for permanent fix

biklas7 mentioned this issue Sep 6, 2021

App won't build on Mac M1 PhilipsHue/flutter_reactive_ble#355

Closed

y60yu1ii mentioned this issue Oct 1, 2021

Please add protobuf setting changes to get it build on Apple Silicon M1 PhilipsHue/flutter_reactive_ble#396

Closed

rmehta19 mentioned this issue Apr 22, 2024

s2a: Add gRPC S2A #11113

Merged

ejona86 mentioned this issue May 23, 2024

osx aarch64 binaries are in fact x86_64 binaries grpc/grpc.io#1296

Closed

heliang666s mentioned this issue Sep 1, 2024

optimize: compilation and packaging for the ARM64 architecture apache/incubator-seata#6803

Merged

1 task

style95 mentioned this issue Sep 17, 2024

M1 mac compatibility apache/openwhisk#5511

Merged

22 tasks

protoc-gen-grpc-java not available on apple m1 #7690

protoc-gen-grpc-java not available on apple m1 #7690

Comments

reinmind commented Dec 3, 2020 • edited Loading

What version of gRPC-Java are you using?

What is your environment?

What did you expect to see?

What did you see instead?

Steps to reproduce the bug

ejona86 commented Dec 3, 2020 • edited Loading

ejona86 commented Dec 3, 2020

gaurav46 commented Dec 17, 2020 • edited Loading

ejona86 commented Dec 17, 2020

gaurav46 commented Dec 17, 2020

zjc17 commented Jan 14, 2021

ejona86 commented Jan 14, 2021

zjc17 commented Jan 15, 2021

hu-chia commented Feb 3, 2021 • edited Loading

Uditmittal commented Feb 23, 2021

zjc17 commented Feb 23, 2021

hu-chia commented Feb 24, 2021

Uditmittal commented Feb 24, 2021 • edited Loading

hu-chia commented Feb 25, 2021

Uditmittal commented Mar 3, 2021

bangbang2333 commented Apr 26, 2021

ejona86 commented May 4, 2021 • edited Loading

ghost commented May 14, 2021

ejona86 commented May 14, 2021

ejona86 commented Jun 2, 2021

vvWantHealthLife commented Jan 31, 2024

martin-traverse commented Mar 1, 2024

ejona86 commented Mar 4, 2024

Areeb786123 commented Mar 5, 2024

gaofeiseu commented Mar 6, 2024

amraupward commented Apr 3, 2024 • edited Loading

siddhsql commented Apr 8, 2024

amraupward commented Apr 9, 2024

NSKryukov commented May 15, 2024

Karm commented May 23, 2024

Ivan-Kurochenko commented May 23, 2024

Karm commented May 23, 2024

Ivan-Kurochenko commented May 23, 2024

Ivan-Kurochenko commented May 23, 2024

Karm commented Jun 6, 2024

huydqdev commented Jun 7, 2024

yash-brahmkshatriya commented Jun 19, 2024 • edited Loading

shalk commented Jun 25, 2024

gharia commented Jul 16, 2024 • edited Loading

ejona86 commented Jul 16, 2024

gharia commented Jul 16, 2024 • edited Loading

gharia commented Jul 17, 2024

shalk commented Jul 17, 2024

gharia commented Jul 17, 2024

ejona86 commented Jul 17, 2024

gharia commented Jul 17, 2024

reinmind commented Dec 3, 2020 •

edited

Loading

ejona86 commented Dec 3, 2020 •

edited

Loading

gaurav46 commented Dec 17, 2020 •

edited

Loading

hu-chia commented Feb 3, 2021 •

edited

Loading

Uditmittal commented Feb 24, 2021 •

edited

Loading

ejona86 commented May 4, 2021 •

edited

Loading

amraupward commented Apr 3, 2024 •

edited

Loading

yash-brahmkshatriya commented Jun 19, 2024 •

edited

Loading

gharia commented Jul 16, 2024 •

edited

Loading

gharia commented Jul 16, 2024 •

edited

Loading