-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FTFBS with glib2.0 >=2.66.3 #500
Comments
@bzed - FYI in case you want/need to build for the glib2.0 in debian/experimental |
Hey just to say that I wouldn't call this a temporary workaround. I think you should apply a patch like this one as general good practice to guard against future deprecations or behaviour changes affecting you until you opt in to them. (In the absence of having it defined you always get the latest stuff available at build time, which might sometimes include breakage like this.) https://developer.gnome.org/glib/stable/glib-Version-Information.html#GLIB-VERSION-MIN-REQUIRED:CAPS But if you ever want to be able to lift this requirement to a higher version, to use newer APIs for example, then you'll need to fix the Cheers! |
Thanks for the clarifications @iainlane ! |
@cpaelzer Thank you for reporting this issue, an internal bug has been filed to track it. |
This is causes open-vm-tools to FTBFS on Fedora 34 now as well. |
We are working and validating the fix on Fedora 34 that addresses this and also addresses use of a deprecated function in a newer GTK3. Stay tuned. |
Excellent! Just FYI, I've filed a bug in RHBZ as well, please make sure once this is fixed that this is addressed: https://bugzilla.redhat.com/show_bug.cgi?id=1939718 |
With glib2.0 releases >= 2.66.3, glib header files inside an extern "C" block will encounter compilation errors. This has impacted several OSS packages. Consumers of newer versions of glib2.0 must not include glib headers in an extern "C" block. GTK 3.20 has deprecated gdk_display_get_device_manager(); using the newer gdk_display_get_default_seat() when the GTK version is >= 3.20. The return value from read() must be used to avoid an unused result warning from the compiler. This can be avoided by using dummy retyping in the case where the return value is not used or in this case, using the returned value in a debug log message. Pull Request: #505 Addresses: #500 Addresses: #509
FTFBS due to new glib2.0 >=2.66.3
Example:
Full log:
https://launchpadlibrarian.net/525172798/buildlog_ubuntu-hirsute-amd64.open-vm-tools_2%3A11.2.5-2_BUILDING.txt.gz
On the glib side this is due to:
https://gitlab.gnome.org/GNOME/glib/-/issues/2331
Also related:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1935
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/J3P4TRHLWNDIKXF76OLYZNAPTABCZ3U5/#7LXFUDBBBIT23FE44QJYWX3I7U4EHW6M
There is a temporary workaround by hard setting the GLIB versions requested.
This I'll use to un-break the build in Ubuntu for now.
=> http://launchpadlibrarian.net/526861180/open-vm-tools_2%3A11.2.5-2_2%3A11.2.5-2ubuntu1.diff.gz
But mid term I guess you'll need to sort out the inclusion of such headers from CPP context more in general.
The text was updated successfully, but these errors were encountered: