After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784236 - totem meson parallelized build fails when not previously installed
totem meson parallelized build fails when not previously installed
Status: RESOLVED NOTGNOME
Product: totem
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-06-27 06:07 UTC by Tristan Van Berkom
Modified: 2017-06-27 07:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Full configure and build log (49.53 KB, text/plain)
2017-06-27 06:07 UTC, Tristan Van Berkom
Details

Description Tristan Van Berkom 2017-06-27 06:07:48 UTC
Created attachment 354542 [details]
Full configure and build log

When building recent totem with meson and `ninja -j8`, the build fails, presumably only if totem was not previously successfully installed (I'm guessing this based on the error which would probably not happen if introspection and/or vapi information had been installed before building).

The error in question is:

FAILED: src/plugins/rotation/rotation@sha/totem-rotation-plugin.c src/plugins/rotation/rotation.h src/plugins/rotation/rotation.vapi 
valac -C --debug --pkg clutter-gtk-1.0 --pkg cogl-pango-1.0 --pkg libpeas-1.0 --pkg gtk+-3.0 -d src/plugins/rotation/rotation@sha --library=rotation -H src/plugins/rotation/rotation.h --use-header --vapi ../rotation.vapi --girdir=/buildstream/build/_builddir/src --pkg=Totem-1.0 ../src/plugins/rotation/bacon-video.vapi ../src/plugins/rotation/totem-rotation-plugin.vala
error: Package `Totem-1.0' not found in specified Vala API directories or GObject-Introspection GIR directories
Compilation failed: 1 error(s), 0 warning(s)


This happen when running `ninja -j 8 -C _builddir`, but it does not happen when running `ninja -j 1 -C _builddir`.

This might be a meson bug causing this ? I am unsure.

Attaching a more complete build log in case that is helpful.
Comment 1 Bastien Nocera 2017-06-27 07:43:48 UTC
It's a bug in meson:
https://github.com/mesonbuild/meson/issues/1994

Easiest way around the problem is to disable vala plugins for now.