# Compiling for Raspberry Pi 4

**URL:** https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652
**Category:** Bug Reports and Issues
**Created:** [September 24, 2022, 9:54pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652 "2022-09-24T21:54:16Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 24, 2022, 9:54pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/1 "2022-09-24T21:54:16Z")

</div>

Hi,  
I tried to compile Flucoma from source onto a Raspberry Pi 4 8gb, and ran into issues during “make install”. Maybe Flucoma does not support Raspberry Pi but they do support ARM, so I wanted to try it out.

[EDIT] I am running Rasbian 11, Bullseye. This is a 32 bit operating system, so maybe that is the issue…

My compile flags were set to the following:

```auto
-DSC_PATH=/home/anony/src/supercollider -march=armv8-a -mfloat-abi=hard -mfpu=neon-fp-armv8 ..

```

These compile flags were pulled from suggested Pi 4 flags listed [here](https://sourceforge.net/projects/raspberry-pi-cross-compilers/files/).

The bash log is printed below. It crashes first during hisstools compile.

```auto
anony@raspberrypi:~/src/flucoma-sc-1.0.4/build $ make install
Scanning dependencies of target flucoma_VERSION_LIB
[1%] Building CXX object _deps/flucoma-core-build/CMakeFiles/flucoma_VERSION_LIB.dir/FluidVersion.cpp.o
[2%] Linking CXX static library libflucoma_VERSION_LIB.a
[2%] Built target flucoma_VERSION_LIB
Scanning dependencies of target FLUID_SC_COPYREPLYADDR
[2%] Building CXX object CMakeFiles/FLUID_SC_COPYREPLYADDR.dir/include/wrapper/CopyReplyAddress.cpp.o
[3%] Building CXX object CMakeFiles/FLUID_SC_COPYREPLYADDR.dir/home/anony/src/supercollider/common/SC_Reply.cpp.o
[4%] Building CXX object CMakeFiles/FLUID_SC_COPYREPLYADDR.dir/home/anony/src/supercollider/external_libraries/boost/libs/system/src/error_code.cpp.o
[5%] Linking CXX static library libFLUID_SC_COPYREPLYADDR.a
[5%] Built target FLUID_SC_COPYREPLYADDR
Scanning dependencies of target HISSTools_FFT
[5%] Building CXX object _deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/__/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp.o
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h: In function ‘void hisstools_fft_impl::shuffle4(const hisstools_fft_impl::Vector4x<T, vec_size>&, const hisstools_fft_impl::Vector4x<T, vec_size>&, const hisstools_fft_impl::Vector4x<T, vec_size>&, const hisstools_fft_impl::Vector4x<T, vec_size>&, hisstools_fft_impl::Vector4x<T, vec_size>*, hisstools_fft_impl::Vector4x<T, vec_size>*, hisstools_fft_impl::Vector4x<T, vec_size>*, hisstools_fft_impl::Vector4x<T, vec_size>*) [with T = float; int vec_size = 4]’:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:611:44: note: called from here
  611 | const float32x4_t v1 = vcombine_f32( vget_low_f32(A.mData[0].mVal), vget_low_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:611:44: note: called from here
  611 | const float32x4_t v1 = vcombine_f32( vget_low_f32(A.mData[0].mVal), vget_low_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:611:44: note: called from here
  611 | const float32x4_t v1 = vcombine_f32( vget_low_f32(A.mData[0].mVal), vget_low_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:612:44: note: called from here
  612 | const float32x4_t v2 = vcombine_f32(vget_high_f32(A.mData[0].mVal), vget_high_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:612:44: note: called from here
  612 | const float32x4_t v2 = vcombine_f32(vget_high_f32(A.mData[0].mVal), vget_high_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:612:44: note: called from here
  612 | const float32x4_t v2 = vcombine_f32(vget_high_f32(A.mData[0].mVal), vget_high_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:613:44: note: called from here
  613 | const float32x4_t v3 = vcombine_f32( vget_low_f32(B.mData[0].mVal), vget_low_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:613:44: note: called from here
  613 | const float32x4_t v3 = vcombine_f32( vget_low_f32(B.mData[0].mVal), vget_low_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:613:44: note: called from here
  613 | const float32x4_t v3 = vcombine_f32( vget_low_f32(B.mData[0].mVal), vget_low_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:614:44: note: called from here
  614 | const float32x4_t v4 = vcombine_f32(vget_high_f32(B.mData[0].mVal), vget_high_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:614:44: note: called from here
  614 | const float32x4_t v4 = vcombine_f32(vget_high_f32(B.mData[0].mVal), vget_high_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:614:44: note: called from here
  614 | const float32x4_t v4 = vcombine_f32(vget_high_f32(B.mData[0].mVal), vget_high_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:10147:1: error: inlining failed in call to ‘always_inline’ ‘float32x4x2_t vuzpq_f32(float32x4_t, float32x4_t)’: target specific option mismatch
10147 | vuzpq_f32 (float32x4_t __a, float32x4_t__ b)
      | ^ ~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:617:50: note: called from here
  617 | const float32x4x2_t v6 = vuzpq_f32(v2, v4);
      | ^
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:10147:1: error: inlining failed in call to ‘always_inline’ ‘float32x4x2_t vuzpq_f32(float32x4_t, float32x4_t)’: target specific option mismatch
10147 | vuzpq_f32 (float32x4_t __a, float32x4_t__ b)
      | ^ ~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:616:50: note: called from here
  616 | const float32x4x2_t v5 = vuzpq_f32(v1, v3);
      | ^
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:611:44: note: called from here
  611 | const float32x4_t v1 = vcombine_f32( vget_low_f32(A.mData[0].mVal), vget_low_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:611:44: note: called from here
  611 | const float32x4_t v1 = vcombine_f32( vget_low_f32(A.mData[0].mVal), vget_low_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:611:44: note: called from here
  611 | const float32x4_t v1 = vcombine_f32( vget_low_f32(A.mData[0].mVal), vget_low_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:612:44: note: called from here
  612 | const float32x4_t v2 = vcombine_f32(vget_high_f32(A.mData[0].mVal), vget_high_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:612:44: note: called from here
  612 | const float32x4_t v2 = vcombine_f32(vget_high_f32(A.mData[0].mVal), vget_high_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:612:44: note: called from here
  612 | const float32x4_t v2 = vcombine_f32(vget_high_f32(A.mData[0].mVal), vget_high_f32(C.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:613:44: note: called from here
  613 | const float32x4_t v3 = vcombine_f32( vget_low_f32(B.mData[0].mVal), vget_low_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7350:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_low_f32(float32x4_t)’: target specific option mismatch
 7350 | vget_low_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:613:44: note: called from here
  613 | const float32x4_t v3 = vcombine_f32( vget_low_f32(B.mData[0].mVal), vget_low_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:613:44: note: called from here
  613 | const float32x4_t v3 = vcombine_f32( vget_low_f32(B.mData[0].mVal), vget_low_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:614:44: note: called from here
  614 | const float32x4_t v4 = vcombine_f32(vget_high_f32(B.mData[0].mVal), vget_high_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7271:1: error: inlining failed in call to ‘always_inline’ ‘float32x2_t vget_high_f32(float32x4_t)’: target specific option mismatch
 7271 | vget_high_f32 (float32x4_t __a)
      | ^ ~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:614:44: note: called from here
  614 | const float32x4_t v4 = vcombine_f32(vget_high_f32(B.mData[0].mVal), vget_high_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:7175:1: error: inlining failed in call to ‘always_inline’ ‘float32x4_t vcombine_f32(float32x2_t, float32x2_t)’: target specific option mismatch
 7175 | vcombine_f32 (float32x2_t __a, float32x2_t__ b)
      | ^ ~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:614:44: note: called from here
  614 | const float32x4_t v4 = vcombine_f32(vget_high_f32(B.mData[0].mVal), vget_high_f32(D.mData[0].mVal));
      | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:10147:1: error: inlining failed in call to ‘always_inline’ ‘float32x4x2_t vuzpq_f32(float32x4_t, float32x4_t)’: target specific option mismatch
10147 | vuzpq_f32 (float32x4_t __a, float32x4_t__ b)
      | ^ ~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:617:50: note: called from here
  617 | const float32x4x2_t v6 = vuzpq_f32(v2, v4);
      | ^
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:9,
                 from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/usr/lib/gcc/arm-linux-gnueabihf/10/include/arm_neon.h:10147:1: error: inlining failed in call to ‘always_inline’ ‘float32x4x2_t vuzpq_f32(float32x4_t, float32x4_t)’: target specific option mismatch
10147 | vuzpq_f32 (float32x4_t __a, float32x4_t__ b)
      | ^ ~~~~~~~~
In file included from /home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc-1.0.4/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:616:50: note: called from here
  616 | const float32x4x2_t v5 = vuzpq_f32(v1, v3);
      | ^
make[2]: *** [_deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/build.make:82: _deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/__/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1963: _deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/all] Error 2

```

I have also tried the default ARM flags presented on Flucoma github, with the same result:

```auto
-march=armv7-a -mtune=cortex-a8 -mfloat-abi=hard -mfpu=neon

```

I thank you in advance for any help and suggestions.

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 26, 2022, 9:43am UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/2 "2022-09-26T09:43:05Z")

</div>

Hi @broccolistem and welcome,

Yes, this will be a ARM + 32bit thing, I think. The problem is with one of our dependencies that uses intrinsics. Alex, the author of that dependency has already updated his code to build for 32-bit on ARM but I haven’t yet updated our stuff to use the updated version. If you’re happy enough making some changes to the CMake, I can take you through what to do to use the new stuff.

---

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 27, 2022, 11:03pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/3 "2022-09-27T23:03:58Z")

