[GEM-dev] solve Re: pb compiling svn

[cyrille henry]

hello,

i install a ubuntu 10.04 on a 2nd HD to test.
gem compile fine : i did not noticed dependency problem.
i however have noticed that ./configure is lot's longer than what it use to be, and output is not very clear : i was not able to know wich plugins was ok to compile, and wich was not.

there is also 1 problem with sudo make install : it did not install plugins.
(just create a *.so broken link)
manually linking to /usr/local/lib/pd.... did not work for me, i had to link the plugins in the Gem/src folder start pd with this location for Gem.

i was not able to find a place where all Gem dependency where listed. it would be nice to have such list somwhere. 

thanks
Cyrille


IOhannes m zmoelnig a écrit :
> On 2010-04-27 21:26, cyrille henry wrote:
>>
>> IOhannes m zmoelnig a écrit :
>>> On 2010-04-27 09:38, IOhannes m zmoelnig wrote:
>>>> i'm currently trying to find out what is causing the crash (which i can
>>>> reproduce on puredyne and other ubuntu systems)
>>>> i'll report back when i found a solution on that...
>>>>
>>>>
>>> i think i found a workaround for the problem.
>> good.
>>
>>> the code for the pluginfactory became ugly again, but this probably
>>> doesn't concern you.
>> i'm concerned about autogen :
>>
>> nusmuk at nusmuk:~/pd/Gem/src$ ./autogen.sh kernel Linux
> 
> 
> i guess the "kernel Linux" part is what autogen.sh prints out, rather
> than what you provided as an argument.
> 
>> ./autogen.sh: 29: function: not found
> 
> sigh; i'm still unable to write sh-functions that can run on ubuntu.
> what was the default shell again? dash? zsh?
> 
> anyhow, should be fixed now.
> 
> 
>> extra
>> plugins
>> ./autogen.sh: 38: Syntax error: "}" unexpected
>> nusmuk at nusmuk:~/pd/Gem/src$
>> changing autogen 1st line from #!/bin/sh
>> to :
>> #!/bin/bash
>> solve the problem.
> 
> my default shell is obviously still bash...
> another way to do it would be to directly run:
> $ autoreconf -fiv
> (the autogen.sh script does just that)
> 
>>> more important, the name of the plugins now has a "gem_" prefixed, so
>>> you can delete the film*.so (and record*.so and video*,so) and link (or
>>> copy) again all the plugins/*/.libs/*.so to live beside Gem.pd_linux
>> ok
>>
>> compilation work fine.
>> pd start and pix_video, pix_film, pix_record instantiate fine.
>>
>> so, i think everything is fine.
>>
>> btw, pd log show : [pix_video]: 0: 'v4l2' video4linux2 v4l2 [pix_video]:
>> 1: 'dv4l' ieee1394 dv4l dv pix_film:: quicktime support
>> pix_film:: libaviplay support
>> pix_film:: libmpeg3 support
>>
>> why does iee1394 is not 2: 'dv'?
> 
> because "v4l" (aka v4l1) is missing.
> the bug was a typo, which i have now fixed.
> 
>> and a new line is missing...
> 
> true.
> but this is rather minor :-)
> 
> fgmasdr
> IOhannes
>