Open mfansler opened 2 years ago
Hi there, thank you for your contribution!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.
If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment.
Thanks!
This is still broken and reproducible. OP has reproduce steps. Only conda info
changes are:
conda version : 4.12.0
virtual packages : __osx=12.3=0
Same conda-build
version (3.12.8).
Why did this get "stale" labeled so quickly? There hasn't even been a new conda-build
release since OP.
I saw the same crash of otool on one executable. This is the otool version info.
otool(1): Apple Inc. version cctools-973.0.1
disassmbler: LLVM version 14.0.3
The otool from XCode 13.4 runs just ok.
llvm-otool(1): Apple Inc. version cctools-994.1
otool(1): Apple Inc. version cctools-994.1
disassmbler: LLVM version 13.1.6, (clang-1316.0.21.2.5)
Editing out this line https://github.com/conda/conda-build/blob/f666e4e8af26a71a73ea4c700e1a85e3453724ba/conda_build/os_utils/macho.py#L150 and hard-coding /usr/bin/[tool name]
allows conda to use the system installed xcode versions of otool and install_name_tool.
You can also do something like this in your build.sh
:
if [[ $target_platform == osx-* ]]; then
for toolname in "otool" "install_name_tool"; do
tool=$(find "${BUILD_PREFIX}/bin/" -name "*apple*-$toolname")
mv "${tool}" "${tool}.bak"
ln -s "/Library/Developer/CommandLineTools/usr/bin/${toolname}" "$tool"
done
fi
Actual Behavior
Running
conda build --R 4.1 .
results in unexpected exit during the post-processing stage of packaging when running on nativeosx-arm64
. Below is the traceback, including some of the preceding "INFO" outputs to establish context. Note that termination occurs in theotool -l
call, and right before the stack trace is a message fromlibc++abi
that observed the exceptioncodesign_failed: 0
.Expected Behavior
It should not fail.
Steps to Reproduce
This seems to affect all R packages that involve C/C++ compilation that I have attempted so far. For example, with conda-forge/r-rcpp-feedstock
Additional notes
Changing path into the residual working directory (under
conda-bld/
), activating the_build_env/
environment, and rerunning the failed command (essentially,arm64-apple-darwin20.0.0-otool -l Rcpp.dylib
) also gets killed:However, running the native
otool -l
(from Xcode) has no issue.Output of conda info