Enable linaro-gcc bootstrap with asan config.
authorMikhail Kashkarov <m.kashkarov@partner.samsung.com>
Thu, 1 Aug 2019 13:34:10 +0000 (16:34 +0300)
committerSlava Barinov <v.barinov@samsung.com>
Thu, 27 Apr 2023 09:07:02 +0000 (12:07 +0300)
commit944f05c0d1df2085f01f758b2790fccdfa3a9d25
treedf8d55f2a9d36495fb1cc33670a2eaba3bf4612f
parent16d288cc394d920ef9eb060546abdc8b08fcad55
Enable linaro-gcc bootstrap with asan config.

We couldn't verify linaro-gcc bootstrap with dynmaic ASan as we don't update
library pathes while running executables, so the compilation is performed with
the new instrumentations and the old external runtime from the build environment
is used during run.

And we'll also get runtime conflicts with 2 libasan.so version inside sanitized
environment, so it doesn't make sense to define 'asanbootstrap' with 'asan'.

If we really do want to test dynamic ASan, we could add the following to the
POSTSTAGE1_LDFLAGS:

  "-rpath$$r/prev-$(TARGET_SUBDIR)/libsanitizer/asan/.libs"

and keep additional rpathes for final binaries or use patchelf tool.

Change-Id: I8783f0395521126f8e01125e24bc40ed457bc008
config/bootstrap-asan.mk
packaging/gcc-aarch64.spec
packaging/gcc-armv7hl.spec
packaging/gcc-armv7l.spec
packaging/linaro-gcc.spec