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 583923 - NI_IDN undefined
NI_IDN undefined
Status: RESOLVED DUPLICATE of bug 652602
Product: system-monitor
Classification: Core
Component: general
git master
Other NetBSD
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 595800 617033 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-05-26 19:08 UTC by Thomas Klausner
Modified: 2012-01-06 23:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thomas Klausner 2009-05-26 19:08:01 UTC 
a) 2.26.x is missing in the Version field

b) for gnome-system-monitor-2.26.2, compilation on NetBSD fails with:
openfiles.cpp: In function 'char* friendlier_hostname(const char*, int)':
openfiles.cpp:70: error: 'NI_IDN' was not declared in this scope
I looked up the value on a Linux system and added
#ifndef NI_IDN
#define NI_IDN 32
#endif
to that file which makes compilation succeed.
Comment 1 Daniel Macks 2009-09-21 06:35:26 UTC 
*** Bug 595800 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Macks 2009-09-21 06:38:19 UTC 
Note my (accidental dup) filing, which adds OS X as a platform affected by this same problem. However, I don't think hard-coding a constant that isn't defined in a system header is the right way to get the intended action from a system-library function...solves the build failure, but makes a blind assumption that the value platform-independent (may be true) and that the feature the flag triggers is even available at all (definitely not true).
Comment 3 Daniel Macks 2009-09-22 01:28:15 UTC 
Looks like it's the "libidn" extension in glibc. Well heck, libidn is an independently-available library, so a portable solution is to use the standard-compliant form of getnameinfo() and then use libidn to do the IDN conversion. That would work for everyone. Alternatively, could have ./configure test for the availability of NI_IDN and only fall back to external libidn if necessary. Could developers chime in here about what approach would be preferred?
Comment 4 Daniel Macks 2010-04-28 05:14:29 UTC 
*** Bug 617033 has been marked as a duplicate of this bug. ***
Comment 5 Daniel Macks 2010-04-28 05:15:29 UTC 
Anyway, still broken on 2.28. Could a developer chime in here about how to proceed, or if there is still any work being done on this module?
Comment 6 Robert Roth 2012-01-06 23:52:19 UTC 

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