Bug ID 1124324
Summary meson: Bug in meson breaks building libmodulemd
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.1
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Development
Assignee bnc-team-screening@forge.provo.novell.com
Reporter ngompa13@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

When I try to build libmodulemd on openSUSE Leap 15.1, it fails with the
following error:

[   13s] FAILED:
modulemd/v2/modulemd@v2@@modulemd@sha/meson-generated_.._modulemd-enums.c.o
[   13s] cc -Imodulemd/v2/modulemd@v2@@modulemd@sha -Imodulemd/v2
-I../modulemd/v2 -I../modulemd/v2/include/modulemd-2.0 -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=c11 -Wpointer-arith -Werror=missing-declarations
-Wmissing-prototypes -Wstrict-prototypes -Wuninitialized
-Werror=format-security -Werror=format=2 -Werror=implicit -Werror=init-self
-Werror=main -Werror=missing-braces -Werror=return-type -Werror=array-bounds
-Werror=write-strings -DG_LOG_USE_STRUCTURED '-DG_LOG_DOMAIN="libmodulemd"'
-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables
-fstack-clash-protection -fPIC  -MD -MQ
'modulemd/v2/modulemd@v2@@modulemd@sha/meson-generated_.._modulemd-enums.c.o'
-MF
'modulemd/v2/modulemd@v2@@modulemd@sha/meson-generated_.._modulemd-enums.c.o.d'
-o
'modulemd/v2/modulemd@v2@@modulemd@sha/meson-generated_.._modulemd-enums.c.o'
-c modulemd/v2/modulemd-enums.c
[   13s] modulemd/v2/modulemd-enums.c:5:10: fatal error:
modulemd/v2/include/modulemd-2.0/modulemd.h: No such file or directory
[   13s]  #include "modulemd/v2/include/modulemd-2.0/modulemd.h"
[   13s]           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[   13s] compilation terminated.


The error is caused due to lack of the following commit from upstream not being
backported to our Meson package:
https://github.com/mesonbuild/meson/commit/c5865c50c444912afd92c2feb94d8739874a62b2

This was fixed in upstream meson 0.47.0, but the commit is trivial to backport
to meson 0.46.0. Thus, the problem doesn't exist in openSUSE Tumbleweed (as of
right now), but does exist in Leap 15.


You are receiving this mail because: