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 621653 - Compile error on Solaris 8 - variable time clashes with function time()
Compile error on Solaris 8 - variable time clashes with function time()
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.7.0
Other Solaris
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-06-15 14:43 UTC by Steve Evans
Modified: 2010-10-09 08:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Steve Evans 2010-06-15 14:43:44 UTC
I get this compile error on Solaris 8:

g++ -c -DENGLISH_ONLY -Wall -W -O2 -I../qtools -o ../objects/portable.o portable.cpp
portable.cpp:30: error: `QTime time' redeclared as different kind of symbol
/usr/include/iso/time_iso.h:91: error: previous declaration of `time_t time(time_t*)'
portable.cpp:30: error: declaration of `QTime time'
/usr/include/iso/time_iso.h:91: error: conflicts with previous declaration `time_t time(time_t*)'
portable.cpp: In function `void portable_sysTimerStart()':
portable.cpp:381: error: request for member `start' in `time', which is of non-class type `time_t ()(time_t*)'
portable.cpp: In function `void portable_sysTimerStop()':
portable.cpp:386: error: request for member `elapsed' in `time', which is of non-class type `time_t ()(time_t*)'

Renaming the variable time on line 30 of portable.cpp and all of its uses in the file fixes the compile error.
Comment 1 Dimitri van Heesch 2010-06-15 14:52:44 UTC
Thanks Steve, I'll but a g_ in front of this global variable.
Comment 2 Dimitri van Heesch 2010-06-25 11:49:05 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.1. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.
Comment 3 Dimitri van Heesch 2010-10-09 08:19:27 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.2. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.