Created attachment 275225 [details] Build log Hello there! You're getting this bug because the package in Summary failed to build in my tinderbox using the gold link editor from binutils. Before closing the bug as INVALID let me explain why this is still important! The gold link editor does not support underlinking of shared objects, which is something I have described in my blog post: http://blog.flameeyes.eu/2010/11/26/it-s-not-all-gold-that-shines-why-underlinking-is-a-bad-thing Even the basic link editor (ld.bfd) has an option to support this but it is a heck to enable and get passed, so linking with gold is simply quicker. Fixing underlinking provides optimized --as-needed builds (because the "softer" version no longer need to recover libraries that are underlinked), so it is a Good Thing To Do. Thank you very much for the attention!
This should also be reported to upstream -> bugzilla.gnome.org
See https://bugzilla.gnome.org/show_bug.cgi?id=613525 vte upstream doesn't want to fix this bug because they think it's gtk's fault; gtk upstream disagrees and won't fix it either :/
Seems this is fixed with this commit http://git.gnome.org/browse/vte/commit/?id=be41faea3651c2a90012648490ebf346eac82d04 The actual problem now is this configure line "checking for GDK target... " This is from: AC_MSG_CHECKING([for GDK target]) AC_MSG_RESULT([$GDK_TARGETS]) in configure.in. This "blank" mean GDK_TARGETS is mis-detected (it should be x11 usually on Linux). If there is x11 in GDK_TARGETS, it add link to x11 as the above commit do. We are applying vte-2.28.0-fix-gdk-targets.patch and this patch is the root of this problem. You see this line in the build.log "./configure: line 3084: --variable: command not found" This patch try to use PKG_CONFIG before the configure set it. We should fix the patch to detect GDK_TARGET properly.
Created attachment 287883 [details, diff] new vte-0.28.0-fix-gdk-targets.patch Replacing vte-0.28.0-fix-gdk-tragets.patch with this file solved the problem. Please review this new patch and commit it if there's no problem with it.
Looks to work fine for me, but would prefer to wait a bit for other team members to confirm (If in a week or so no action was taken, feel free to comment again here to push this up)
Fixed, thanks a lot