Closed
Bug 610234
Opened 14 years ago
Closed 14 years ago
nsWindow.cpp includes gtkprivate.h
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 627699
People
(Reporter: ht990332, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [GTK3])
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b8pre) Gecko/20100101 Firefox/4.0b8pre
Build Identifier:
gtkprivate.h is no longer installed in gtk2 fro gtk2 version 2.24
http://ftp.gnome.org/pub/GNOME/sources/gtk+/2.23/gtk+-2.23.1.changes
This breaks firefox build.
Reproducible: Always
Updated•14 years ago
|
Blocks: 339548
Keywords: regression
Updated•14 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•14 years ago
|
||
See bug 339548, comment #68 and following for why this was used in the first place. Guess something else is going to have to be done to get around that now...
Comment 2•14 years ago
|
||
Looks like Ubuntu 11.04 is going to ship with GTK+ 2.24, which means this bug will affect that release. Requesting blocking.
blocking2.0: --- → ?
Comment 3•14 years ago
|
||
gtkprivate.h was dropped in the 2.23.1 tarball by mistake (the 2.23.1 tarball wasn't based on the gtk-2.24 branch). I mentioned this to Matthias Clasen, and he rolled 2.23.2, whidh fixes this (ie, gtkprivate.h is back again).
gtkprivate.h is only going away in gtk 3
Comment 4•14 years ago
|
||
Note, we dropped 2.23.1 entirely from our archive once we noticed this, as it caused an ABI break too.
Updated•14 years ago
|
Comment 6•14 years ago
|
||
So http://ftp.gnome.org/pub/GNOME/sources/gtk+/2.23/gtk+-2.23.1.changes
diverges from those at http://git.gnome.org/browse/gtk+/log/?h=gtk-2-24
because gtk+-2.23.1.changes describe some other branch, I assume?
Or maybe the branch tag was moved.
Whiteboard: [GTK3]
Comment 7•14 years ago
|
||
Karl - yeah, the 2.23.1 release was created incorrectly, and didn't look like it came from the gtk-2-24 branch at all (or, at least I couldn't work out what commit the tarball was generated from when I tried to bisect an issue it was causing us).
The gtk-2.24 branch was never tagged 2.23.1, it seems like the tarball was rolled from a local branch that Matthias had.
Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•