[PD] pd-extended build on 9.10 /gem 0.92.1 eeepc = no luck with v4l2

[IOhannes m zmölnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

olsen wrote:
> thanks hans for this indication
> this is the correct flag to compile it with v4l2?!
> --with-libv4l2-includes=/usr/lib/libv4l2.so

hmm, the ..-includes flag is meant for adding _include_ directives to
the compiler rather than libraries for the linker.

try something like
"--with-libv4l" and/or "--with-libv4l2" and you should be done if libv4l
 is properly installed.


> the package builts but still i'm gettin
> error: [pix_video]: could not find a backend for driver 'v4l2'
> 
> i also tried a gem solo & make spits this error:
> recordQT4L.cpp -o ../Objects/recordQT4L.o
> recordQT4L.cpp: In function ‘lqt_file_type_t guess_qtformat(const char*)’:
> recordQT4L.cpp:96: error: invalid conversion from ‘const char*’ to ‘char*’
> make[1]: *** [recordQT4L.o] Error 1
> make[1]: Leaving directory `/home/olsen/pd/pd-extended/Gem/src/Pixes'
> make: *** [Pixes] Er

yah, this is dues to an overly pedantic compiler (or probably: invalid
headers: the line the error is referring to is (here; but i might have a
different version :-)) using the (const char*) argument to
guess_qtformat() as input for strchr(). according to my man-pages,
strchr() indeed takes (const char*) rather than (char*). if this is
indeed the problem, just add a cast to (const char*) to the call of
strchr(), and file a bug-report to ubuntu that they are shipping broken
headers)


> 
> same with gem 0.92-1
> recordQT4L.cpp: In function ‘lqt_file_type_t guess_qtformat(const char*)’:
> recordQT4L.cpp:96: error: invalid conversion from ‘const char*’ to ‘char*’
> make[1]: *** [recordQT4L.o] Error 1
> make[1]: Leaving directory `/home/olsen/pd/extra/0.92-1/Gem/src/Pixes'
> make: *** [Pixes] Error 2
> 
> 
> with gem0.92svn i stuck at the configure:
> ./configure: line 3005: syntax error near unexpected token `PIC,'
> ./configure: line 3005: `GEM_ARG_ENABLE(PIC,     PositionIndependentCode
> (potentially slower))'

you did run ./autogen.sh, did you?


mfgasr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkryAu0ACgkQkX2Xpv6ydvSKuACfXw1iDILzRRzQxQetWqZStlWR
w8EAoPbWSa53nuUpP8iptq07N7qJQW/k
=wCUA
-----END PGP SIGNATURE-----