Can you re-run configure and look through the output for the relevant Jack checks? It may not be finding Jack correctly. Also, what does the final configure print out say for the Audio APIS? Is JACK listed?
On Jul 18, 2017, at 12:00 PM, pd-list-request@lists.iem.at wrote:
From: Max <abonnements@revolwear.com mailto:abonnements@revolwear.com> Subject: Re: [PD] [PD-announce] pd 0.48-0test1 released Date: July 18, 2017 at 10:41:37 AM GMT+2 To: IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at>, pd-list@lists.iem.at mailto:pd-list@lists.iem.at
On 2017년 07월 17일 20:00, IOhannes m zmölnig wrote:
On 07/17/2017 04:24 PM, Max wrote:
Great work, I really appreciate the more verbose INSTALL.txt. The autogen.sh process worked flawless, however, I could not get JACK to work, even with ./configure --enable-jack
i'm not sure jack is supported on w32.
I assume that's IOhannes way of saying that I need to specify the platform I'm on to receive better answers on the list, but feel slightly violated that he suggests that I'm using windows...
Linux Mint Cinnamon 18.2 64bit kernel 4.11.11 lowlatency
Jack2 works fine on this machine and does so on Pd 0.47.1, but not with 0.48-Otest1
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 2017년 07월 18일 15:04, Dan Wilcox wrote:
Can you re-run configure and look through the output for the relevant Jack checks? It may not be finding Jack correctly.
checking for jack_set_xrun_callback in -ljack... yes checking for jack_set_error_function in -ljack... yes
Also, what does the final configure print out say for the Audio APIS? Is JACK listed?
configure:
pd 0.48.0 is now configured
Platform: Linux
Debug build: no
Universal build: no
Localizations: yes
Source directory: .
Installation prefix: /usr/local
Compiler: gcc
CFLAGS: -g -O2 -ffast-math -funroll-loops
-fomit-frame-pointer LDFLAGS: INCLUDES: LIBS: -lpthread -ldl -lrt
External extension: pd_linux
External CFLAGS: -fPIC
External LDFLAGS: -Wl,--export-dynamic -fPIC
fftw: no
wish(tcl/tk): wish
audio APIs: PortAudio JACK alsa OSS
midi APIs: alsa OSS
i did another make and surprise! it doesn't run any more.
./pd Segmentation fault
do i need to do a make clean or something before a new attempt?
On Jul 18, 2017, at 12:00 PM, pd-list-request@lists.iem.at mailto:pd-list-request@lists.iem.at wrote:
*From:*Max <abonnements@revolwear.com mailto:abonnements@revolwear.com> *Subject:**Re: [PD] [PD-announce] pd 0.48-0test1 released* *Date:*July 18, 2017 at 10:41:37 AM GMT+2 *To:*IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at>,pd-list@lists.iem.at mailto:pd-list@lists.iem.at
On 2017년 07월 17일 20:00, IOhannes m zmölnig wrote:
On 07/17/2017 04:24 PM, Max wrote:
Great work, I really appreciate the more verbose INSTALL.txt. The autogen.sh process worked flawless, however, I could not get JACK to work, even with ./configure --enable-jack
i'm not sure jack is supported on w32.
I assume that's IOhannes way of saying that I need to specify the platform I'm on to receive better answers on the list, but feel slightly violated that he suggests that I'm using windows...
Linux Mint Cinnamon 18.2 64bit kernel 4.11.11 lowlatency
Jack2 works fine on this machine and does so on Pd 0.47.1, but not with 0.48-Otest1
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com
On Jul 18, 2017, at 3:56 PM, Max abonnements@revolwear.com wrote:
On 2017년 07월 18일 15:04, Dan Wilcox wrote:
Can you re-run configure and look through the output for the relevant Jack checks? It may not be finding Jack correctly.
checking for jack_set_xrun_callback in -ljack... yes checking for jack_set_error_function in -ljack... yes
That looks good. It's finding the jack library.
Also, what does the final configure print out say for the Audio APIS? Is JACK listed?
configure:
audio APIs: PortAudio JACK alsa OSS
It detected things ok.
i did another make and surprise! it doesn't run any more.
./pd Segmentation fault
do i need to do a make clean or something before a new attempt?
Possibly, depending on if things have changed in the configuration, etc it doesn't hurt to clean & make again.
Also, what's the output of: pkg-config --libs jack
This might be a problem IOhannes will need to help with as I don't have a Linux install right now.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 2017년 07월 18일 16:22, Dan Wilcox wrote:
On Jul 18, 2017, at 3:56 PM, Max <abonnements@revolwear.com On 2017년 07월 18일 15:04, Dan Wilcox wrote: i did another make and surprise! it doesn't run any more.
./pd Segmentation fault
do i need to do a make clean or something before a new attempt?
Possibly, depending on if things have changed in the configuration, etc it doesn't hurt to clean & make again.
I just deleted the whole folder and downloaded it again
./autogen.sh ./configure --enable-jack make cd bin ./pd Segmentation fault
Same thing happens now without --enable-jack too.
Also, what's the output of: pkg-config --libs jack
pkg-config --libs jack -ljack
On Jul 18, 2017, at 5:14 PM, Max abonnements@revolwear.com wrote:
On 2017년 07월 18일 16:22, Dan Wilcox wrote:
On Jul 18, 2017, at 3:56 PM, Max <abonnements@revolwear.com On 2017년 07월 18일 15:04, Dan Wilcox wrote: i did another make and surprise! it doesn't run any more.
./pd Segmentation fault
do i need to do a make clean or something before a new attempt?
Possibly, depending on if things have changed in the configuration, etc it doesn't hurt to clean & make again.
I just deleted the whole folder and downloaded it again
No need to do that. Running "make clean" clears out the build.
./autogen.sh ./configure --enable-jack make cd bin ./pd Segmentation fault
I would do a rebuild with debug enabled and then run it through gdb to see where the crash is happening:
make clean ./configure --enable-debug --enable-jack make cd bin gdb ./pd
Basic instructions are here: http://unknownroad.com/rtfm/gdbtut/gdbsegfault.html http://unknownroad.com/rtfm/gdbtut/gdbsegfault.html
What we need is the stack trace to see which functions are begin called before the crash.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 2017년 07월 18일 17:53, Dan Wilcox wrote:
I would do a rebuild with debug enabled and then run it through gdb to see where the crash is happening:
make clean
make: *** No rule to make target 'clean'. Stop.
./configure --enable-debug --enable-jack make cd bin gdb ./pd
Starting program: /home/max/Code/pd-0.48-0test1a/bin/pd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff7f32700 (LWP 28486)] [New Thread 0x7ffff7eb1700 (LWP 28488)]
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 28488)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 (gdb) watchdog: signaling pd...
Basic instructions are here: http://unknownroad.com/rtfm/gdbtut/gdbsegfault.html
What we need is the stack trace to see which functions are begin called before the crash.
is it the above?
On Jul 18, 2017, at 6:20 PM, Max abonnements@revolwear.com wrote:
On 2017년 07월 18일 17:53, Dan Wilcox wrote:
I would do a rebuild with debug enabled and then run it through gdb to see where the crash is happening: make clean
make: *** No rule to make target 'clean'. Stop.
That means the the makefiles aren't generated. If so, you need to run to generate them:
./autogen.sh
Judging from the stack trace, I'm not sure pd was built with debugging on. You can do a clean and rebuild with debugging by:
make clean ./configure --enable-debug --enable-jack make
If the stack trace output is the same, maybe try the above without --enable-jack as well.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 2017년 07월 18일 18:42, Dan Wilcox wrote:
On Jul 18, 2017, at 6:20 PM, Max <abonnements@revolwear.com mailto:abonnements@revolwear.com> wrote:
make clean
make: *** No rule to make target 'clean'. Stop.
That means the the makefiles aren't generated. If so, you need to run to generate them:
./autogen.sh
ah, I see.
Judging from the stack trace, I'm not sure pd was built with debugging on. You can do a clean and rebuild with debugging by:
make clean ./configure --enable-debug --enable-jack make
cd bin ./pd Segmentation fault
./pd -nrt as IOhannes suggested runs ok.
gdb ./pd run -nrt also runs ok.
If the stack trace output is the same, maybe try the above without --enable-jack as well.
Pd runs like that! make clean ./configure --enable-debug make cd bin ./pd API 5 not supported, reverting to 1 (ALSA)
-
Dan Wilcox -
IOhannes m zmölnig -
Max