</div>

Hiya @weefuzzy,  
Thanks for confirming the issue!  
I appreciate your offer to assist in modifying the Cmake list.  
But I’ve discovered the Raspi folks now have an official non-beta release of a 64 bit OS.  
I will be back in my studio with the Pi within a week or so, and will try first building on this 64 bit OS.  
And I will report back here with results once I’ve had the chance. Hopefully Jack, SC, Reaper & my GPIO DAC/ADC all work with that too. If not… adjusting the Cmake list will be worth doing:))  
Thanks again, more to come.  
Broccoli

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 28, 2022, 8:49pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/4 "2022-09-28T20:49:30Z")

</div>

No worries – good luck with the 64 bit build. I’ve now updated the HISSTools version for our builds, so the latest nightlies should be 32-bit friendly, should it be needed.

---

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 29, 2022, 8:12pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/5 "2022-09-29T20:12:29Z")

</div>

Hiya @weefuzzy  
Thanks for making an update to the dev-branch.  
On my side, with the 64 bit OS, cmake didn’t throw any errors, but I am receiving this error with ‘make install’—something else related to Hisstools, it appears. Any thoughts? Thanks for your help.

```auto
anony@raspberrypi:~/src/flucoma-sc/build $ sudo make install
Scanning dependencies of target flucoma_VERSION_LIB
[1%] Building CXX object _deps/flucoma-core-build/CMakeFiles/flucoma_VERSION_LIB.dir/FluidVersion.cpp.o
[2%] Linking CXX static library libflucoma_VERSION_LIB.a
[2%] Built target flucoma_VERSION_LIB
Scanning dependencies of target FLUID_SC_COPYREPLYADDR
[2%] Building CXX object CMakeFiles/FLUID_SC_COPYREPLYADDR.dir/include/wrapper/CopyReplyAddress.cpp.o
[3%] Building CXX object CMakeFiles/FLUID_SC_COPYREPLYADDR.dir/home/anony/src/supercollider/common/SC_Reply.cpp.o
[4%] Building CXX object CMakeFiles/FLUID_SC_COPYREPLYADDR.dir/home/anony/src/supercollider/external_libraries/boost/libs/system/src/error_code.cpp.o
[5%] Linking CXX static library libFLUID_SC_COPYREPLYADDR.a
[5%] Built target FLUID_SC_COPYREPLYADDR
Scanning dependencies of target HISSTools_FFT
[5%] Building CXX object _deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/__/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp.o
In file included from /home/anony/src/flucoma-sc/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp:3:
/home/anony/src/flucoma-sc/build/_deps/hisstools-src/HISSTools_FFT/HISSTools_FFT_Core.h:16:10: fatal error: emmintrin.h: No such file or directory
   16 | #include <emmintrin.h>
      | ^ ~~~~~~~~~~~~
compilation terminated.
make[2]: *** [_deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/build.make:82: _deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/__/hisstools-src/HISSTools_FFT/HISSTools_FFT.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1963: _deps/flucoma-core-build/CMakeFiles/HISSTools_FFT.dir/all] Error 2
make: *** [Makefile:149: all] Error 2

```

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 29, 2022, 8:34pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/6 "2022-09-29T20:34:19Z")

