Re: [PD] build Pd from source on Raspberry Pi
Actually I never use the "autoget" system - I just cd to src and hit 'make -f makefile.gnu'. But I think yes you ned tk8.5 devel, plus the alsa libraries (alsa-devel?) cheers M On Thu, May 23, 2013 at 09:34:45AM +0100, Julian Brooks wrote: > Hello Miller, > > Thanks for wading in with this. > > Failed here in 'make' (and hope I've included all the necessary info) > > mv -f .deps/stdout.Tpo .deps/stdout.Plo > /bin/bash ../../libtool --tag=CC --mode=link gcc -O6 -funroll-loops > -fomit-frame-pointer -module -avoid-version -shared -shrext .pd_linux > -L../../src -o stdout.la -rpath /usr/local/lib/pd/extra/stdout stdout.lo > -lpthread -ldl > libtool: link: gcc -shared -fPIC -DPIC .libs/stdout.o -L../../src > -lpthread -ldl -O6 -Wl,-soname -Wl,stdout.pd_linux -o > .libs/stdout.pd_linux > libtool: link: ( cd ".libs" && rm -f "stdout.la" && ln -s "../stdout.la" " > stdout.la" ) > make[3]: Leaving directory `/root/pure-data/extra/stdout' > make[3]: Entering directory `/root/pure-data/extra' > make[3]: Nothing to be done for `all-am'. > make[3]: Leaving directory `/root/pure-data/extra' > make[2]: Leaving directory `/root/pure-data/extra' > make[2]: Entering directory `/root/pure-data' > make[2]: *** No rule to make target `doc/5.reference/sublist-help.pd', > needed by `all-am'. Stop. > make[2]: Leaving directory `/root/pure-data' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/pure-data' > make: *** [all] Error 2 > > Couple of (possibly dumb) questions > > Do I need to install tk8.5 (-dev or not)? > > When running './autgen.sh' > > Are these lines relevant: > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and > libtoolize: rerunning libtoolize, to keep the correct libtool macros > in-tree. > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > > Don't have enough experience with building from source to know whether it's > being automagically sorted or they could do with a helping hand, or it's > just not important at all? > > It seems to me that the build process and instructions (INSTALL.txt) have > become simpler/clearer? If so, thank you. > > On the various RPi images I've been putting together, I have always had a > go at building (more for my own satisfaction) and given up in a huff when I > kept falling over at early stages. Then installing from raspbian repo's, > sticking on the pre-built most recent from your site and linking to ./pd > via bash. Works fine but isn't quite satisfactory somehow. > > Anyway. > > Hope we can get it going (I'm going to sit tight this time). > > Regards, > > Julian > > > > On 23 May 2013 04:09, Miller Puckette wrote: > > > Looks like x_array.c and x_scalar.c were missing from the file list in > > Makefile.am (I just added these files) - try to update the source and > > recompile now... > > > > cheers > > Miller > > > > On Thu, May 23, 2013 at 03:03:47AM +0100, Julian Brooks wrote: > > > Hi, > > > > > > Been wanting to do this for a while but it always keeps failing so could > > do > > > with some tips. > > > > > > I have the source from git > > > > > > git clone git:// > > pure-data.git.sourceforge.net/gitroot/pure-data/pure-data > > > > > > Then (as it's a minimal RPi image) have installed > > > automake (and dependencies: autoconf, autotools-dev, m4, libtool, > > gettext) > > > > > > Also added libasound2-dev and tk8.5-dev (not sure if tk required?) > > > > > > When running > > > > > > ./autogen.sh > > > then > > > ./configure > > > and finally > > > make (I ran make previously so much shorter bit before it fails. > > > > > > I get this: > > > > > > autoreconf: Entering directory `.' > > > autoreconf: configure.ac: not using Gettext > > > autoreconf: running: aclocal --force -I m4/generated -I m4 > > > ^[[B^[[Bautoreconf: configure.ac: tracing > > > autoreconf: configure.ac: adding subdirectory portaudio to autoreconf > > > autoreconf: Entering directory `portaudio' > > > autoreconf: configure.in: not using Gettext > > > autoreconf: running: aclocal --force > > > autoreconf: configure.in: tracing > > > autoreconf: configure.in: subdirectory bindings/cpp not present > > > autoreconf: running: libtoolize --copy --force > > > libtoolize: putting auxiliary files in `.'. > > > libtoolize: copying file `./ltmain.sh' > > > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.inand > > > libtoolize: rerunning libtoolize, to keep the correct libtool macros > > > in-tree. > > > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > > > autoreconf: running: /usr/bin/autoconf --force > > > autoreconf: configure.in: not using Autoheader > > > autoreconf: configure.in: not using Automake > > > autoreconf: Leaving directory `portaudio' > > > libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `m4/config'. > > > libtoolize: copying file `m4/config/ltmain.sh' > > > libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4/generated'. > > > libtooliz
Re: [PD] build Pd from source on Raspberry Pi
Hello Miller, Thanks for wading in with this. Failed here in 'make' (and hope I've included all the necessary info) mv -f .deps/stdout.Tpo .deps/stdout.Plo /bin/bash ../../libtool --tag=CC --mode=link gcc -O6 -funroll-loops -fomit-frame-pointer -module -avoid-version -shared -shrext .pd_linux -L../../src -o stdout.la -rpath /usr/local/lib/pd/extra/stdout stdout.lo -lpthread -ldl libtool: link: gcc -shared -fPIC -DPIC .libs/stdout.o -L../../src -lpthread -ldl -O6 -Wl,-soname -Wl,stdout.pd_linux -o .libs/stdout.pd_linux libtool: link: ( cd ".libs" && rm -f "stdout.la" && ln -s "../stdout.la" " stdout.la" ) make[3]: Leaving directory `/root/pure-data/extra/stdout' make[3]: Entering directory `/root/pure-data/extra' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/root/pure-data/extra' make[2]: Leaving directory `/root/pure-data/extra' make[2]: Entering directory `/root/pure-data' make[2]: *** No rule to make target `doc/5.reference/sublist-help.pd', needed by `all-am'. Stop. make[2]: Leaving directory `/root/pure-data' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/pure-data' make: *** [all] Error 2 Couple of (possibly dumb) questions Do I need to install tk8.5 (-dev or not)? When running './autgen.sh' Are these lines relevant: libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. Don't have enough experience with building from source to know whether it's being automagically sorted or they could do with a helping hand, or it's just not important at all? It seems to me that the build process and instructions (INSTALL.txt) have become simpler/clearer? If so, thank you. On the various RPi images I've been putting together, I have always had a go at building (more for my own satisfaction) and given up in a huff when I kept falling over at early stages. Then installing from raspbian repo's, sticking on the pre-built most recent from your site and linking to ./pd via bash. Works fine but isn't quite satisfactory somehow. Anyway. Hope we can get it going (I'm going to sit tight this time). Regards, Julian On 23 May 2013 04:09, Miller Puckette wrote: > Looks like x_array.c and x_scalar.c were missing from the file list in > Makefile.am (I just added these files) - try to update the source and > recompile now... > > cheers > Miller > > On Thu, May 23, 2013 at 03:03:47AM +0100, Julian Brooks wrote: > > Hi, > > > > Been wanting to do this for a while but it always keeps failing so could > do > > with some tips. > > > > I have the source from git > > > > git clone git:// > pure-data.git.sourceforge.net/gitroot/pure-data/pure-data > > > > Then (as it's a minimal RPi image) have installed > > automake (and dependencies: autoconf, autotools-dev, m4, libtool, > gettext) > > > > Also added libasound2-dev and tk8.5-dev (not sure if tk required?) > > > > When running > > > > ./autogen.sh > > then > > ./configure > > and finally > > make (I ran make previously so much shorter bit before it fails. > > > > I get this: > > > > autoreconf: Entering directory `.' > > autoreconf: configure.ac: not using Gettext > > autoreconf: running: aclocal --force -I m4/generated -I m4 > > ^[[B^[[Bautoreconf: configure.ac: tracing > > autoreconf: configure.ac: adding subdirectory portaudio to autoreconf > > autoreconf: Entering directory `portaudio' > > autoreconf: configure.in: not using Gettext > > autoreconf: running: aclocal --force > > autoreconf: configure.in: tracing > > autoreconf: configure.in: subdirectory bindings/cpp not present > > autoreconf: running: libtoolize --copy --force > > libtoolize: putting auxiliary files in `.'. > > libtoolize: copying file `./ltmain.sh' > > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.inand > > libtoolize: rerunning libtoolize, to keep the correct libtool macros > > in-tree. > > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > > autoreconf: running: /usr/bin/autoconf --force > > autoreconf: configure.in: not using Autoheader > > autoreconf: configure.in: not using Automake > > autoreconf: Leaving directory `portaudio' > > libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `m4/config'. > > libtoolize: copying file `m4/config/ltmain.sh' > > libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4/generated'. > > libtoolize: copying file `m4/generated/libtool.m4' > > libtoolize: copying file `m4/generated/ltoptions.m4' > > libtoolize: copying file `m4/generated/ltsugar.m4' > > libtoolize: copying file `m4/generated/ltversion.m4' > > libtoolize: copying file `m4/generated/lt~obsolete.m4' > > autoreconf: configure.ac: not using Autoheader > > autoreconf: running: automake --add-missing --copy --force-missing > > autoreconf: Leaving directory `.' > > root@BitChime:~/pure-data# ./configure > > checking for a BSD
Re: [PD] build Pd from source on Raspberry Pi
Looks like x_array.c and x_scalar.c were missing from the file list in Makefile.am (I just added these files) - try to update the source and recompile now... cheers Miller On Thu, May 23, 2013 at 03:03:47AM +0100, Julian Brooks wrote: > Hi, > > Been wanting to do this for a while but it always keeps failing so could do > with some tips. > > I have the source from git > > git clone git://pure-data.git.sourceforge.net/gitroot/pure-data/pure-data > > Then (as it's a minimal RPi image) have installed > automake (and dependencies: autoconf, autotools-dev, m4, libtool, gettext) > > Also added libasound2-dev and tk8.5-dev (not sure if tk required?) > > When running > > ./autogen.sh > then > ./configure > and finally > make (I ran make previously so much shorter bit before it fails. > > I get this: > > autoreconf: Entering directory `.' > autoreconf: configure.ac: not using Gettext > autoreconf: running: aclocal --force -I m4/generated -I m4 > ^[[B^[[Bautoreconf: configure.ac: tracing > autoreconf: configure.ac: adding subdirectory portaudio to autoreconf > autoreconf: Entering directory `portaudio' > autoreconf: configure.in: not using Gettext > autoreconf: running: aclocal --force > autoreconf: configure.in: tracing > autoreconf: configure.in: subdirectory bindings/cpp not present > autoreconf: running: libtoolize --copy --force > libtoolize: putting auxiliary files in `.'. > libtoolize: copying file `./ltmain.sh' > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and > libtoolize: rerunning libtoolize, to keep the correct libtool macros > in-tree. > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > autoreconf: running: /usr/bin/autoconf --force > autoreconf: configure.in: not using Autoheader > autoreconf: configure.in: not using Automake > autoreconf: Leaving directory `portaudio' > libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `m4/config'. > libtoolize: copying file `m4/config/ltmain.sh' > libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4/generated'. > libtoolize: copying file `m4/generated/libtool.m4' > libtoolize: copying file `m4/generated/ltoptions.m4' > libtoolize: copying file `m4/generated/ltsugar.m4' > libtoolize: copying file `m4/generated/ltversion.m4' > libtoolize: copying file `m4/generated/lt~obsolete.m4' > autoreconf: configure.ac: not using Autoheader > autoreconf: running: automake --add-missing --copy --force-missing > autoreconf: Leaving directory `.' > root@BitChime:~/pure-data# ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking build system type... armv6l-unknown-linux-gnueabihf > checking host system type... armv6l-unknown-linux-gnueabihf > configure: iPhone SDK only available for arm-apple-darwin hosts, skipping > tests > configure: Android SDK only available for arm-linux hosts, skipping tests > checking for style of include used by make... GNU > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking dependency style of gcc... gcc3 > checking how to print strings... printf > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for fgrep... /bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking how to convert armv6l-unknown-linux-gnueabihf file names to > armv6l-unknown-linux-gnueabihf format... func_convert_file_noop > checking how to convert armv6l-unknown-linux-gnueabihf file names to > toolchain format... func_convert_file_noop > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for dlltool... dlltool > checking how to associate runtime and link libraries... printf %s\n > checking for ar... ar > checking for archiver @FILE support... @ > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from g
