Julien PUYDT a écrit: >>0. My camcorder works great with dvgrab, so I know that there is no >>fundamental OS problem. But gnomemeeting doesn't recognize the device >>under the AVC plugin. > > Is it an AVC or a DC? You have to be sure!
How do I tell? I can't find anything in the FAQ about this. I assumed that I need DC, as no devices were found by gnomemeeting with the AVC plugin. >>2. My only course of action is to download the pwlib source, and to set >>about compiling it myself. The next problem I encounter is that the >>source is not ISO C++, and g++ 4.0 refuses to compile it. > > > Hmmm... this raises two questions: > 1. which pwlib sources? You have to use the exact version that > gnomemeeting was compiled for, or it will crash hard and fast. > 2. our debian packager didn't complain that much about g++ 4.0... so I > guess he could get pwlib to compile with it. I used the sources on the gnomemeeting website: http://www.gnomemeeting.org/index.php?rub=5&path=sources/sources gnomemeeting-1.2.1.tar.gz openh323-1.15.3.tar.gz pwlib-1.8.4.tar.gz >>4. Having tried manual compilation (the old-fashioned way), it occurs >>to me that I'm too old-school, and there may be a simpler approach. So >>I download the source RPMs, and attempt to 'rpmbuild' these. To get >>rpmbuild to use g++32, I prefix the command line with CXX=g++32. e.g.: >> CC=gcc32 CXX=g++32 rpmbuild --rebuild pwlib-1.8.4-1.src.rpm >>But the configure script bombs out with the error: >> checking for x86_64-redhat-linux-gnu-g++... g++32 >> checking for C++ compiler default output file name... configure: >>error: C++ compiler cannot create executables >> See `config.log' for more details. > > > Have you seen 'config.log' for more details? Yes! I thought of that too! :-) The only extra information in config.log is something like "exiting with code 77". Does that help? It didn't mean much to me. Anyway, I finally figured out how to get the SRPMS to compile under FC4. I'll post that information in another message, since it might be useful to someone, somewhere. > I would first check that the device is not an AVC after all... Does it > work with kino? Haven't tried kino, but as I said initially, it works perfectly with dvgrab without adjusting any settings at all. Because gnomemeeting did not show any devices when set to the AVC plugin, I assumed my camera (it's a regular MiniDV camcorder) was not supported by that plugin. Is there something else I can try? BTW, when I finally did get everything compiled, I executed gnomemeeting, and set the plugin to DC. Gnomemeeting then recognized device /dev/raw1394. Hooray! But then a window pops up saying "Error while opening video device /dev/raw1394 ... There was an error while opening the device. Please check your permissions and make sure that the appropriate driver is loaded." I checked the permissions for /dev/raw1394 (and /dev/raw/raw1394, which is the new location for this device), and even tried chown'ing them to my own userid. No change. Any other ideas? Thanks, -- Dominick _______________________________________________ GnomeMeeting-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
