I just checked out a fresh copy of CVS -r devel_0_38 on my fresh Fedora Core 3 Linux install, compiled ok, but the locations of the resulting executables seem to be a bit confused (to the extent I can't run pd from the build directory, as I did with devel_0_37 a few months ago).
----snip----
$ cd pd/
$ ./bootstrap.sh
$ ./configure --enable-jack --enable-portaudio --enable-simd --enable-optimize=athlon-xp --enable-threadedsf --enable-gathreadlocks --enable-atomic --enable-newhash --enable-debug --enable-dependency-tracking (success)
$ make depend make: *** No rule to make target `depend'. Stop.
$ make (success)
$ ./src/pd Pd version 0.38.0 devel compiled 14:13:41 Jan 9 2005 port 5400 TCL_LIBRARY="./tcl/library" TK_LIBRARY="./tk/library" "./bin/pd-gui" 5400 sh: ./bin/pd-gui: No such file or directory Waiting for connection request... Pd: signal 2
$ cd src/ $ ./pd Pd version 0.38.0 devel compiled 14:13:41 Jan 9 2005 port 5400 TCL_LIBRARY="../tcl/library" TK_LIBRARY="../tk/library" "../bin/pd-gui" 5400 sh: ../bin/pd-gui: No such file or directory Waiting for connection request... Pd: signal 2
$ cd .. $ find bin/nada src/pd src/pdreceive src/pdsend src/bin/pd-watchdog src/bin/pd-gui src/bin/pd.tk (edited)
----snip----
I guess I will have to do it the "proper" way and specify a prefix directory for ./configure and then make && make install, but it's nice for quick testing to be able to run from the build directory.
Also note the "make depend" step indicated by the output of ./configure (I think) doesn't work.
Happy New Year greetings to everyone in Pd-land.
Problems with "./configure --prefix=~/pd ...etc... && make && make install" to an empty directory "~/pd" resolved by making the following directories manually (install complained about "no such file or directory"):
$ mkdir ~/pd/lib $ mkdir ~/pd/lib/pd $ mkdir ~/pd/lib/pd/bin $ mkdir ~/pd/lib/pd/extra
Only after these did "make install" succeed.
But then:
$ ~/pd/bin/pd Pd version 0.38.0 devel compiled 14:13:41 Jan 9 2005 port 5400 TCL_LIBRARY="~/pd/lib/pd/tcl/library" TK_LIBRARY="~/pd/lib/pd/tk/library" "~/pd/lib/pd/bin/pd-gui" 5400 Waiting for connection request... sh: ~/pd/lib/pd/bin/pd-gui: No such file or directory Pd: signal 2
$ find ~/pd/ ~/pd/ ~/pd/man ~/pd/man/man1 ~/pd/man/man1/pdsend.1 ~/pd/man/man1/pdreceive.1 ~/pd/man/man1/pd.1 ~/pd/include ~/pd/include/m_pd.h ~/pd/lib ~/pd/lib/pd ~/pd/lib/pd/pd-watchdog ~/pd/lib/pd/pd-gui ~/pd/lib/pd/extra ~/pd/lib/pd/extra/lrshift~.pd_linux ~/pd/lib/pd/extra/loop~.pd_linux ~/pd/lib/pd/extra/bonk~.pd_linux ~/pd/lib/pd/extra/expr.pd_linux ~/pd/lib/pd/extra/fiddle~.pd_linux ~/pd/lib/pd/extra/pique.pd_linux ~/pd/lib/pd/extra/expr~.pd_linux ~/pd/lib/pd/extra/fexpr~.pd_linux ~/pd/lib/pd/extra/choice.pd_linux ~/pd/lib/pd/bin ~/pd/lib/pd/bin/pd.tk ~/pd/bin ~/pd/bin/pdsend ~/pd/bin/pdreceive ~/pd/bin/pd
pd-gui and pd-watchdog are installed in the wrong place! So, quick fix for now:
$ cd ~/pd/lib/pd/bin/ $ ln -s ../pd-gui $ ln -s ../pd-watchdog
Try again:
$ ~/pd/bin/pd Pd version 0.38.0 devel compiled 14:13:41 Jan 9 2005 port 5400 TCL_LIBRARY="~/pd/lib/pd/tcl/library" TK_LIBRARY="~/pd/lib/pd/tk/library" "~/pd/lib/pd/bin/pd-gui" 5400 Waiting for connection request... ... connected device 1: tried /dev/midi READ/WRITE; returned 5 OSS: requested audio buffer size 8816 limited to 8192 OSS: issuing first ADC 'read' ... ...done. Configuring for UNIX Pd version 0.38.0 devel {OSS 2} {ALSA 1} {jack 5} courier
Success! I have a Pd running! Not tested it yet, but I'm optimistic :-)
Problems with "./configure --prefix=~/pd ...etc... && make && make install" to an empty directory "~/pd" resolved by making the following
yes ... this is a problem ... pd's file hierarchy vs linux standard ... the path to the pd-gui is hardcoded ...
i'll check the install section of the makefile, though ...
cheers ... tim
On Sun, 9 Jan 2005, ClaudiusMaximus wrote:
Problems with "./configure --prefix=~/pd ...etc... && make && make install" to an empty directory "~/pd" resolved by making the following directories manually (install complained about "no such file or directory"):
This may be related to the fact that the unix shell only expands leading tildes. compare the results of:
echo ~ echo ~/blahblah echo --prefix=~
I figured that you can safely write $HOME instead of ~ and it works perfectly, because then, it gets replaced by a real name _before_ running ./configure, instead of _during_.
Mathieu Bouchard -=- Montréal QC Canada -=- http://artengine.ca/matju