At 07:18 PM 2/5/03 +0100, Zdenek Kabelac wrote:
Take a look at the most recent (#179220) Debian bug report filed (with patch) for vcr. It's at this URL:> This is a sort of problem that occurs with some regularity, BTW. My > Debian-unstable (Sid) video boxes currently do not work with the very > latest version of libavifile once again, because vcr hasn't yet been > updated to use the new API. (It's a particular problem with this appAPI should be backward compatible - if there is something incompilable or missing let me know - but just recompilation should be enough - if the package has been using some undocumented or 'in developement' feature - it might require update - but common interface has remained the same for more then 2 years...
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=vcr
Its author claims that a change in the libavifile API causes a patch (which he supplies) to be needed in vcr.
Subsequent to my reading that bug report, updating Sid caused still newer avifile packages to be installed. When I try to run vcr now (with what apt thinks is current versions of everything as of about 15 minutes ago), I get a different failure (I'm having to retype this, so please forgive any typos):
vcr: relocation error: /usr/lib/libaviplay-0.7.so.0: undefined symbol: _ZTVN10__cxxabiv120__si_class_type_infoE
I haven't tried a recompile yet (I thought I'd give Debian upstream a chance to update first, including correcting the prior bug ... and you'll recall that Sid is in the midst of changing its standard gcc version right now as well ... calling it "unstable" is truth in advertising), so a simple recompile may fix this newer problem.
BTW, a normal "apt-get upgrade" doesn't cause the problem to show up, because libavifile is a "held-back" package if vcr (maybe other apps too) is present on the system. I see it only on the system I have that is a new install. (This may be why you are not hearing about these problems.)
The prior time I saw segfault problems (I think last October), a simple recompile of vcr against the new headers was all that was needed. The time before that (June? July?), vcr needed the patch I previously described to remove its own "invert the image" step.
And just a reminder for others here -- this patching is only occurring with the Debian version of vcr, to the best of my knowledge.
> because vcr has apparently been abandoned by its author, and only its
> Debian version is being updated to stay in sync with libavifile.) I go
> through this problem here roughly once every 3 months, as outside apps need
> to catch up to changes to libavifile. That you get used to it is the only
> advice I can offer.
The only think which has really changes has been the abadoned usage
of exceptions - and this has been only for practical reason -
various versions of gcc either aborts() or leak memory - this makes
the whole point of the usage of expections completely meaningless
as you basicaly could never know what actually will happen whenver
you throw exception.
(and thanks goes to GCC developers :) for clearing this out...)
If there are some simple stupid 'compatible' problem - please report
them - I'm trying to keep things compatible for 0.7 version.
-- -------------------------------------------"Never tell me the odds!"-------- Ray Olszewski -- Han Solo Palo Alto, California, USA [EMAIL PROTECTED] ------------------------------------------------------------------------------- _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
