Sören Tempel

> What interesting if I have installation of gcc-12 and libgcc-12-dev on my ubuntu 22.04 system I have broken clang build. After removing libgcc-12-dev I can do it by clang...

I fixed the master branch build with GCC 12.X. Can you rebase your changes against that? Maybe it helps with the build error.

Interesting that it fails with clang since that it was AOSP actually supports. Don't have the time to debug this further myself right now but will hopefully find some time...

How does boringssl obtain the Go dependencies then? Does the boringssl build system set `GOPATH` and vendor the dependency or how does it work with `GO111MODULE=off`?

Thanks for pointing this out, keep in mind though that 31.0.2 is not merged yet.

> Another question: Where do the used patches actually come from? From contributors to this repository, initially a few have been [copied from Arch](https://github.com/nmeum/android-tools#see-also).

I think I will just remove the NOTICE for the upcoming release, see https://github.com/nmeum/android-tools/pull/20#issuecomment-853097683

> How about asking the maintainers of the packages in the other distributions you mentioned in the README.md, if they would like to use this source repository as well (so...

> […] some glibc architectures requiring `-D_FILE_OFFSET_BITS=64`. Which architectures? Any idea why this is the case? If there is a specfic reason why this is needed we could just add...

Added `-D_FILE_OFFSET_BITS=64` to `CFLAGS` / `CXXFLAGS` by default. If you find anything else let me know. Ideally, android-tools should compile on all distros without any downstream patches.