</div>

That means it’s still reaching for Intel instructions, not ARM. Which makes me realise I omitted an important piece of information (sorry).

If you’re cloning from Github, which is that you need to be on the `dev` branch, rather than `main`. If you didn’t clone, but are just using the source.zip from Github, you’ll need to clone, I think (because the source.zip strips all the git stuff out). So, in your `src` folder, try:

```bash
git clone https://github.com/flucoma/flucoma-sc.git
git checkout dev 
mkdir build && cd build 
export CXXFLAGS="-march=armv8-a -mfloat-abi=hard -mfpu=neon-fp-armv8" 
cmake -DSC_PATH=/home/anony/src/supercollider -DFLUID_BRANCH=dev ..
make install

```

The configure step will take a little while longer, but it should pull in the correct components now…

---

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 29, 2022, 8:55pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/7 "2022-09-29T20:55:13Z")

</div>

Thank you for helping to walk me through this @weefuzzy  
This is my latest error, following your commands,

```auto
-- The CXX compiler identification is GNU 10.2.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ - broken
CMake Error at /usr/share/cmake-3.18/Modules/CMakeTestCXXCompiler.cmake:59 (message):
  The C++ compiler

    "/usr/bin/c++"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/anony/src/flucoma-sc/build/CMakeFiles/CMakeTmp
    
    Run Build Command(s):/usr/bin/gmake cmTC_c25e2/fast && /usr/bin/gmake -f CMakeFiles/cmTC_c25e2.dir/build.make CMakeFiles/cmTC_c25e2.dir/build
    gmake[1]: Entering directory '/home/anony/src/flucoma-sc/build/CMakeFiles/CMakeTmp'
    Building CXX object CMakeFiles/cmTC_c25e2.dir/testCXXCompiler.cxx.o
    /usr/bin/c++ -march=armv8-a -mfloat-abi=hard -mfpu=neon-fp-armv8 -fPIE -std=c++17 -o CMakeFiles/cmTC_c25e2.dir/testCXXCompiler.cxx.o -c /home/anony/src/flucoma-sc/build/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
    c++: error: unrecognized command-line option ‘-mfloat-abi=hard’
    c++: error: unrecognized command-line option ‘-mfpu=neon-fp-armv8’
    gmake[1]: *** [CMakeFiles/cmTC_c25e2.dir/build.make:85: CMakeFiles/cmTC_c25e2.dir/testCXXCompiler.cxx.o] Error 1
    gmake[1]: Leaving directory '/home/anony/src/flucoma-sc/build/CMakeFiles/CMakeTmp'
    gmake: *** [Makefile:140: cmTC_c25e2/fast] Error 2
    
    

  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:41 (project)

-- Configuring incomplete, errors occurred!
See also "/home/anony/src/flucoma-sc/build/CMakeFiles/CMakeOutput.log".
See also "/home/anony/src/flucoma-sc/build/CMakeFiles/CMakeError.log".

```

