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 645668 - Both git master and gtk-3-0 branch fail to build
Both git master and gtk-3-0 branch fail to build
Status: RESOLVED NOTGNOME
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
: 645670 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-03-25 20:52 UTC by Wouter Bolsterlee (uws)
Modified: 2011-06-01 03:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Wouter Bolsterlee (uws) 2011-03-25 20:52:46 UTC 
The build fails in both active branches:


  GISCAN Gtk-3.0.gir
./.libs/libgtk-3.so: undefined reference to `gdk_x11_window_set_theme_variant_gtk_only'
collect2: ld returned 1 exit status
Comment 1 Fabio Durán Verdugo 2011-03-26 00:24:27 UTC 
*** Bug 645670 has been marked as a duplicate of this bug. ***
Comment 2 Matthias Clasen 2011-03-26 21:10:05 UTC 
Builds fine here. I suspect the usual Debian libtool <> introspection bullshit
Comment 3 Wouter Bolsterlee (uws) 2011-03-27 21:11:42 UTC 
It seems that installing the binutils-gold linker (which becomes the default linker after installing) fixes the problem. I'm not really into these things – is there anything worth mentioning about that? If so, I'll report a downstream bug, but right now I don't know exactly how to formulate the problem…
Comment 4 Wouter Bolsterlee (uws) 2011-03-27 21:12:24 UTC 
(Oh, and fwiw: the problem occurred on a Debian unstable system)
Comment 5 Wouter Bolsterlee (uws) 2011-04-09 11:06:28 UTC 
Hi Matthias,

You are probably totally right about this issue, but it strikes me that you RESOLVED this bug twice as NOTGNOME without providing any sufficient response.

The first time you did so providing a not so helpful explanation using not so nice language either ("the usual Debian libtool <> introspection bullshit"). I reopened the issue and asked very politely for your help, conciously ignoring the tone of your previous reply and even providing additional information.

A few weeks later you decided to close this bug again, not providing any response at all. I totally understand that you are extremely busy and that this is just one of the many issues you need to take care of, but the way this bug is handled just doesn't feel right to me. I can't express this any better than Gnome's Code of Conduct at http://live.gnome.org/CodeOfConduct does:

    If someone asks for help it is because they need it. Do politely suggest
    specific documentation or more appropriate venues where appropriate,
    but avoid aggressive or vague responses such as "RTFM".

Therefore I'm (re)opening this issue for the third time, politely asking you to answer to my previous question (in the third comment on this bug). We all try to make Gnome a better platform. Please consider that. Thanks in advance for your help.

Wouter
Comment 6 Matthias Clasen 2011-06-01 03:14:31 UTC 
I don't have further documentation to offer, unfortunately. And I don't think I have a responsibility to offer 'sufficient response' before I am allowed to close a bug...