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 653177 - Don't bail out when running on a different release
Don't bail out when running on a different release
Status: RESOLVED FIXED
Product: libgtop
Classification: Core
Component: general
2.28.x
Other All
: Normal normal
: ---
Assigned To: libgtop maintainers
libgtop maintainers
: 602666 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-06-22 15:50 UTC by Jasper Lievisse Adriaanse
Modified: 2013-04-01 11:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jasper Lievisse Adriaanse 2011-06-22 15:50:31 UTC
FreeBSD has had this patch for a while:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/libgtop/files/patch-src_daemon_server.c

The problem is that on FreeBSD that packages for a certain release can be built on different release (right, Marcus?). Same goes for OpenBSD to a lesser extend, as a machine can be running 5.0-beta with a package for 4.9-current. Not to mention cross-compiling.
This leads to differences in LIBGTOP_COMPILE_RELEASE and triggers the message and stops the application.

While it's possible for FreeBSD and OpenBSD to keep maintaining this patch in our ports trees, would generalizing it to something like this make it Ok for inclusion in libgtop?

Say, just an #ifdef dance for __NetBSD__ && __FreeBSD__ && __OpenBSD__ around _exit(1) ?
Comment 1 Colin Walters 2011-06-22 16:22:41 UTC
If it's a general desync problem, then improving the error message looks fine to me?
Comment 2 Jasper Lievisse Adriaanse 2011-06-22 16:26:07 UTC
Like changing the error message to what FreeBSD does? That would be sane.

What shall we do with the _exit(1). Should non-BSD keep hitting that, or can it be removed altogether since we have a clearer error message?
Comment 3 Jasper Lievisse Adriaanse 2011-08-30 12:39:06 UTC
It seems there is another ticket related to the issue: #602666.
Any objections to committing that patch to get rid of the message altogether?
Comment 4 Joe Marcus Clarke 2011-08-30 14:38:08 UTC
I like the idea, obviously.  The exit was a bit much,
Comment 5 Jasper Lievisse Adriaanse 2011-08-30 16:19:22 UTC
*** Bug 602666 has been marked as a duplicate of this bug. ***
Comment 6 Antoine Jacoutot 2013-04-01 11:31:51 UTC
This patch makes sense, please push it.
Comment 7 Jasper Lievisse Adriaanse 2013-04-01 11:37:10 UTC
Thanks, it's been pushed.