Any idea where I should look next? Sorry to bug.  
Broccoli

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 29, 2022, 9:30pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/8 "2022-09-29T21:30:04Z")

</div>

Huh. That’s one of those very puzzling errors. I’m assuming this is GCC, right? If you do

```bash
/usr/bin/c++ --version 

```

It gives you something GCCish. So, this line worries me particularly:

```auto
-- Detecting CXX compiler ABI info - failed

```

Because that shouldn’t happen, AFAIK. If you delete the file `CMakeCache` from your build folder and unset the CXXFLAGS before trying CMake again, is it happier?  
(going by a process of elimination here…)

```bash
rm CMakeCache.txt
unset CXXFLAGS
cmake -DSC_PATH=/home/anony/src/supercollider -DFLUID_BRANCH=dev ..

```

Whilst we’re at it, we can see if `armv8-a` is right or not

```bash
uname -m

```

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 29, 2022, 9:53pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/9 "2022-09-29T21:53:47Z")

</div>

Some additional Googling suggests that those fpu / floating point options might indeed not be valid on ARM 64.

Running

```nohighlight
gcc -c -Q -mcpu=native --help=target

```

might shed some light on what options are optimal / permissible. And, if you’re just building for that particular machine, `-mcpu=native` might just be the quickest way of getting the right magic options anyway.

---

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 30, 2022, 3:20pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/10 "2022-09-30T15:20:19Z")

</div>

[EDIT] I left cmake running overnight and just noticed your followup message…off to try that…

Hi @weefuzzy

> If you do  
> /usr/bin/c++ --version

I get …

```auto
$ /usr/bin/c++ --version

c++ (Debian 10.2.1-6) 10.2.1 20210110

```

> Whilst we’re at it, we can see if `armv8-a` is right or not  
> uname -m

I get…

```auto
$ uname -m
aarch64

```

And…

> cmake -DSC\_PATH=/home/anony/src/supercollider -DFLUID\_BRANCH=dev …

This is working!

But “sudo make install” results, eventually, in…

