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 664545 - FTBFS on !linux: 'SYS_gettid' undeclared
FTBFS on !linux: 'SYS_gettid' undeclared
Status: RESOLVED DUPLICATE of bug 660177
Product: gnome-online-accounts
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Online Accounts maintainer(s)
GNOME Online Accounts maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-11-22 09:19 UTC by Michael Biebl
Modified: 2012-03-14 16:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Biebl 2011-11-22 09:19:12 UTC
Version: 3.2.1
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646886

gnome-online-accounts fails to build on kfreebsd:

goalogging.c: In function 'goa_log':
goalogging.c:210:55: error: 'SYS_gettid' undeclared (first use in this function)
goalogging.c:210:55: note: each undeclared identifier is reported only once for each function it appears in
make[4]: *** [libgoa_backend_1_0_la-goalogging.lo] Error 1
make[4]: Leaving directory `/build/buildd-gnome-online-accounts_3.2.1-1-kfreebsd-amd64-7CtYoG/gnome-online-accounts-3.2.1/src/goabackend'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/build/buildd-gnome-online-accounts_3.2.1-1-kfreebsd-amd64-7CtYoG/gnome-online-accounts-3.2.1/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd-gnome-online-accounts_3.2.1-1-kfreebsd-amd64-7CtYoG/gnome-online-accounts-3.2.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd-gnome-online-accounts_3.2.1-1-kfreebsd-amd64-7CtYoG/gnome-online-accounts-3.2.1'
make: *** [debian/stamp-makefile-build] Error 2

Full build log at 
https://buildd.debian.org/status/fetch.php?pkg=gnome-online-accounts&arch=kfreebsd-amd64&ver=3.2.1-1&stamp=1319757645


The usage of SYS_gettid is not portable, according to [1]. It only seems to be used for logging, so I guess it would be just fine to check for the availability of SYS_gettid and use it conditionally.


[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590005#15
Comment 1 Debarshi Ray 2012-03-14 16:21:05 UTC

*** This bug has been marked as a duplicate of bug 660177 ***