boringssl's time_support.c should include time.h before time_support.h |
|||
Issue descriptionI just hit this locally on windows with clang/win: [1044/32652] CC obj\third_party\boringssl\src\crypto\boringssl.time_support.obj FAILED: ninja -t msvc -e environment.x86 -- "..\..\third_party/llvm-build/Release+Asserts/bin/clang-cl" -m32 /nologo /sh owIncludes /FC @obj\third_party\boringssl\src\crypto\boringssl.time_support.obj.rsp /c ..\..\third_party\boringssl\src\c rypto\time_support.c /Foobj\third_party\boringssl\src\crypto\boringssl.time_support.obj /Fdobj\third_party\boringssl\bor ingssl.c.pdb In file included from ..\..\third_party\boringssl\src\crypto\time_support.c:62: ..\..\third_party\boringssl\src\include\openssl/time_support.h(73,33) : error: unknown type name 'time_t'; did you mean 'size_t'? struct tm *OPENSSL_gmtime(const time_t *timer, struct tm *result); I tweaked my local header setup a bit for working on bug 592745 , so this is only broken on my machine -- but it's a true positive: time_support.h doesn't include anything but uses time_t. Either it should include time.h, or all of its clients need to include time.h before including time_support.h. time_support.c doesn't. davidben: If you tell me which of the two patches to write, I can write the patch if you want.
,
Mar 17 2016
The following revision refers to this bug: https://boringssl.googlesource.com/boringssl.git/+/b371f1b9ddd8ed519b4ab74b8860aea317e943fa commit b371f1b9ddd8ed519b4ab74b8860aea317e943fa Author: David Benjamin <davidben@google.com> Date: Tue Mar 15 22:06:13 2016 Include time.h in time_support.h. For time_t and struct tm. BUG= 595118 Change-Id: I6c7f05998887ed2bd3fb56c83ac543894ef27fe6 Reviewed-on: https://boringssl-review.googlesource.com/7462 Reviewed-by: Emily Stark (Dunn) <estark@google.com> Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> [modify] https://crrev.com/b371f1b9ddd8ed519b4ab74b8860aea317e943fa/include/openssl/time_support.h
,
Mar 18 2016
,
Mar 18 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by davidben@chromium.org
, Mar 15 2016