[Bug 297450] New video(4) framework conflicts with multimedia/v4l_compat
| Newsgroups | gmane.os.freebsd.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297450
Bug ID: 297450
Summary: New video(4) framework conflicts with
multimedia/v4l_compat
Product: Base System
Version: 16.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: [email protected]
Reporter: [email protected]
The problem at a glance can be seen in the following poudriere build log:
https://pkg-status.freebsd.org/beefy24/data/main-amd64-default/p41b0a5a50014_s207d96dabf/logs/opencv-4.13.0_7.log
To put it short, our base headers now define the same types and structs as
Linux ones coming from the multimedia/v4l_compat port. This is not a complaint,
rather a question on how we porters should now adapt our ports. Are FreeBSD
video(4) headers and definitions expected to be compatible with v4l ones? In
this case, we can just drop multimedia/v4l_compat in affected ports and let
them build against native headers?
--
You are receiving this mail because:
You are the assignee for the bug.