[Solus Linux] Fails to build: fatal error: libgupnp/gupnp.h: No such file or directory

[ckorn]

Hi there,

currently I am trying to build a package of pragha-1.3.99.1 for Solus Linux. The missing flle exists in this directory: /usr/include/gupnp-1.2/libgupnp

But somehow it is not found. Probably because of a missing -I compiler flag. Can you help me here?

Making all in dlna
make[3]: Entering directory '/home/build/YPKG/root/pragha/build/pragha-1.3.99.1/plugins/dlna'
  CC       libdlna_la-pragha-dlna-plugin.lo
In file included from /usr/include/rygel-2.6/rygel-server.h:13,
                 from pragha-dlna-plugin.c:36:
/usr/include/rygel-2.6/rygel-core.h:6:10: fatal error: libgupnp/gupnp.h: No such file or directory
    6 | #include <libgupnp/gupnp.h>
      |          ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [Makefile:577: libdlna_la-pragha-dlna-plugin.lo] Error 1

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/92189785-solus-linux-fails-to-build-fatal-error-libgupnp-gupnp-h-no-such-file-or-directory?utm_campaign=plugin&utm_content=tracker%2F352350&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F352350&utm_medium=issues&utm_source=github).

[ckorn]

I was able to compile with this patch applied.

Index: pragha-1.3.99.1/plugins/dlna/Makefile.am
===================================================================
--- pragha-1.3.99.1.orig/plugins/dlna/Makefile.am   2019-08-13 13:42:44.000000000 +0200
+++ pragha-1.3.99.1/plugins/dlna/Makefile.am    2020-07-20 14:14:39.008780706 +0200
@@ -2,6 +2,9 @@

 AM_CPPFLAGS = \
    -I$(top_srcdir)     \
+   -I/usr/include/gupnp-1.2 \
+   -I/usr/include/gssdp-1.2 \
+   -I/usr/include/libsoup-2.4 \
    $(LIBPEAS_CFLAGS)       \
    $(LIBPEAS_GTK_CFLAGS)

However this does not seem correct.

Unfortunately the packaging request for Solus Linux was not accepted. But I will upload the build files to a repository in my account.

[tux93]

I was encountering the same on openSUSE Leap and applied your patch until a proper solution comes up