Re: [GnomeMeeting-list] No DC plugin? Cannot compile...



Dominick Layfield a écrit :
I'm trying to get Gnomemeeting working with my firewire DV camcorder.
I'm running FC4 on x86-64.

x86-64... perhaps the DC plugin will have isssues: we don't distribute it widely because it is the most untested of all.

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!

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.

and a single remark: point (1) will force you to use an old version of pwlib, but point (2) will force you to use a recent version of pwlib... so perhaps that's the problem ;-)

3.  Next I install the compat-g++32 and compat-gcc32 Fedora packages, so
that I can try to compile under g++ version 3.2.  Though it ought to be
easy, compilation turns out to be a *major* headache.  Finally, when all
the parts compile, gnomemeeting terminates with a segmentation fault.

Bad version?

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?

I'm tearing my hair out.  Can anyone help?  For any stage?

I would first check that the device is not an AVC after all... Does it work with kino?

Snark on #gnomemeeting



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]