```auto
In file included from /home/anony/src/flucoma-sc/build/_deps/flucoma-docs-build/generated_sources/DumpParams.cpp:69:
/home/anony/src/flucoma-sc/build/_deps/flucoma-core-src/include/clients/nrt/KMeansClient.hpp: In member function ‘fluid::client::MessageResult<fluid::FluidTensor<long int, 1> > fluid::client::kmeans::KMeansClient::predict(fluid::client::InputDataSetClientRef, fluid::client::LabelSetClientRef) const’:
/home/anony/src/flucoma-sc/build/_deps/flucoma-core-src/include/clients/nrt/KMeansClient.hpp:128:22: warning: ‘minK’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  128 | assignments(i) = mAlgorithm.vq(query);
      | ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/anony/src/flucoma-sc/build/_deps/flucoma-docs-build/generated_sources/DumpParams.cpp:70:
/home/anony/src/flucoma-sc/build/_deps/flucoma-core-src/include/clients/nrt/SKMeansClient.hpp: In member function ‘fluid::client::MessageResult<fluid::FluidTensor<long int, 1> > fluid::client::skmeans::SKMeansClient::predict(fluid::client::DataSetClientRef, fluid::client::LabelSetClientRef) const’:
/home/anony/src/flucoma-sc/build/_deps/flucoma-core-src/include/clients/nrt/SKMeansClient.hpp:130:22: warning: ‘minK’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  130 | assignments(i) = mAlgorithm.vq(query);
      | ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
At global scope:
cc1plus: note: unrecognized command-line option ‘-Wno-c++11-narrowing’ may have been intended to silence earlier diagnostics
[39%] Linking CXX executable DumpParams
[39%] Built target DumpParams
Scanning dependencies of target MAKE_SC_REF
[40%] Making SC docs
Traceback (most recent call last):
  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/anony/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/MakeRef.py", line 16, in <module>
    from flucoma.doc import render
  File "/home/anony/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/doc/render.py", line 18, in <module>
    from flucoma.doc.rst.html import no_rst_filter
  File "/home/anony/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/doc/rst/html.py", line 19, in <module>
    from jinja2 import pass_context
ImportError: cannot import name 'pass_context' from 'jinja2' (/usr/lib/python3/dist-packages/jinja2/ __init__.py)
make[2]: *** [CMakeFiles/MAKE_SC_REF.dir/build.make:78: CMakeFiles/MAKE_SC_REF] Error 1
make[1]: *** [CMakeFiles/Makefile2:1054: CMakeFiles/MAKE_SC_REF.dir/all] Error 2
make: *** [Makefile:149: all] Error 2

```

What do you think?  
Sorry for the problems and thanks again for your help 🙂  
Broccoli

---

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 30, 2022, 3:44pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/11 "2022-09-30T15:44:25Z")

</div>

Continuing this thread, after just noticing your followup post…

> gcc -c -Q -mcpu=native --help=target

This returns…

```auto
The following options are target specific:
  -mabi= lp64
  -march= armv8-a
  -mbig-endian [disabled]
  -mbionic [disabled]
  -mbranch-protection=        		
  -mcmodel= small
  -mcpu= cortex-a72
  -mfix-cortex-a53-835769 [enabled]
  -mfix-cortex-a53-843419 [enabled]
  -mgeneral-regs-only [disabled]
  -mglibc [enabled]
  -mharden-sls=               		
  -mlittle-endian [enabled]
  -mlow-precision-div [disabled]
  -mlow-precision-recip-sqrt [disabled]
  -mlow-precision-sqrt [disabled]
  -mmusl [disabled]
  -momit-leaf-frame-pointer [enabled]
  -moutline-atomics [enabled]
  -moverride=<string>         		
  -mpc-relative-literal-loads [enabled]
  -msign-return-address= none
  -mstack-protector-guard-offset= 	
  -mstack-protector-guard-reg= 		
  -mstack-protector-guard= global
  -mstrict-align [disabled]
  -msve-vector-bits=<number> scalable
  -mtls-dialect= desc
  -mtls-size= 24
  -mtrack-speculation [disabled]
  -mtune= cortex-a72
  -muclibc [disabled]
  -mverbose-cost-dump [disabled]

  Known AArch64 ABIs (for use with the -mabi= option):
    ilp32 lp64

  Supported AArch64 return address signing scope (for use with -msign-return-address= option):
    all non-leaf none

  The code model option names for -mcmodel:
    large small tiny

  Valid arguments to -mstack-protector-guard=:
    global sysreg

  The possible SVE vector lengths:
    1024 128 2048 256 512 scalable

  The possible TLS dialects:
    desc trad

```

and again with your suggested updated cmake command…

> cmake -DSC\_PATH=/home/anony/src/supercollider -DFLUID\_BRANCH=dev -mcpu=native …

That works. Then: “sudo make install”, results eventually again in…

```auto
                                                    ^ ~~~~~~~~~~
[38%] Linking CXX shared module ../release-packaging/Plugins/FluidBufOnsetFeature.so
[38%] Built target FluidBufOnsetFeature
[39%] Built target DumpParams
Scanning dependencies of target MAKE_SC_REF
[40%] Making SC docs
Traceback (most recent call last):
  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/anony/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/MakeRef.py", line 16, in <module>
    from flucoma.doc import render
  File "/home/anony/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/doc/render.py", line 18, in <module>
    from flucoma.doc.rst.html import no_rst_filter
  File "/home/anony/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/doc/rst/html.py", line 19, in <module>
    from jinja2 import pass_context
ImportError: cannot import name 'pass_context' from 'jinja2' (/usr/lib/python3/dist-packages/jinja2/ __init__.py)
make[2]: *** [CMakeFiles/MAKE_SC_REF.dir/build.make:78: CMakeFiles/MAKE_SC_REF] Error 1
make[1]: *** [CMakeFiles/Makefile2:1054: CMakeFiles/MAKE_SC_REF.dir/all] Error 2
make: *** [Makefile:149: all] Error 2

```

Thank you @weefuzzy  
Broccoli

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 30, 2022, 3:59pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/12 "2022-09-30T15:59:44Z")

</div>

Ok, that’s better than it seems: we’ve made it to python problems in the documentation generating code. The C++ appears to be happier (interesting to see that there are no `-mfpu` or similar options on arm8).

So, two choices to get the docs: (1) we can install the packages needed for the doc-gen to work or (2) we can turn that bit off and just pull the docs out of one of the release packages. Sort of depends on your level of python-related patience 😄

---

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 30, 2022, 4:03pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/13 "2022-09-30T16:03:41Z")

</div>

In regards to plan #1, if it’s just a matter to pull some things via apt-get I’m down, but if it is much more complex than that, let’s do option #2 😛

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 30, 2022, 4:12pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/14 "2022-09-30T16:12:17Z")

</div>

## Installing the Python Dependencies

- Inside your `build` folder will be a sub-sub-folder like `_deps/flucoma-docs-src`
- in there should be a `requirements.txt` file
- at its simplest, running

```auto
pip install -r <full path to requirements.txt file> 

```

will download and install all the necessary bits. More fancy options are possible with virtual environments etc., if you need to use python machine for other stuff.

## Or Disable docs, and grab from package

re-run CMake again (sorry), with these arguments

```auto
cmake -UDOCS -DDOCS=OFF ..

```

This will clear the currently cached value of the should-i-build-the-docs flag, and reset it to `OFF`.

Then `make install` will (hopefully) make it all the way through.

Next, just download the [latest pre-built release from Github](https://github.com/flucoma/flucoma-sc/releases/latest), un-tar and copy the `HelpSource` folder over to the partially assembled package (iirc `flucoma-sc/release-packaging/FluidCorpusManipulation/`

---

<div class="post-metadata">

### Author: ![broccolistem](https://discourse.flucoma.org/letter_avatar_proxy/v4/letter/b/a5b964/32.png) [@broccolistem](https://discourse.flucoma.org/u/broccolistem)
#### Post date: [September 30, 2022, 7:13pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/15 "2022-09-30T19:13:27Z")

</div>

Hi @weezfuzzy,  
Well I couldn’t get pip to install everything I needed through the requirements.txt, however, disabling docs worked smoothly!

For reference this was my final cmake command,

```auto
cmake -DSC_PATH=/home/anony/src/supercollider -DFLUID_BRANCH=dev -march=armv8-a -mcpu=cortex-a72 -mabi=lp640 -UDOCS -DDOCS=OFF ..

```

Then I copied in the docs and also the ‘Resources’ folder from the pre-built release.

Thank you again ~VERY MUCH~ for holding me hand through these issues. I have only the moment to minimally test the build, and things seem to be working so far. In October & November & beyond I’ll be attempting to pursue some compositional activities with Flucoma, so I am sure I will have a bunch of (much more interesting) further questions to bring.  
Broccoli

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [September 30, 2022, 7:36pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/16 "2022-09-30T19:36:18Z")

</div>

Excellent – have fun with it, and I look forward to hearing about what you get up to with it!

---

<div class="post-metadata">

### Author: ![balintlaczko](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/balintlaczko/32/1184_2.png) [@balintlaczko](https://discourse.flucoma.org/u/balintlaczko)
#### Post date: [August 6, 2024, 8:36pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/17 "2024-08-06T20:36:54Z")

</div>

Hey there, reviving this old thread since I also need some hand holding :))

I am trying to compile flucoma-pd on a raspberry pi 4b, and I get quite far, it successfully builds almost everything in `make install` until about 95% where it bites into `fluid_libmanipulation`, and gets stuck.

I can’t paste the entire output, since it is such a long wall of warnings that it overruns the console limit, but the very end looks like this:

```auto
/home/dietpi/flucoma-pd-rpi/flucoma-pd/include/FluidPDWrapper.hpp:1289:37: required from ‘static void fluid::client::FluidPDWrapper<Client>::makeClass(const char*) [with Client = fluid::client::NRTThreadingAdaptor<fluid::client::NRTSharedInstanceAdaptor<fluid::client::mlpclassifier::MLPClassifierClient> >]’
/home/dietpi/flucoma-pd-rpi/flucoma-pd/include/FluidPDWrapper.hpp:2047:36: required from ‘void fluid::client::makePDWrapper(const char*) [with Client = NRTThreadingAdaptor<NRTSharedInstanceAdaptor<mlpclassifier::MLPClassifierClient> >]’
/home/dietpi/flucoma-pd-rpi/flucoma-pd/build/generated_sources/fluid_libmanipulation.cpp:51:48: required from here
/home/dietpi/flucoma-pd-rpi/flucoma-pd/include/FluidPDWrapper.hpp:746:38: warning: conversion from ‘long int’ to ‘float’ may change value [-Wconversion]

```

The RPI is warm to the touch, so I guess it is still churning on it? It has been 3-4h though. It ended in a fatal error the first time (that I forgot to document, sorry), and when I restarted it skipped everything and went straight to building `fluid_libmanipulation`, and then got stuck. I’ll leave it overnight and see, but in case anyone has some tips, let me know! 🙂 Thanks.

Update: now I realize it is also completely unresponsive, so maybe I ran out of memory or something? I’ll try to monitor some stats and report back.

Update 2: had 2 other runs, it seems nothing is freezing (at least this time), it’s just slow. Both times ended in the “fatal error”:

```auto
/home/dietpi/flucoma-pd-rpi/flucoma-pd/include/FluidPDWrapper.hpp:2047:36: required from ‘void fluid::client::makePDWrapper(const char*) [with Client = NRTThreadingAdaptor<NRTSharedInstanceAdaptor<mlpclassifier::MLPClassifierClient> >]’
/home/dietpi/flucoma-pd-rpi/flucoma-pd/build/generated_sources/fluid_libmanipulation.cpp:51:48: required from here
/home/dietpi/flucoma-pd-rpi/flucoma-pd/include/FluidPDWrapper.hpp:746:38: warning: conversion from ‘long int’ to ‘float’ may change value [-Wconversion]
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [CMakeFiles/fluid_libmanipulation.dir/build.make:76: CMakeFiles/fluid_libmanipulation.dir/generated_sources/fluid_libmanipulation.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:2223: CMakeFiles/fluid_libmanipulation.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

```

Any idea what this might mean?

