Re: [PD] compiling Pd 0.45 on Linux
On Sat, Feb 08, 2014 at 02:06:18AM +0900, Max wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I need jack support in Pd, so I am trying to recompile 0.45-4 - - libtool, libjack0 and libjack-dev are installed. I get this: ./autogen.sh [thousands of lines deleted :)] make[2]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4' make[2]: Für das Ziel »all-am« ist nichts zu tun. make[2]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4' make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4' - there is no binary in the bin directory after all this. any ideas? The 'automake' system, although apparently vital for preparing Pd for distributions such as Debian, seems to be far too fragile for non-experts to use effectively. You can just make pd by cding to pd/src and typing: make -f makefile.gnu clean # (not needed if a clean source tree) make -f makefile.gnu JACK=true The makefile.gnu solution is the one I always use. It's completely independent of the automake setup. cheers Miller ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] compiling Pd 0.45 on Linux
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 2014? 02? 08? 02:50, schrieb Miller Puckette: On Sat, Feb 08, 2014 at 02:06:18AM +0900, Max wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I need jack support in Pd, so I am trying to recompile 0.45-4 - - libtool, libjack0 and libjack-dev are installed. I get this: ./autogen.sh [thousands of lines deleted :)] :/ The 'automake' system, although apparently vital for preparing Pd for distributions such as Debian, seems to be far too fragile for non-experts to use effectively. You can just make pd by cding to pd/src and typing: make -f makefile.gnu clean # (not needed if a clean source tree) make -f makefile.gnu JACK=true The makefile.gnu solution is the one I always use. It's completely independent of the automake setup. ok, thanks miller, it compiles, but i have no jack support whatsoever. make -f makefile.gnu JACK=true test -d ../bin || mkdir -p ../bin cd ../obj; cc -Wl,-export-dynamic -o ../bin/pd g_canvas.o g_graph.o g_text.o g_rtext.o g_array.o g_template.o g_io.o g_scalar.o g_traversal.o g_guiconnect.o g_readwrite.o g_editor.o g_all_guis.o g_bang.o g_hdial.o g_hslider.o g_mycanvas.o g_numbox.o g_toggle.o g_vdial.o g_vslider.o g_vumeter.o m_pd.o m_class.o m_obj.o m_atom.o m_memory.o m_binbuf.o m_conf.o m_glob.o m_sched.o s_main.o s_inter.o s_file.o s_print.o s_loader.o s_path.o s_entry.o s_audio.o s_midi.o s_utf8.o s_audio_paring.o d_ugen.o d_ctl.o d_arithmetic.o d_osc.o d_filter.o d_dac.o d_misc.o d_math.o d_fft.o d_fft_mayer.o d_fftroutine.o d_array.o d_global.o d_delay.o d_resample.o d_soundfile.o x_arithmetic.o x_connective.o x_interface.o x_midi.o x_misc.o x_time.o x_acoustics.o x_net.o x_text.o x_gui.o x_list.o x_array.o x_scalar.o s_midi_oss.o s_audio_alsa.o s_audio_alsamm.o s_midi_alsa.o s_audio_jack.o s_audio_oss.o -ldl -lm -lpthread - -lasound -ljack test -d ../bin || mkdir -p ../bin cc -DPD -DHAVE_LIBDL -DHAVE_UNISTD_H -DHAVE_ALLOCA_H - -DPDGUIDIR=\tcl/\ -D_LARGEFILE64_SOURCE - -DINSTALL_PREFIX=\/usr/local\ -Wall -W -Wstrict-prototypes - -Wno-unused -Wno-unused-parameter -Wno-parentheses -Wno-switch - -DUSEAPI_ALSA -DUSEAPI_JACK -DUSEAPI_OSS -O3 -ffast-math - -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -o ../bin/pd-watchdog s_watchdog.c test -d ../bin || mkdir -p ../bin cc -DPD -DHAVE_LIBDL -DHAVE_UNISTD_H -DHAVE_ALLOCA_H - -DPDGUIDIR=\tcl/\ -D_LARGEFILE64_SOURCE - -DINSTALL_PREFIX=\/usr/local\ -Wall -W -Wstrict-prototypes - -Wno-unused -Wno-unused-parameter -Wno-parentheses -Wno-switch - -DUSEAPI_ALSA -DUSEAPI_JACK -DUSEAPI_OSS -O3 -ffast-math - -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -o ../bin/pdsend u_pdsend.c test -d ../bin || mkdir -p ../bin cc -DPD -DHAVE_LIBDL -DHAVE_UNISTD_H -DHAVE_ALLOCA_H - -DPDGUIDIR=\tcl/\ -D_LARGEFILE64_SOURCE - -DINSTALL_PREFIX=\/usr/local\ -Wall -W -Wstrict-prototypes - -Wno-unused -Wno-unused-parameter -Wno-parentheses -Wno-switch - -DUSEAPI_ALSA -DUSEAPI_JACK -DUSEAPI_OSS -O3 -ffast-math - -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -o ../bin/pdreceive u_pdreceive.c u_pdreceive.c: In function ?tcpmakeoutput?: u_pdreceive.c:224:22: warning: ignoring return value of ?write?, declared with attribute warn_unused_result [-Wunused-result] write(1, outbuf, outlen); ^ make -C ../extra/bonk~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/bonk~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/bonk~' make -C ../extra/choice make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/choice' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/choice' make -C ../extra/expr~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/expr~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/expr~' make -C ../extra/fiddle~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/fiddle~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/fiddle~' make -C ../extra/loop~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/loop~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/loop~' make -C ../extra/lrshift~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/lrshift~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/lrshift~' make -C ../extra/pique make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/pique' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/pique' make -C ../extra/sigmund~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/sigmund~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis
Re: [PD] compiling Pd 0.45 on Linux
1. You can reset LANG environment variable for international log, like this: env LANG= make -f makefile.gnu JACK=true 2. Show stdout of this: ldd ../bin/pd 3. Any error-messages about jack in stderr of Pd? 4. Have you tried to run the JACK before Pd? On 7 February 2014 22:46, Max abonneme...@revolwear.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 2014? 02? 08? 02:50, schrieb Miller Puckette: On Sat, Feb 08, 2014 at 02:06:18AM +0900, Max wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I need jack support in Pd, so I am trying to recompile 0.45-4 - - libtool, libjack0 and libjack-dev are installed. I get this: ./autogen.sh [thousands of lines deleted :)] :/ The 'automake' system, although apparently vital for preparing Pd for distributions such as Debian, seems to be far too fragile for non-experts to use effectively. You can just make pd by cding to pd/src and typing: make -f makefile.gnu clean # (not needed if a clean source tree) make -f makefile.gnu JACK=true The makefile.gnu solution is the one I always use. It's completely independent of the automake setup. ok, thanks miller, it compiles, but i have no jack support whatsoever. make -f makefile.gnu JACK=true test -d ../bin || mkdir -p ../bin cd ../obj; cc -Wl,-export-dynamic -o ../bin/pd g_canvas.o g_graph.o g_text.o g_rtext.o g_array.o g_template.o g_io.o g_scalar.o g_traversal.o g_guiconnect.o g_readwrite.o g_editor.o g_all_guis.o g_bang.o g_hdial.o g_hslider.o g_mycanvas.o g_numbox.o g_toggle.o g_vdial.o g_vslider.o g_vumeter.o m_pd.o m_class.o m_obj.o m_atom.o m_memory.o m_binbuf.o m_conf.o m_glob.o m_sched.o s_main.o s_inter.o s_file.o s_print.o s_loader.o s_path.o s_entry.o s_audio.o s_midi.o s_utf8.o s_audio_paring.o d_ugen.o d_ctl.o d_arithmetic.o d_osc.o d_filter.o d_dac.o d_misc.o d_math.o d_fft.o d_fft_mayer.o d_fftroutine.o d_array.o d_global.o d_delay.o d_resample.o d_soundfile.o x_arithmetic.o x_connective.o x_interface.o x_midi.o x_misc.o x_time.o x_acoustics.o x_net.o x_text.o x_gui.o x_list.o x_array.o x_scalar.o s_midi_oss.o s_audio_alsa.o s_audio_alsamm.o s_midi_alsa.o s_audio_jack.o s_audio_oss.o -ldl -lm -lpthread - -lasound -ljack test -d ../bin || mkdir -p ../bin cc -DPD -DHAVE_LIBDL -DHAVE_UNISTD_H -DHAVE_ALLOCA_H - -DPDGUIDIR=\tcl/\ -D_LARGEFILE64_SOURCE - -DINSTALL_PREFIX=\/usr/local\ -Wall -W -Wstrict-prototypes - -Wno-unused -Wno-unused-parameter -Wno-parentheses -Wno-switch - -DUSEAPI_ALSA -DUSEAPI_JACK -DUSEAPI_OSS -O3 -ffast-math - -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -o ../bin/pd-watchdog s_watchdog.c test -d ../bin || mkdir -p ../bin cc -DPD -DHAVE_LIBDL -DHAVE_UNISTD_H -DHAVE_ALLOCA_H - -DPDGUIDIR=\tcl/\ -D_LARGEFILE64_SOURCE - -DINSTALL_PREFIX=\/usr/local\ -Wall -W -Wstrict-prototypes - -Wno-unused -Wno-unused-parameter -Wno-parentheses -Wno-switch - -DUSEAPI_ALSA -DUSEAPI_JACK -DUSEAPI_OSS -O3 -ffast-math - -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -o ../bin/pdsend u_pdsend.c test -d ../bin || mkdir -p ../bin cc -DPD -DHAVE_LIBDL -DHAVE_UNISTD_H -DHAVE_ALLOCA_H - -DPDGUIDIR=\tcl/\ -D_LARGEFILE64_SOURCE - -DINSTALL_PREFIX=\/usr/local\ -Wall -W -Wstrict-prototypes - -Wno-unused -Wno-unused-parameter -Wno-parentheses -Wno-switch - -DUSEAPI_ALSA -DUSEAPI_JACK -DUSEAPI_OSS -O3 -ffast-math - -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -o ../bin/pdreceive u_pdreceive.c u_pdreceive.c: In function ?tcpmakeoutput?: u_pdreceive.c:224:22: warning: ignoring return value of ?write?, declared with attribute warn_unused_result [-Wunused-result] write(1, outbuf, outlen); ^ make -C ../extra/bonk~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/bonk~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/bonk~' make -C ../extra/choice make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/choice' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/choice' make -C ../extra/expr~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/expr~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/expr~' make -C ../extra/fiddle~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/fiddle~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/fiddle~' make -C ../extra/loop~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/loop~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis '/home/max/Code/pd-0.45-4/extra/loop~' make -C ../extra/lrshift~ make[1]: Betrete Verzeichnis '/home/max/Code/pd-0.45-4/extra/lrshift~' make[1]: Für das Ziel »all« ist nichts zu tun. make[1]: Verlasse Verzeichnis
Re: [PD] check mail with pd ?
On 02/06/2014 01:53 AM, Chris McCormick wrote:
On 06/02/14 06:29, pured...@11h11.com wrote:
but pd is not really good with strings afaik
Maybe soon:
https://sourceforge.net/p/pure-data/pure-data/ci/8a02332a5fb68edc2899e2f13513c77f0796d21b/
https://sourceforge.net/p/pure-data/pure-data/ci/49ffcf8ba5cdde7660e82f1e190fcee7c6fa5627/
:)
One of the reasons (I think) the string manipulation libs in Pd extended
haven't caught on is because they seem to force users to care directly
about character codes. If I want to pass the string hello{world}
around in Pd, I should not have to know the codes for curly braces just
to create that string in an object box.
To work, this will require a new set of GUI classes that allow the user
to type strings that get saved underneath as character codes, as well as
display lists of character codes as a string in the patch. I don't know
any externals that do this, but it shouldn't be hard if you're sending
the text to the GUI as floats. Also, you need i/o classes to read from
and write to files without having to pass through lists of symbols and
floats as intermediaries. Otherwise, you will lose data on the read.
Finally, you can't leverage any of the extant symbol manipulation tools,
because then you run into symbol-table growth, dollsym
substitutions/escapes, and all the other problems that I assume are the
reason for introducing lists of character codes. Otherwise you're just
pushing the current problems users have with symbols to the edges of the
new string library.
I understand the desire for this approach, and it's probably less work
than making symbols deallocatable. But if the user has to stare at
character codes just to get around the limitations of symbol atoms,
they'll probably just use symbol atoms and work within Pd's current
limitations for string processing.
-Jonathan
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
Re: [PD] check mail with pd ?
You can manipulate strings in pdlua and only export the symbols you
want; yes you need to learn lua but it's not very hard.
Martin
On 2014-02-08 01:10, Jonathan Wilkes wrote:
On 02/06/2014 01:53 AM, Chris McCormick wrote:
On 06/02/14 06:29, pured...@11h11.com wrote:
but pd is not really good with strings afaik
Maybe soon:
https://sourceforge.net/p/pure-data/pure-data/ci/8a02332a5fb68edc2899e2f13513c77f0796d21b/
https://sourceforge.net/p/pure-data/pure-data/ci/49ffcf8ba5cdde7660e82f1e190fcee7c6fa5627/
:)
One of the reasons (I think) the string manipulation libs in Pd extended
haven't caught on is because they seem to force users to care directly
about character codes. If I want to pass the string hello{world}
around in Pd, I should not have to know the codes for curly braces just
to create that string in an object box.
To work, this will require a new set of GUI classes that allow the user
to type strings that get saved underneath as character codes, as well as
display lists of character codes as a string in the patch. I don't know
any externals that do this, but it shouldn't be hard if you're sending
the text to the GUI as floats. Also, you need i/o classes to read from
and write to files without having to pass through lists of symbols and
floats as intermediaries. Otherwise, you will lose data on the read.
Finally, you can't leverage any of the extant symbol manipulation tools,
because then you run into symbol-table growth, dollsym
substitutions/escapes, and all the other problems that I assume are the
reason for introducing lists of character codes. Otherwise you're just
pushing the current problems users have with symbols to the edges of the
new string library.
I understand the desire for this approach, and it's probably less work
than making symbols deallocatable. But if the user has to stare at
character codes just to get around the limitations of symbol atoms,
they'll probably just use symbol atoms and work within Pd's current
limitations for string processing.
-Jonathan
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
