[CM] snd pd external reports "Unbound variable: in" during startup

[Carlos Pita]

Kjetil (sorry for the misspelling last time),

I got an error when building your tar:

snd_pd_external.c: In function 'snd0_gensym':
snd_pd_external.c:143: error: 'par' undeclared (first use in this function)

So in line 131 I changed this:

  {
    struct sched_param par;
    par.sched_priority = sched_get_priority_max(SCHED_FIFO);

for this other:

    struct sched_param par;
  {
    par.sched_priority = sched_get_priority_max(SCHED_FIFO);

At least the build went all the way to its end, although I'm not sure
what I did will be harmless. But while loading the pd external I'm
still getting unbound variables:

/site/install/pd-extra.extended/snd-pd/rt-engine.scm:1362:50: In
expression (jack_ringbuffer_create rt-to-ringbuffer-size):
/site/install/pd-extra.extended/snd-pd/rt-engine.scm:1362:50: Unbound
variable: jack_ringbuffer_create

Jack is running, all its development files are installed... but is it
really needed for the pd external? I mean, io will be done through pd,
won't it?

TIA
Best regards
-Carlos


On Mon, Jul 21, 2008 at 11:28 AM, Kjetil S. Matheussen
<k.s.matheussen at notam02.no> wrote:
> On Mon, 21 Jul 2008, Bill Schottstaedt wrote:
>
>> >  (I guess "in" comes with gtk or motif only.)
>>
>> I'll add it to the no-op list in the no-gui case, or should
>> it do something?  It actually could work, now that I think
>> about it -- isn't there some "SIGALARM" even when there's
>> no gui?
>>
>
> How about just using guile's thread support?
>
> (define (in time thunk)
>  (call-with-new-thread
>   (lambda ()
>     (usleep (* 1000 time))
>     (thunk))))
>
> It's a little bit resource hungry in case call-with-new-thread
> create a new pthread (?), but should work as a backup solution.
>
>