I looked at upstream ptlib sources yesterday and noticed that it uses calls in the libraw1394 v1 API which are no longer present in the v2 API. This is the same as with pwlib, see bug 272848. Reproducible: Always Steps to Reproduce: 1. emerge libraw1394 v2 2. emerge ptlib with ieee1394 use flag The "avc" and "dc" video input modules are both controlled by the ieee1394 use flag. 1. The "dc" module uses libdc1394 v1 (and minimally libraw1394, v1 or v2 should both work from what I saw in the source). The dc module is for IIDC (a.k.a. DCAM) cameras which send uncompressed video. Those are industrial-grade cameras, and a few webcams which are no longer produced. 2. The "avc" module uses libraw1394 and must depend on <= libraw1394 v1, as noted in comment 4. The avc module is for DV camcorders (which follow the AV/C standard; DV is compressed video). So, should there perhaps be separate dc1394 and avc1394 use flags instead of the shared ieee1394 use flag?
Created attachment 196692 [details] build.log
> 2. The "avc" module uses libraw1394 and must depend on <= libraw1394 v1, as > noted in comment 4 of bug 272848.
I hit this one today while updating opal (which pulled in ptlib-2.6.2). After reading through this bug and bug 272848. I opted to add a "--disable-avc", drop the ieee1394 use flag check for avc, and drop the dep on dev-libs/libavc1394 in favor of the debian team's choice over v4l2 and libdc1394 use. With the following flags, built clean: alsa asn audio config-file dns doc dtmf esd ffmpeg ftp http http-forms http-server ieee1394 ipv6 jabber ldap mail odbc pipechan qos remote sasl sdl serial shmvideo snmp soap socks ssl stun telnet tts url v4l v4l2 video video-file wav xml xmlrpc
Created attachment 197871 [details] modified ebuild modified ebuild to exclude libavc1394
Sorry for the delay, i wanted to take time to report the bug upstream [1] before disabling the plugin. So, avc plugin has been disabled for ptlib. [1] https://sourceforge.net/tracker/?func=detail&aid=2821744&group_id=204472&atid=989748
