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 75741 - Build of GTK+ is broken on Solaris
Build of GTK+ is broken on Solaris
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
2.0.x
Other Solaris
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2002-03-21 12:46 UTC by padraig.obriain
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to fix build (653 bytes, patch)
2002-03-21 12:49 UTC, padraig.obriain
none Details | Review

Description padraig.obriain 2002-03-21 12:46:57 UTC
GTK+ does not build on Solaris from HEAD.

It fails in gdkwindow.c in G_BREAKPOINT because SIGTRAP is not defined.

This seems to have been caused by recent change to gobject when signal.h
was removed from gobject/gsignal.h
Comment 1 padraig.obriain 2002-03-21 12:49:41 UTC
Created attachment 7288 [details] [review]
Patch to fix build
Comment 2 Owen Taylor 2002-03-21 16:56:47 UTC
Fixed on the GDK end.

Thu Mar 21 10:04:05 2002  Owen Taylor  <otaylor@redhat.com>

	* gdk/gdkwindow.c (gdk_window_real_get_depth): Remove
	some left over debugging code with a G_BREAKPOINT()
	in it.

The issue of adding the signal.h include at this point was
discussed in some length on gtk-devel-list, though I can't
find the relevant thread right now. I think we decided
that anybody using G_BREAKPOINT() had to include signal.h
themselves, which obviously posed a big problem when
the G_BREAKPOINT() in question was in a header file.

The only reason I considered the need to include signal.h
at all acceptable is that I don't believe G_BREAKPOINT() should
ever appear in production code.
Comment 3 Owen Taylor 2002-03-21 21:16:48 UTC
Tim considers the fact that the include files changed NOTABUG.