This mode instructs the linker to search for libraries in hwasan
subdirectories of all library search paths. This is set up to contain a
hwasan-enabled copy of libc, which is needed for HWASan programs to
operate. There are two ways this mode can be enabled:
* for native binaries, by using the linker_hwasan64 symlink as its
interpreter
* for apps: by setting the LD_HWASAN environment variable in wrap.sh
Bug: 276930343
Change-Id: I0f4117a50091616f26947fbe37a28ee573b97ad0
The apex hash tree is automatically generated at compile time for
apexes in apexd-bootstrap, so there's no need to explicitly specify
anything here.
Bug: b/203820392, b/198361718
Test: presubmit
Change-Id: I5ff0363fde701e7fe4e3ed8ab274c6a57852828c
Non-updatable APEXes are going to be only present on a dm-verity
protected read-only partition. For such APEXes there is no need in
embedding a hashtree.
This is a no-op change in preparation of switching default value of
generate_hashtree to true.
Bug: 190621617
Test: m
Change-Id: I426c1fce37ce63200810d69092660644e13291c2
Auto-generate NOTICE files for all the directories, and for each one
individually rather than mixing libc and libm together.
Test: N/A
Change-Id: I7e251194a8805c4ca78fcc5675c3321bcd5abf0a
Currently, this is the default so this is a no-op,
But the default is changing to true.
Bug: 180375550
Test: Treehugger
Change-Id: I74cfd805958687a4c1e43eded31fb0e6583c1482
Move linkerconfig to Runtime APEX for better updatability. linkerconfig
shared ld.config.txt format with linker, so it is better that linker and
linkerconfig to be updated together. This change moves linkerconfig into
Runtime APEX.
Bug: 165769179
Test: Cuttlefish boot succeeded
Change-Id: I81e2a547804ab9f796c00af382ae43e35c8459ef
Linkerconfig is going to remove all hard-coded dependencies from APEX
modules and let APEX modules specify its own requirements. As part of
it, this change adds a new configuration file for linkerconfig and let
it aware that bionic APEX should be visible from all sections.
Bug: 167946001
Test: atest passed
Change-Id: If934d9a3e72b1466ee0d7bbb66d9383b90986a6b
ART runs it on host to create the linker config for its chroot test
environment. This avoids problems building linkerconfig in the reduced
master-art manifest.
Even though linkerconfig currently is in platform/system I'm adding it
to the Bionic module exports based on discussions that the linkerconfig
binary should be part of the Runtime (Bionic) APEX due to its close
ties to the linker.
Test: build/soong/scripts/build-aml-prebuilts.sh runtime-module-host-exports
then try the prebuilt snapshot with art/tools/buildbot-build.sh in
master-art
Bug: 162819454
Change-Id: I4d43d7f0b980af48b193d5eb358e4f010eea541b
ART runs some tests on host using linux_bionic (cf.
ab/git_master-art-host). On device Bionic binaries come from its APEX,
but on host they have to be supplied separately. Since they're not part
of the SDK they are instead provided through a `module_export` module,
which is technically similar to `sdk` in the way it produces prebuilt
snapshots.
Test: art/test/testrunner/run_build_test_target.py art-linux-bionic-x64
on a master-art branch using snapshot built from runtime-module-sdk
and runtime-module-host-exports
Bug: 152255951
Change-Id: I143b5412f7284f42c7e8be6cecc5ec96f1dc70f3
Test: v
1. build/soong/scripts/build-aml-prebuilts.sh runtime-module-sdk
2. Unzip out/aml/soong/mainline-sdks/runtime-module-sdk-current.zip
into prebuilts/module_sdk/runtime in a master-art tree without
platform/bionic in its manifest.
3. Check that all shared libs in the generated Android.bp file in the
zip archive have stubs.version set.
4. art/build/apex/runtests.sh is successful in the master-art tree.
Bug: 152255951
Change-Id: Iaada409c2edfa504056da8bebfb30756456eb282
A future change will introduce a version lock between linker and
crash_dump. Move crash_dump into the runtime APEX alongside linker in order to
ensure that they will be the same version even if the runtime APEX is updated.
Bug: 135772973
Change-Id: I94740f9c45107f08490df639a2e4d589a3044847
Merged-In: I94740f9c45107f08490df639a2e4d589a3044847
Dynamic linker will use generated linker configuration in general. As
ld.config.txt file in the APEX module will not be used, we can remove
this to avoid confusion.
Bug: 149887007
Test: m -j passed
Test: Boot succeeded from cuttlefish and walleye
Change-Id: Iffd2113cf29055a7263eb3697547297639e9dc0c
