Bug 1519731 - pipewire-devel-0.1.6-1 misses spa/pod-parser.h
Summary: pipewire-devel-0.1.6-1 misses spa/pod-parser.h
Keywords:
Status: CLOSED DUPLICATE of bug 1514955
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1519203 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-01 10:44 UTC by Robert Mader
Modified: 2017-12-01 17:31 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-01 17:31:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Mader 2017-12-01 10:44:01 UTC
Description of problem:
pipewire-devel does not provide the file /usr/include/spa/pod-parser.h, making it impossible to build packages against it.

Version-Release number of selected component (if applicable):
0.1.6-1

How reproducible:
Always.

Steps to Reproduce:
1. try to build e.g. mutter from srpm on a fully updated system

Actual results:
the build fails with the following error:
In file included from /usr/include/spa/node.h:34:0,
                 from /usr/include/pipewire/port.h:31,
                 from /usr/include/pipewire/core.h:45,
                 from /usr/include/pipewire/client.h:47,
                 from /usr/include/pipewire/pipewire.h:29,
                 from backends/meta-screen-cast.c:27:
/usr/include/spa/props.h:29:10: fatal error: spa/pod-parser.h: No such file or directory
 #include <spa/pod-parser.h>
          ^~~~~~~~~~~~~~~~~~
compilation terminated.

Expected results:
It should compile

Additional info:
easy workaround: just get the file from github (https://raw.githubusercontent.com/PipeWire/pipewire/0.1.6/spa/include/spa/pod-parser.h)

Comment 1 Robert Mader 2017-12-01 10:45:07 UTC
*** Bug 1519203 has been marked as a duplicate of this bug. ***

Comment 2 Robert Mader 2017-12-01 17:31:09 UTC

*** This bug has been marked as a duplicate of bug 1514955 ***


Note You need to log in before you can comment on or make changes to this bug.