Subject: Re: [ecasound] Visecas 0.3.1
From: bart_AT_solozone.com
Date: Tue Jan 20 2004 - 23:16:14 EET
here is another error I get on open -> file
bart_AT_linux:~/download/visecas-0.3.1/bin> ./visecas
scanning presets...
scanning internal operators...
scanning ladspa plugins...
opening 'command-line-setup'...
action_show_user_guide
action_show_user_guide
../lib/visecas/ecasound.rb:138:in `command': lost synchronisation to ecasound su bprocess (Ecasound::EcasoundError)
last command was: 'cs-load /home/bart/test.wav' from ../lib/visecas/ecasound.rb: 118:in `synchronize'
from ../lib/visecas/ecasound.rb:118:in `command'
from ../lib/visecas/application.rb:287:in `eci_command'
from ../lib/visecas/application.rb:142:in `command'
from ../lib/visecas/application.rb:185:in `open_chainsetups'
from ../lib/visecas/application.rb:183:in `each'
from ../lib/visecas/application.rb:183:in `open_chainsetups'
from ../lib/visecas/main-window.rb:544:in `action_open'
from ../lib/visecas/main-window.rb:543:in `call'
from ./visecas:39:in `main'
from ./visecas:39
bart_AT_linux:~/download/visecas-0.3.1/bin>
bart_AT_solozone.com
>
> From: Jan Weil <jawebada_AT_mailbox.tu-berlin.de>
> Date: 2004/01/18 Sun PM 03:24:16 PST
> To: ecasound mailing list <ecasound-list_AT_wakkanet.fi>
> Subject: Re: Re: [ecasound] Visecas 0.3.1 CRASH
>
> Hi bart once more,
>
> On Sun, 2004-01-18 at 22:57, bart_AT_solozone.com wrote:
> > Be ADVISED there is NO such target as 'make uninstall'
> > in EITHER ruby-gtk or ruby-gnome-all
> > This is the report from ruby extconf.rb
>
> Yes, once again you are absolutely right.
> I didn't notice this yet because I usually install software from source
> code using checkinstall (http://asic-linux.com.mx/~izto/checkinstall/).
> Thereby I can be sure that I can safely uninstall it no matter which
> build system was used.
> I only saw configure and associated autotools which was wrong.
>
> [snip error messages]
>
> Unfortunately these error messages do not contain the commandline which
> calls the compiler.
> To me it looks like a missing -I (preprocessor include path) which would
> point to a bug in ruby-gnome2's configure scripts (maybe this is due to
> the uncommon /opt path? but pkg-config should catch that... hmmm?).
> If you want me to debug this please send me all the output which is
> generated after you type 'make'.
>
> > these are my SuSe 9.0 current with January 15, 2004
> > upgrades.
> >
> > I seem to have these for glade
> > libglade2-2.0.1-398
> ^^^^^^^^^^^^^^^^^^^^^
> > libglade-0.17-44
> > libglade-devel-0.17-44
> > glade-0.6.4-623
> > libglade2-devel-2.0.1-398
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> These should suffice.
>
> >
> > I hesitate to say this; but
> > I have found delelopers using gnone apps to be
> > stuck with numerous fine upgrade distinctions
> > Also red hat and suse do not use the same
> > file standard (this may change we hear)
>
> Bart, I'm sorry you have all these inconviniences.
> But after all I do not really feel responsible for these issues. ;)
> Please note however that Visecas does not depend on GNOME as a whole but
> only on libgtk2 and libglade2 (+ Ruby bindings which admittedly seem to
> be the problem here).
> I deliberately avoided any further dependencies.
> I must admit that ruby-gnome2 is not as popular as say
> pygtk/gnome-python which is a pitty.
> Maybe Visecas' development will result in ruby-gnome2's packages being
> added to all of the major distributions. :-)
>
> Jan
>
>
> --
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <ecasound-list-request_AT_wakkanet.fi>.
>
This archive was generated by hypermail 2b28 : Tue Jan 20 2004 - 23:14:32 EET