Age | Commit message (Collapse) | Author |
|
As of https://boringssl-review.googlesource.com/27524, BoringSSL
automatically excludes those files on Trusty.
As of https://boringssl-review.googlesource.com/49265, BoringSSL checks
__TRUSTY__ instead of TRUSTY.
Tested: trusty/vendor/google/aosp/scripts/build.py generic-arm64-test-debug
Change-Id: I45c1a78d53082a0668b4621a328f965571875a11
|
|
Changes openssl-stubs from a standalone library into extra sources
included in the boringssl library.
Boringssl is the only user of openssl-stubs in Trusty. Because we don't
want to expose it in the SDK, we need to roll it into the boringssl
library itself.
Test: build.py qemu-generic-arm64-test-debug
Bug: 169448829
Change-Id: I1118ae7aaad1be1bc3ce1821b3c0d3939277dd4f
|
|
If we disallow usage of FP instructions, we can't build a ghash or
chacha armv8 assembly. Disable including these files if ALLOW_FP_USE is
disabled.
Test: Add boringssl to kernel and build
Bug: None
Change-Id: I1a9ddb38110fb6963d00084578fa94ab5f69bfca
|
|
The AOSP Clang stdatomic.h header (which is actually the bionic header,
not the LLVM one) does not build against musl, since musl does not
include a sys/cdefs.h header. Until this is resolved, we are disabling
the C11 atomics usage in BoringSSL.
Test: build.py
Bug: 194209538
Change-Id: I4d2a658e4563092bc7e75a70020a4a8de2acf3e2
|
|
Switch to building boringssl with the library.mk system instead of as a
generic lk module.
Test: build.py qemu-generic-arm64-test-debug
Change-Id: I04b91b6c18480bdc9018be18aebaf9b40bdefedf
|
|
We now have an STL available for boringssl, so we can build with C++
support which is needed for ACVP testing. Remove the define suppressing
C++ APIs.
Test: build.py qemu-generic-arm64-test-debug
Change-Id: Ibc5cc5fe3a8461b8f73ad32e96112bd8577c1840
|
|
By default static linking is enabled in trusty modules
Bug: 157916058
Change-Id: I122a5bc31e37bbe3fc5a80e9344a6ed2726f0f01
|
|
Bug: 141189390
Change-Id: I583fac431383fc829c24adf95ab4a51be61cfc93
|
|
Bypass compiling src/crypto/fipsmodule/rand/urandom.c as it is not
supported.
Remove filtering out now non-exiting files.
Change-Id: If0308aea56ab602a4fb59e9bb55a2ae02683d3c5
|
|
Adjust rules.mk (Trusty specific makefile) to accomodate for
new location of src/crypto/asn1/time_support.c (former
src/crypto/time_support.c)
Change-Id: I25af0c87812edb1611b877a1717e62e317f4a88e
|
|
This includes the following changes:
https://boringssl.googlesource.com/boringssl/+log/0e9138d295cd556e830dc8b3be735e808680f4bd..e34bcc91c07c0bf65ecc53a814d51f5246007150
This also removes BORINGSSL_ENABLE_RC4_TLS and android_compat_hacks.c as
they are no longer needed.
Test: Built tree, phone boots. Ran cts-tradefed run cts -m CtsLibcoreTestCases
Change-Id: I86df196e1856c338bbf72c60e2e47dd1b74ae537
|
|
This is required by new keymaster code.
Bug: 31439506
Change-Id: I7c7f9b62a0c378a59188eac6c8480d42a3f1107a
|
|
This includes the following changes:
https://boringssl.googlesource.com/boringssl/+log/aa24851515d6280aa1d6a8b1548fe74691df3136..0e9138d295cd556e830dc8b3be735e808680f4bd
This requires some build tweaks:
- trusty's rules.mk builds with BORINGSSL_NO_CXX to suppress the new C++
scopers since they build their version of keymaster without the STL.
- BORINGSSL_ENABLE_RC4_TLS to temporarily keep RC4 in the TLS stack.
Change-Id: Ic688ec5779f649a4912b00fb2b55cba64fb07449
|
|
Change-Id: Ide28171787db4e481b0b05b4107e58071d8c0fee
|
|
The default partially linked lk module .o files does not allow
unreferenced assembly files to be dropped.
Change-Id: I49931c6e1a17fa6552fa444c8e5e20ca7fca5cf1
|
|
This allows linking into the kernel.
Change-Id: Ia906bc8eff1f85a78aa8afb72f7fd0d26d5529ee
|
|
Change-Id: I6a663f0039eb1557269696b1af9034cda5dbb983
|
|
(This is a no-op change for the Android build. The Android build system
doesn't care about rules.mk.)
Change-Id: I19359abd83983efa597047f88295bb4f88bb415b
|