Skip to content

Gradle script does not run on M1 chipsets #199

Open
#200
Open
Gradle script does not run on M1 chipsets#199
#200
Assignees
sumitaich1998

Description

@stym06
stym06
opened on Sep 28, 2022

Description
Mentioned version of protoc does not have aarch64 files, that fails the gradle build

To Reproduce
./gradlew clean dagger-common:generateTestProto

Expected behavior
Proto file generation

Behavior

Execution failed for task ':dagger-common:generateTestProto'.
> Could not resolve all files for configuration ':dagger-common:protobufToolsLocator_protoc'.
   > Could not find protoc-3.1.0-osx-aarch_64.exe (com.google.protobuf:protoc:3.1.0).
     Searched in the following locations:
         https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.1.0/protoc-3.1.0-osx-aarch_64.exe

Additional context

Activity

  1. sumitaich1998 commented on Oct 3, 2022

    @sumitaich1998
    sumitaich1998
    on Oct 3, 2022
    Contributor

    hey @stym06 , i have raised a pr for this #200 , can you pull the branch fix-protoc-arm64 and rerun the build to test if its working?

  2. sumitaich1998
    self-assigned this
    on Oct 3, 2022

  3. stym06 commented on Oct 4, 2022

    @stym06
    stym06
    on Oct 4, 2022
    Author

    Still fails with another dependency issue:

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

  4. stym06 commented on Oct 4, 2022

    @stym06
    stym06
    on Oct 4, 2022
    Author

    Can we have a profile for aarm64 arch builds? I think hotfixes might break in future.

  5. sumitaich1998 commented on Nov 4, 2022

    @sumitaich1998
    sumitaich1998
    on Nov 4, 2022
    Contributor

    @stym06 feel free to raise a pr to fix this issue. Let us know if any help is needed. Since we cannot test this on our system, it might be difficult to fix this ourselves, since we do not know which all dependencies can fail for M1 chipsets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions