OSCx was not compiling on raspberry pi2 - #15
Conversation
[root@pi2 ~]# /usr/share/automake-1.15/config.guess armv7l-unknown-linux-gnueabihf
As configure.ac has been modified, I presume that autoconf has to be launched to regenerate ./configure
It was not compiling.
|
Hi, Just saw this. Is there a reason why you are copying rpi install file inside a desktop install mode (inside tar_em_up.sh)? I think that one should go under rpi install, or? Also, do your changes compile ok on rpi1? |
|
-r and -R flags are for Raspberry Pi, not specifically raspbian distro. I guess that is a misnomer inside the tar_em_up.sh and can you check if using -R flag with RPi2 successfully compiles? |
|
Coincidentally, I fixed the OSCx build in Purr Data yesterday to get it to compile on an arm Chromebook: Btw-- PiDiP has a non-standard, non-free license that prohibits use in commercial installations: |
3 participants
OSCx was not compiling on raspberry pi2 and was generating an error. Others externals were not being compiled.