More fixes

Author: larryliu0820

.ci/scripts/setup-macos.sh

@@ -99,7 +99,7 @@ print_cmake_info() {
   # Explicitly add conda env lib folder to cmake rpath to address the flaky issue
   # where cmake dependencies couldn't be found. This seems to point to how conda
   # links $CMAKE_EXEC to its package cache when cloning a new environment
-  install_name_tool -add_rpath @executable_path/../lib "${CMAKE_EXEC}" || true
+  # install_name_tool -add_rpath @executable_path/../lib "${CMAKE_EXEC}" || true
   # Adding the rpath will invalidate cmake signature, so signing it again here
   # to trust the executable. EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
   # with an exit code 137 otherwise

examples/models/moshi/mimi/install_requirements.sh

@@ -9,7 +9,7 @@ set -x
 
 conda install -c conda-forge "ffmpeg<8" -y
 pip install torchcodec==0.7.0.dev20251012 --extra-index-url https://download.pytorch.org/whl/nightly/cpu
-pip install moshi==0.2.11 --no-deps
+pip install moshi==0.2.11
 pip install bitsandbytes soundfile einops
 # Run llama2/install requirements for torchao deps
 SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )