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 778832 - Fix build failure on Continuous
Fix build failure on Continuous
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-02-17 13:49 UTC by Emmanuele Bassi (:ebassi)
Modified: 2017-02-19 19:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gir: Look in the right path for vtetypebuiltins.cc (979 bytes, patch)
2017-02-17 13:49 UTC, Emmanuele Bassi (:ebassi)
committed Details | Review

Description Emmanuele Bassi (:ebassi) 2017-02-17 13:49:41 UTC
Continuous builds vte in a separate build directory.

We caught this issue because Continuous disables the Vala bindings explicitly, which allows us to build VTE outside of the source directory.
Comment 1 Emmanuele Bassi (:ebassi) 2017-02-17 13:49:45 UTC
Created attachment 346074 [details] [review]
gir: Look in the right path for vtetypebuiltins.cc

The vtetypebuiltins.cc file is generated, so it can only be found in the
build directory, not in the source directory.

This fixes non-srcdir builds like GNOME Continuous.
Comment 2 Javier Jardón (IRC: jjardon) 2017-02-17 15:23:12 UTC
Review of attachment 346074 [details] [review]:

This is a build failure that is affecting the whole GNOME project
As part of the release team I'm ok on merging this; chpe feel
free to contact us if you prefer another solution for this problem
Comment 3 Emmanuele Bassi (:ebassi) 2017-02-17 16:06:56 UTC
Attachment 346074 [details] pushed as 9ca6db2 - gir: Look in the right path for vtetypebuiltins.cc
Comment 4 Christian Persch 2017-02-17 18:02:47 UTC
(In reply to Javier Jardón (IRC: jjardon) from comment #2)
> This is a build failure that is affecting the whole GNOME project
> As part of the release team I'm ok on merging this; chpe feel
> free to contact us if you prefer another solution for this problem

The patch is fine. Simple build fixes like this are always ok to commit.
(A bit puzzled though why something from a 6 day old commit now suddently causes a problem?)
Comment 5 Emmanuele Bassi (:ebassi) 2017-02-19 19:14:25 UTC
The builder has beeb out of commission since December and until this weekend, so we caught issues like these really late. Sorry about that.