[asterisk-bugs] [Asterisk 0012022]: Compile fails with "structure has no member named `tm_gmtoff'"
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Feb 20 07:04:04 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12022
======================================================================
Reported By: asgaroth
Assigned To: Corydon76
======================================================================
Project: Asterisk
Issue ID: 12022
Category: Core-General
Reproducibility: always
Severity: major
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.18
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 02-19-2008 01:59 CST
Last Modified: 02-20-2008 07:04 CST
======================================================================
Summary: Compile fails with "structure has no member named
`tm_gmtoff'"
Description:
I have been unable to build asterisk 1.4.17/1.4.18 on Solaris x86. The
specific error message is as follows:
[CC] stdtime/localtime.c -> stdtime/localtime.o
stdtime/localtime.c: In function `localsub':
stdtime/localtime.c:1136: error: structure has no member named
`tm_gmtoff'
gmake[1]: *** [stdtime/localtime.o] Error 1
gmake: *** [main] Error 2
I am not too sure how far back this change was made that breaks a build on
Solaris, I can say with certainty that the last version I built
successfully was 1.4.13 (Without the above error). I have not tried
building .14/.15 or .16 editions.
======================================================================
----------------------------------------------------------------------
asgaroth - 02-20-08 07:04
----------------------------------------------------------------------
I think I have found another issue with the compilation that is holding up
the build of 1.4.18. It has to do with a "u_int32_t" failure, do I need to
log another bug, or can I post it here?
Issue History
Date Modified Username Field Change
======================================================================
02-20-08 07:04 asgaroth Note Added: 0082634
======================================================================
More information about the asterisk-bugs
mailing list