[roll] Roll fuchsia [heapdump][instrumentation] Do not dynamically link libunwind.so.1

When libheapdump_instrumentation.so is used by SDK clients,
libunwind.so.1 may not exist or have a different ABI in the client's
toolchain.

We originally used to link it statically using the
//build/config/fuchsia:static_cpp_standard_library config option, but
fxrev.dev/919272 removed it to avoid a warning, introducing the runtime
dependency on libunwind.so.1 by mistake.

This CL restores the old correct behavior, but in a way that does not
trigger the warning.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1013656
Original-Revision: d32d25ab25286365c806d4e5e1ffcaca18d8f153
GitOrigin-RevId: cc1bd1442aeac06df2a8a56fd3e09e333a2e5614
Change-Id: I017a1f87215caec64d29b5a7ee3f26da81736819
1 file changed
tree: 52769dbcbf81a527dd5a58e46e76f5586127f98d
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.