This time I was also monitoring the system, so it seems it was really working on it until the error:

 ![image](https://discourse.flucoma.org/uploads/default/original/2X/a/a03d290a3846cad1165e99f1ac60b1633ceace81.png)

Could it be that 4GB RAM is just not enough to compile it?

Update 3: some searching tells me that this is likely a memory issue, so I bumped up the swap and started another run now.

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [August 7, 2024, 9:49am UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/18 "2024-08-07T09:49:43Z")

</div>

You’re compiling directly on the R-PI? _Could_ be a memory issue yes. That warning about conversions definitely shouldn’t wreck the build.

If increasing the swap size doesn’t work, we can resort to turning stuff off in the libmanipulation target until we narrow it down (maybe there’s some awful template recursion that’s eating all the ram).

There’s also some diagnostics we could try adding to the GCC call, like `-ftime-report` that might shed some light [Developer Options (Using the GNU Compiler Collection (GCC))](https://gcc.gnu.org/onlinedocs/gcc/Developer-Options.html#index-ftime-report)

---

<div class="post-metadata">

### Author: ![balintlaczko](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/balintlaczko/32/1184_2.png) [@balintlaczko](https://discourse.flucoma.org/u/balintlaczko)
#### Post date: [August 7, 2024, 1:07pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/19 "2024-08-07T13:07:21Z")

</div>

> [@weefuzzy](#):
>
> If increasing the swap size doesn’t work

It did! …but pd does not want to eat it:

```auto
root@DietPi:/home/dietpi/flucoma-pd-rpi# pd -stderr -nogui -verbose -audiodev 0 -midiindev 2 -midioutdev 2 -path "./flucoma-pd" -lib "/home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation"
Pd-0.55.0 ("") compiled for Debian (0.55.0+ds-1~bpo12+1) on 2024/06/18 at 07:11:57 UTC
float precision = 32 bits
verbose(4): input channels = 2, output channels = 2
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation.linux-arm64-32.so and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation.linux-arm64-0.so and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation.l_arm64 and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation.pd_linux and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation/fluid_libmanipulation.linux-arm64-32.so and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation/fluid_libmanipulation.linux-arm64-0.so and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation/fluid_libmanipulation.l_arm64 and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation/fluid_libmanipulation.pd_linux and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation.pd and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation.pat and failed
verbose(4): tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation/fluid_libmanipulation.pd and failed
/home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation: can't load library

```

…although things definitely seem to be there:

```auto
root@DietPi:/home/dietpi/flucoma-pd-rpi/flucoma-pd# cd pd_objects && ls
fluid.ampfeature~.pd_linux fluid.bufchroma.pd_linux fluid.bufnmf.pd_linux fluid.bufscale.pd_linux fluid.bufthreaddemo.pd_linux fluid.melbands~.pd_linux fluid.onsetslice~.pd_linux fluid.transientslice~.pd_linux
fluid.ampgate~.pd_linux fluid.bufcompose.pd_linux fluid.bufnmfcross.pd_linux fluid.bufselect.pd_linux fluid.bufthresh.pd_linux fluid.mfcc~.pd_linux fluid.pitch~.pd_linux fluid.transients~.pd_linux
fluid.ampslice~.pd_linux fluid.bufflatten.pd_linux fluid.bufnmfseed.pd_linux fluid.bufselectevery.pd_linux fluid.buftransients.pd_linux fluid.nmffilter~.pd_linux fluid.plotter.pd_linux fluid.waveform.pd_linux
fluid.audiotransport~.pd_linux fluid.bufhpss.pd_linux fluid.bufnoveltyfeature.pd_linux fluid.bufsinefeature.pd_linux fluid.buftransientslice.pd_linux fluid.nmfmatch~.pd_linux fluid.sinefeature~.pd_linux fluid_libmanipulation.pd_linux
fluid.bufampfeature.pd_linux fluid.bufinfo.pd_linux fluid.bufnoveltyslice.pd_linux fluid.bufsines.pd_linux fluid.chroma~.pd_linux fluid.nmfmorph~.pd_linux fluid.sines~.pd_linux
fluid.bufampgate.pd_linux fluid.bufloudness.pd_linux fluid.bufonsetfeature.pd_linux fluid.bufspectralshape.pd_linux fluid.gain~.pd_linux fluid.noveltyfeature~.pd_linux fluid.spectralshape~.pd_linux
fluid.bufampslice.pd_linux fluid.bufmelbands.pd_linux fluid.bufonsetslice.pd_linux fluid.bufstats.pd_linux fluid.hpss~.pd_linux fluid.noveltyslice~.pd_linux fluid.stats.pd_linux
fluid.bufaudiotransport.pd_linux fluid.bufmfcc.pd_linux fluid.bufpitch.pd_linux fluid.bufstft.pd_linux fluid.loudness~.pd_linux fluid.onsetfeature~.pd_linux fluid.stftpass~.pd_linux

```

So in the previous output it says it `tried /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation/fluid_libmanipulation.pd_linux and failed`.

> [@broccolistem](#):
>
> `-march=armv8-a -mcpu=cortex-a72 -mabi=lp640`

Should I also try something like this? My build command was just the “in a hurry” style without docs, so I didn’t specify anything.

---

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [August 7, 2024, 1:19pm UTC](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652/20 "2024-08-07T13:19:21Z")

</div>

Are any of the flucoma objects you just built working? If so, does comparing the output of `file` in the shell between a working object and our misbehaving yield anything different?

```bash
file <working thing> 
file /home/dietpi/flucoma-pd-rpi/flucoma-pd/pd-objects/fluid_libmanipulation/fluid_libmanipulation.pd_linux

```

That might also shed some light on whether you needed to pass in those flags

[Next page](https://discourse.flucoma.org/t/compiling-for-raspberry-pi-4/1652.md?page=2)