Closed hmaarrfk closed 1 year ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
@conda-forge-admin please rerender
Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found some lint.
Here's what I've got...
For recipe:
meta.yaml
, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint .
from the recipe directory. Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
I need a local x86 mac to troubleshoot this better.
Essentially, we need to tell protoc to use the BUILD_PREFIX
protoc during cross compilation, not the HOST one.
maybe i can troubleshoot using arm + linux
That should be a common problem with a common solution though? We set protobuf to the build prefix for osx-arm all over the place. There's also a dedicated cmake variable for that.
Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found some lint.
Here's what I've got...
For recipe:
meta.yaml
, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint .
from the recipe directory. Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found some lint.
Here's what I've got...
For recipe:
requirements: build: cmake != 3.23.0
should not contain a space between relational operator and the version, i.e. cmake !=3.23.0
requirements: run_constrained: pytorch-cpu = 2.0.0
should not contain a space between relational operator and the version, i.e. pytorch-cpu =2.0.0
requirements: run_constrained: pytorch-gpu = 99999999
should not contain a space between relational operator and the version, i.e. pytorch-gpu =99999999
requirements: run_constrained: pytorch-gpu = 2.0.0
should not contain a space between relational operator and the version, i.e. pytorch-gpu =2.0.0
requirements: run_constrained: pytorch-cpu = 99999999
should not contain a space between relational operator and the version, i.e. pytorch-cpu =99999999
Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found some lint.
Here's what I've got...
For recipe:
requirements: build: cmake != 3.23.0
should not contain a space between relational operator and the version, i.e. cmake !=3.23.0
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
Ok, so "debugging" this build on my little machine is really tiring, but I'm finding some locations in cmake that we can likely modify:
${PREFIX}/lib/cmake/protobuf/protobuf-targets-release.cmake
# Import target "protobuf::protoc" for configuration "Release"
set_property(TARGET protobuf::protoc APPEND PROPERTY IMPORTED_CONFIGURATIONS RELEASE)
set_target_properties(protobuf::protoc PROPERTIES
IMPORTED_LOCATION_RELEASE "${_IMPORT_PREFIX}/bin/protoc-23.3.0"
)
list(APPEND _cmake_import_check_targets protobuf::protoc )
list(APPEND _cmake_import_check_files_for_protobuf::protoc "${_IMPORT_PREFIX}/bin/protoc-23.3.0" )
we cna likely change the locations of the specific protoc commands.
seems like we got through it. fingers crossed we get to the end.
Trying to debug a failure that historically occurs at:
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)