hello,
after an svn update, make clean, aclocal, autogen.sh and ./configue, (all of them working ok), make fail with error : make[3]: entrant dans le répertoire « /home/nusmuk/pd/Gem/src/plugins/filmAVI » /bin/bash ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -DPD -g -O2 -MT filmAVI_la-filmAVI.lo -MD -MP -MF .deps/filmAVI_la-filmAVI.Tpo -c -o filmAVI_la-filmAVI.lo `test -f 'filmAVI.cpp' || echo './'`filmAVI.cpp libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2, but the libtool: definition of this LT_INIT comes from libtool 2.2.6. libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b Debian-2.2.6b-2 libtool: and run autoconf again. make[3]: *** [filmAVI_la-filmAVI.lo] Erreur 63 cd . && /bin/bash ./config.status config.h config.status: creating config.h config.status: config.h is unchanged make[3]: La cible « all-am » n'a pas pu être refabriquée à cause d'erreurs. make[3]: quittant le répertoire « /home/nusmuk/pd/Gem/src/plugins/filmAVI » make[2]: *** [all] Erreur 2 make[2]: quittant le répertoire « /home/nusmuk/pd/Gem/src/plugins/filmAVI » make[1]: *** [filmAVI] Erreur 2 make[1]: quittant le répertoire « /home/nusmuk/pd/Gem/src/plugins » make: *** [PLUGINS] Erreur 2
what should i do?
thx Cyrille
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
hello, libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2, but the libtool: definition of this LT_INIT comes from libtool 2.2.6.
very interesting. i had the same problem on the OSX-10.4 autobuild machine. which system do you have?
on the autobuild machine the following helped: % LIBTOOL=glibtool make
i asked on the #autoconf channel, but nobody could give me an answer why the wrong libtool was used (but then: all the people that reacted had an aversion against OSX)
if the problem you are having is indeed on ubuntu, then i have no idea.
madr IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
hello, libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2, but the libtool: definition of this LT_INIT comes from libtool 2.2.6.
very interesting. i had the same problem on the OSX-10.4 autobuild machine. which system do you have?
latest stable ubuntu (9.10) will certainly upgrade to 10.04 in few weeks...
on the autobuild machine the following helped: % LIBTOOL=glibtool make
it does not change anything.
i realize that Gem is build, it's the plugins that does not compile...
i asked on the #autoconf channel, but nobody could give me an answer why the wrong libtool was used (but then: all the people that reacted had an aversion against OSX)
if the problem you are having is indeed on ubuntu, then i have no idea.
ok, thanks.
c
madr IOhannes
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvRikEACgkQkX2Xpv6ydvST4gCg82FEqueo1LKibnZQKFWbOAeh cSIAoOkoihw2mpunTZzgeA2aYDivJyo9 =NaKV -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
very interesting. i had the same problem on the OSX-10.4 autobuild machine. which system do you have?
latest stable ubuntu (9.10) will certainly upgrade to 10.04 in few weeks...
hmm, very interesting (and sad for me, as it tells me the problem is somewhere else)
on the autobuild machine the following helped: % LIBTOOL=glibtool make
it does not change anything.
what does % libtool --version % libtoolize --version and % ./plugins/filmAVI/libtool --version
tell you?
i realize that Gem is build, it's the plugins that does not compile...
true. but you won't be able to use [pix_film], [pix_record] nor [pix_video] without these plugins. (the entire idea of the plugin system is to get runtime dependencies out of the Gem.pd_linux)
so we really should get the build system going...
if the problem you are having is indeed on ubuntu, then i have no idea.
ok, thanks.
thanks for the bug report anyhow.
i now see that the problem indeed happened yesterday on the karmic autobuild machine as well...
gmsdr IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
very interesting. i had the same problem on the OSX-10.4 autobuild machine. which system do you have?
latest stable ubuntu (9.10) will certainly upgrade to 10.04 in few weeks...
hmm, very interesting (and sad for me, as it tells me the problem is somewhere else)
on the autobuild machine the following helped: % LIBTOOL=glibtool make
it does not change anything.
what does % libtool --version
ltmain.sh (GNU libtool) 2.2.6
% libtoolize --version
libtoolize (GNU libtool) 2.2.6
and % ./plugins/filmAVI/libtool --version
ltmain.sh (GNU libtool) 2.2.6b
tell you?
i realize that Gem is build, it's the plugins that does not compile...
true. but you won't be able to use [pix_film], [pix_record] nor [pix_video] without these plugins.
ok
(the entire idea of the plugin system is to get runtime dependencies out of the Gem.pd_linux)
nice
so we really should get the build system going...
yep
if the problem you are having is indeed on ubuntu, then i have no idea.
ok, thanks.
thanks for the bug report anyhow.
i now see that the problem indeed happened yesterday on the karmic autobuild machine as well...
ok
tell me if i can be more helpfull. c
gmsdr IOhannes
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvRjd4ACgkQkX2Xpv6ydvSk2QCgnjMGEhFxaJNuObPXy/DpgpsM mlIAoJReMksvu+trUiNvbMwA3AjkiiMX =Z+QL -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
on the autobuild machine the following helped: % LIBTOOL=glibtool make
it does not change anything.
actually, this really should have changed the error...
i now see that the problem indeed happened yesterday on the karmic autobuild machine as well...
ok
tell me if i can be more helpfull.
i think i fixed it. could you try again?
fgmadsr IOhannes
not yet!
libtool: link: g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.4.1/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.4.1/crtbeginS.o .libs/filmAVIPLAY_la-filmAVIPLAY.o /usr/lib/libaviplay.so -ldts -lz -L/usr/lib/gcc/i486-linux-gnu/4.4.1 -L/usr/lib/gcc/i486-linux-gnu/4.4.1/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.4.1/../../.. -L/usr/lib/i486-linux-gnu -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.4.1/crtendS.o /usr/lib/gcc/i486-linux-gnu/4.4.1/../../../../lib/crtn.o -Wl,-soname -Wl,filmAVIPLAY.so.0 -o .libs/filmAVIPLAY.so.0.0.0 libtool: link: (cd ".libs" && rm -f "filmAVIPLAY.so.0" && ln -s "filmAVIPLAY.so.0.0.0" "filmAVIPLAY.so.0") libtool: link: (cd ".libs" && rm -f "filmAVIPLAY.so" && ln -s "filmAVIPLAY.so.0.0.0" "filmAVIPLAY.so") libtool: link: ar cru .libs/filmAVIPLAY.a filmAVIPLAY_la-filmAVIPLAY.o libtool: link: ranlib .libs/filmAVIPLAY.a /bin/sed: can't read /usr/lib/liba52.la: No such file or directory libtool: link: `/usr/lib/liba52.la' is not a valid libtool archive make[3]: *** [filmAVIPLAY.la] Erreur 1 cd . && /bin/bash ./config.status config.h config.status: creating config.h config.status: config.h is unchanged make[3]: La cible « all-am » n'a pas pu être refabriquée à cause d'erreurs. make[3]: quittant le répertoire « /home/nusmuk/pd/Gem/src/plugins/filmAVIPLAY » make[2]: *** [all] Erreur 2 make[2]: quittant le répertoire « /home/nusmuk/pd/Gem/src/plugins/filmAVIPLAY » make[1]: *** [filmAVIPLAY] Erreur 2 make[1]: quittant le répertoire « /home/nusmuk/pd/Gem/src/plugins » make: *** [PLUGINS] Erreur 2 nusmuk@nusmuk:~/pd/Gem/src$
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
on the autobuild machine the following helped: % LIBTOOL=glibtool make
it does not change anything.
actually, this really should have changed the error...
i now see that the problem indeed happened yesterday on the karmic autobuild machine as well...
ok tell me if i can be more helpfull.
i think i fixed it. could you try again?
fgmadsr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvRqhAACgkQkX2Xpv6ydvRlkgCgrOjRNwdI5wwzCubigDrktG6k 2EYAn0TUwEJhVC8s3m2LOR9CkpUgkN9P =quQb -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
not yet!
i've seen that too. i think, just running "make" again, fixes the problem. (it's not good enough for autobuild though...)
fasdrm IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
not yet!
i've seen that too. i think, just running "make" again, fixes the problem. (it's not good enough for autobuild though...)
doing make again finish the compilation. but then, creating this object gives error : error: [pix_film]: no movie decoding backends found! error: [pix_record]: no recording backends found! error: [pix_video]: no video backends found!
c
fasdrm IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvRu/sACgkQkX2Xpv6ydvSy/gCdHjMVp+sSN6v4EOgXB6f8ZtdQ rHMAnj9sFfQPVdEqigbSs5CIQgftJUYe =xESd -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
doing make again finish the compilation.
good (though weird)
but then, creating this object gives error : error: [pix_film]: no movie decoding backends found! error: [pix_record]: no recording backends found! error: [pix_video]: no video backends found!
did you do a "make install"?
if not, you should make sure that the plugins (e.g. plugins/filmQT4L/.libs/filmQT4L.so) live besides your Gem.pd_linux
for testing i do: Gem/src$ make Gem/src$ ln -s plugins/*/.libs/*.so . Gem/src$ pd -lib Gem
it's still a bit in a flux, so that's why there are still some manual parts you have to do... anyhow, the plugins are _not_ searched in the Pd path; instead ALL plugins found besides Gem.pd_linux are loaded.
masdr IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
doing make again finish the compilation.
good (though weird)
but then, creating this object gives error : error: [pix_film]: no movie decoding backends found! error: [pix_record]: no recording backends found! error: [pix_video]: no video backends found!
did you do a "make install"?
no
if not, you should make sure that the plugins (e.g. plugins/filmQT4L/.libs/filmQT4L.so) live besides your Gem.pd_linux
ok
for testing i do: Gem/src$ make Gem/src$ ln -s plugins/*/.libs/*.so . Gem/src$ pd -lib Gem
done
no, pd just crash with a segfault when trying to create a pix_video object
nusmuk@nusmuk:~/pd/Gem/src$ pd -lib Gem factory @ 0x86efe98 ctor[]=0 factory @ 0x8715440 ctor[]=0 factory @ 0x8721e70 ctor[]=0 open: ./gem.conf: No such file or directory load plugins 'video' in '' pattern : /home/nusmuk/pd/Gem/src/video*.so dylib loading file '/home/nusmuk/pd/Gem/src/videoDV4L.so'! factory @ 0x86efe98 Erreur de segmentation nusmuk@nusmuk:~/pd/Gem/src$ pd_gui: pd process exited
it's still a bit in a flux, so that's why there are still some manual parts you have to do... anyhow, the plugins are _not_ searched in the Pd path; instead ALL plugins found besides Gem.pd_linux are loaded.
ok thx C
masdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvRwOgACgkQkX2Xpv6ydvTl2QCg27P1521P/ZI8adAxNuCjy27E QRsAoOqo1MroTQY1v98wtzwWQ54AsPNt =/53S -----END PGP SIGNATURE-----
On 2010-04-23 17:25, IOhannes m zmölnig wrote:
cyrille henry wrote:
not yet!
i've seen that too. i think, just running "make" again, fixes the problem. (it's not good enough for autobuild though...)
hmm, i'm not sure, but i think the problem lies in the /usr/lib/libaviplay.la file provided by libavifile-0.7-dev it explicitely refers to /usr/lib/liba52.la, which is not present on your system.
on debian, this has been "fixed" with "libavifile-0.7-dev 1:0.7.48~20090503.ds-1", where all the .la files from libavifile have been dumped (deleted), so they don't interfere anymore with libtool.
on ubuntu, this fix only made it into >=lucid. (the karmic version is 1:0.7.47.20070718-1.2ubuntu1(!))
for now, the only "clean" possibility i see to circumvent this problem, is to install liba52-0.7.4-dev, which will provide /usr/lib/liba52.la
fmgasdr IOhannes
_______________________________________________ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On 2010-04-26 11:27, IOhannes m zmoelnig wrote:
on ubuntu, this fix only made it into >=lucid. (the karmic version is 1:0.7.47.20070718-1.2ubuntu1(!))
for now, the only "clean" possibility i see to circumvent this problem, is to install liba52-0.7.4-dev, which will provide /usr/lib/liba52.la
this of course if also relevant for the autobuild machines:
hans: in order to get the auto-builds going for the ubuntu-machines, could you install "liba52-0.7.4-dev" on <=karmic and <=etch machines.
there are some more problems with the autobuilds caused by Gem, namely on w32, where it fails with: <snip> autoreconf-2.61: running: automake --add-missing --copy --force-missing am-wrapper: c:MinGWbinautomake-1.10 is missing or not executable. Please try installing the correct version of automake. autoreconf-2.61: automake failed with exit status: 1 </snip>
any ideas?
finally, the debian machines stopped building pd-devel since 23/04/10. any ideas why? (no logs at all...)
bmsd IOhannes
hello thanks for the sugestion, but it still don't work.
IOhannes m zmoelnig a écrit :
for now, the only "clean" possibility i see to circumvent this problem, is to install liba52-0.7.4-dev, which will provide /usr/lib/liba52.la
i install liba52-0.7.4-dev then make clean, aclocal, autogen, configure, make, make
creating a pix_film object create this segfault :
load plugins 'film' in '' pattern : /home/nusmuk/pd/Gem/src/film*.so dylib loading file '/home/nusmuk/pd/Gem/src/filmAVI.so'! dylib loading file '/home/nusmuk/pd/Gem/src/filmAVIPLAY.so'! <init> : Avifile RELEASE-0.7.47-080115-14:47-4.2.3 <init> : Available CPU flags: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx smx <init> : 800.00 MHz Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz processor detected factory @ 0x8acfe70 socket receive error: Connection reset by peer (104) Erreur de segmentation
creating a pix_record create this segfault :
load plugins 'record' in '' pattern : /home/nusmuk/pd/Gem/src/record*.so dylib loading file '/home/nusmuk/pd/Gem/src/recordQT.so'! dylib loading file '/home/nusmuk/pd/Gem/src/recordQT4L.so'! factory @ 0xa136440 pd_gui: pd process exited Erreur de segmentation
Cyrille
fmgasdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On 2010-04-26 21:11, cyrille henry wrote:
hello thanks for the sugestion, but it still don't work.
[...]
Erreur de segmentation
sorry for being unclear (and too promising) the suggestion about liba52 was really only about the compilation issue.
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...
fgamsdr IOhannes
IOhannes m zmoelnig a écrit :
On 2010-04-26 21:11, cyrille henry wrote:
hello thanks for the sugestion, but it still don't work.
[...]
Erreur de segmentation
sorry for being unclear (and too promising) the suggestion about liba52 was really only about the compilation issue.
ok. but it did not help for the compilation (i still have to "make" 2 times).
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...
thanks
c
fgamsdr IOhannes
On 2010-04-27 09:47, cyrille henry wrote:
IOhannes m zmoelnig a écrit :
On 2010-04-26 21:11, cyrille henry wrote:
hello thanks for the sugestion, but it still don't work.
[...]
Erreur de segmentation
sorry for being unclear (and too promising) the suggestion about liba52 was really only about the compilation issue.
ok. but it did not help for the compilation (i still have to "make" 2 times).
ok, i now checked on my fresh pure:dyne installation, and indeed it bails out at a missing /usr/lib/libSDL.la
according to http://packages.ubuntu.com/, this is contained withing libsdl1.2-dev. after installing this compilation went fine.
anyhow, these are really issues of the ubuntu package "libavifile-0.7-dev". you should report this as a bug at ubuntu.
fgm,ar IOhannes
IOhannes m zmoelnig a écrit :
ok, i now checked on my fresh pure:dyne installation, and indeed it bails out at a missing /usr/lib/libSDL.la
according to http://packages.ubuntu.com/, this is contained withing libsdl1.2-dev. after installing this compilation went fine.
anyhow, these are really issues of the ubuntu package "libavifile-0.7-dev". you should report this as a bug at ubuntu.
ok, installing libsdl1.2-dev fix the compilation issues.
what exactly do you exactly consider as a bug (libsdl should be a dependency of libavifile?)
thx c
fgm,ar IOhannes
On 2010-04-27 10:57, cyrille henry wrote:
what exactly do you exactly consider as a bug (libsdl should be a dependency of libavifile?)
EITHER libavifile-0.7-dev should depend on libdts-dev, libsdl1.2-dev & liba52-*-dev OR libavifile should provide files that do not claim to need one of the above libraries ("avifile-config --libs" tells the linker to link against libdts; /usr/lib/libaviplay.la lists liba52.la and libSDL.la as linking dependencies)
in reality, you would not need libSDL-dev and liba52-dev and libdts-dev to link a binary against libaviplay. it's only the helpers (pkgconfig, libtool) that are convinced that these libs are needed, and will refuse to link. however, it's the idea of these helpers to allow correct linking. so either the helpers have to be fixed or their dependencies fullfilled.
fmgasdr IOhannes
ok. is this specific to *ubuntu, and not to debian? c
IOhannes m zmoelnig a écrit :
On 2010-04-27 10:57, cyrille henry wrote:
what exactly do you exactly consider as a bug (libsdl should be a dependency of libavifile?)
EITHER libavifile-0.7-dev should depend on libdts-dev, libsdl1.2-dev & liba52-*-dev OR libavifile should provide files that do not claim to need one of the above libraries ("avifile-config --libs" tells the linker to link against libdts; /usr/lib/libaviplay.la lists liba52.la and libSDL.la as linking dependencies)
in reality, you would not need libSDL-dev and liba52-dev and libdts-dev to link a binary against libaviplay. it's only the helpers (pkgconfig, libtool) that are convinced that these libs are needed, and will refuse to link. however, it's the idea of these helpers to allow correct linking. so either the helpers have to be fixed or their dependencies fullfilled.
fmgasdr IOhannes
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. the code for the pluginfactory became ugly again, but this probably doesn't concern you.
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
fgmasdr IOhannes
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@nusmuk:~/pd/Gem/src$ ./autogen.sh kernel Linux ./autogen.sh: 29: function: not found extra plugins ./autogen.sh: 38: Syntax error: "}" unexpected nusmuk@nusmuk:~/pd/Gem/src$
changing autogen 1st line from #!/bin/sh to : #!/bin/bash solve the problem.
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'? and a new line is missing...
thanks a lot Cyrille
fgmasdr IOhannes
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@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@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
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@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@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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
hello,
i install a ubuntu 10.04 on a 2nd HD to test. gem compile fine : i did not noticed dependency problem.
yes, because of the new plugin system, dependencies are handled a bit more gracefully (that is: you won't notice until runtime...whether this is good or not, is to be found out)
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
yes, each plugins runs it's own configure, soit takes way longer. running "./configure --cache-file=config.cache" should speed things up.
plugins was ok to compile, and wich was not.
yes, hopefully i will add some feedback at the end of configure again, so you can see what has been found..
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.
ok. in my first simple tests it worked (symbolic links were resolved with "install"), but there might (well, obivously: are) still some issues.
i was not able to find a place where all Gem dependency where listed. it would be nice to have such list somwhere.
eventually i will compile this list.... it didn't change a bit since 0.92 though.
suggested: libgl-dev libglu-dev libxxf86vm-dev ftgl-dev libmagick++-dev libv4l-dev libgmerlin-avdec-dev libquicktime-dev
optional (could be used (e.g. instead of the above), but i are often not installed on my machines) libavifile-0.7-dev libmpeg3-dev libdv-dev (however, grabbing doesn't work with the new juju firewire stack)
mfgasdr IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
hello,
i install a ubuntu 10.04 on a 2nd HD to test. gem compile fine : i did not noticed dependency problem.
yes, because of the new plugin system, dependencies are handled a bit more gracefully (that is: you won't notice until runtime...whether this is good or not, is to be found out)
i was taking about the libdts-dev and libsdl1.2-dev problem i had last week...
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
yes, each plugins runs it's own configure, soit takes way longer. running "./configure --cache-file=config.cache" should speed things up.
why is this not default?
plugins was ok to compile, and wich was not.
yes, hopefully i will add some feedback at the end of configure again, so you can see what has been found..
thanks
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.
ok. in my first simple tests it worked (symbolic links were resolved with "install"), but there might (well, obivously: are) still some issues.
i did not really investigate, but yes, it look like a small issues.
i was not able to find a place where all Gem dependency where listed. it would be nice to have such list somwhere.
eventually i will compile this list.... it didn't change a bit since 0.92 though.
suggested: libgl-dev libglu-dev libxxf86vm-dev ftgl-dev libmagick++-dev libv4l-dev libgmerlin-avdec-dev libquicktime-dev
optional (could be used (e.g. instead of the above), but i are often not installed on my machines) libavifile-0.7-dev libmpeg3-dev libdv-dev (however, grabbing doesn't work with the new juju firewire stack)
thanks Cyrille
mfgasdr IOhannes
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvcJE0ACgkQkX2Xpv6ydvToGgCeJgsdFK/klh74OKvQixescGn7 HmQAn3FX5MLTG/gefLxIecWNZDCgM93l =D+FQ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
yes, because of the new plugin system, dependencies are handled a bit more gracefully (that is: you won't notice until runtime...whether this is good or not, is to be found out)
i was taking about the libdts-dev and libsdl1.2-dev problem i had last week...
because i firmly believe that these are packaging issues of ubuntu.
mfgqd IOhannes
IOhannes m zmölnig a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cyrille henry wrote:
yes, because of the new plugin system, dependencies are handled a bit more gracefully (that is: you won't notice until runtime...whether this is good or not, is to be found out)
i was taking about the libdts-dev and libsdl1.2-dev problem i had last week...
because i firmly believe that these are packaging issues of ubuntu.
i understand that. i did not noticed any packaging issues of ubuntu when compiling gem, so i think it's a good news, even if you are not concerned about it.
c
mfgqd IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvcUrsACgkQkX2Xpv6ydvTYIwCeO+TVy/pdAMZGH4YinwJjM2jY gegAoIML9baHgVWAU2mVH+sDO4sSntIx =L14/ -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
I installed liba52-0.7.4-dev on all Debian/Ubuntu machines/chroots. Some had it already.
.hc
On Apr 26, 2010, at 3:11 PM, cyrille henry wrote:
hello thanks for the sugestion, but it still don't work.
IOhannes m zmoelnig a écrit :
for now, the only "clean" possibility i see to circumvent this problem, is to install liba52-0.7.4-dev, which will provide /usr/lib/liba52.la
i install liba52-0.7.4-dev then make clean, aclocal, autogen, configure, make, make
creating a pix_film object create this segfault :
load plugins 'film' in '' pattern : /home/nusmuk/pd/Gem/src/film*.so dylib loading file '/home/nusmuk/pd/Gem/src/filmAVI.so'! dylib loading file '/home/nusmuk/pd/Gem/src/filmAVIPLAY.so'! <init> : Avifile RELEASE-0.7.47-080115-14:47-4.2.3 <init> : Available CPU flags: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx smx <init> : 800.00 MHz Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz processor detected factory @ 0x8acfe70 socket receive error: Connection reset by peer (104) Erreur de segmentation
creating a pix_record create this segfault : load plugins 'record' in '' pattern : /home/nusmuk/pd/Gem/src/record*.so dylib loading file '/home/nusmuk/pd/Gem/src/recordQT.so'! dylib loading file '/home/nusmuk/pd/Gem/src/recordQT4L.so'! factory @ 0xa136440 pd_gui: pd process exited Erreur de segmentation
Cyrille
fmgasdr IOhannes _______________________________________________ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
----------------------------------------------------------------------------
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink- collar temp pool day. - “Hijab Scene #2", by Mohja Kahf