clang/LLVM version targeted for bullseye?

[Vagrant Cascadian]

I'm looking at submitting patches for several packages to upgrade to
clang-10, as it supports the -ffile-prefix-map argument. Older versions
fail to build when passed this argument, triggering:

  https://tests.reproducible-builds.org/debian/issues/unstable/ffile_prefix_map_passed_to_clang_issue.html
  https://tests.reproducible-builds.org/debian/issues/bullseye/ffile_prefix_map_passed_to_clang_issue.html

In our test infrastructure, several packages using clang FTBFS because
we pass DEB_BUILD_OPTIONS=reproducible=+fixfilepath, and we do not
currently pass this in bullseye, where many of them build successfully.


So I'm wondering if clang-10 or clang-11 likely to be the default for
bullseye?


I've tested a few packages so far that seem to build fine with clang-10,
which supports -ffile-prefix-map. Is it reasonable in general at this
point to suggest packagers switch to using clang-10 or clang-11?


An alternate workaround for clang-9 is to disable this feature:

  DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath,+fixdebugpath

But then it should be removed once clang updates to 10 or newer...


Thanks for your work on LLVM and friends!


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20200929/cac7eb4c/attachment.sig>