Your message dated Thu, 23 Nov 2023 12:38:39 -0700
with message-id <[email protected]>
and subject line Re: clang-15: resource directory lacks stable path
has caused the Debian Bug report #1038991,
regarding clang-15: resource directory lacks stable path
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1038991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038991
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: clang-15
Version: 1:15.0.7-4
Severity: wishlist
X-Debbugs-Cc: [email protected], [email protected]

Dear Maintainer,

I would like to update HIP to use clang-16, but that would require
building the rocm-device-libs with clang-16. Once I do that, they may no
longer be compatible with clang-15, but they will still be found in a
path that clang-15 will search.

It would be nice to match the behaviour of upstream (and Fedora) by
placing the rocm-device-libs in the clang resource directory.
Unfortunately, `clang++-15 -print-resource-dir` shows that the current
resource dir is '/usr/lib/llvm-15/lib/clang/15.0.7', which includes the
clang patch version and therefore may change in future package updates.

If the resource directory path could be relied upon to remain unchanged,
it would be possible to install the rocm-device-libs directly into the
clang resource directory and drop the patches in HIP and LLVM used to
search the system library directories.

Could a stable path to the resource directory be established for each
major version of clang?

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages clang-15 depends on:
ii  binutils                2.40.50.20230622-1
ii  libc6                   2.36-9
ii  libc6-dev               2.36-9
ii  libclang-common-15-dev  1:15.0.7-4
ii  libclang-cpp15          1:15.0.7-4
ii  libclang1-15            1:15.0.7-4
ii  libgcc-12-dev           12.3.0-4
ii  libgcc-s1               13.1.0-6
ii  libllvm15               1:15.0.7-4
ii  libobjc-12-dev          12.3.0-4
ii  libstdc++-12-dev        12.3.0-4
ii  libstdc++6              13.1.0-6
ii  llvm-15-linker-tools    1:15.0.7-4

Versions of packages clang-15 recommends:
ii  llvm-15-dev  1:15.0.7-4
ii  python3      3.11.2-1+b1

Versions of packages clang-15 suggests:
pn  clang-15-doc  <none>
pn  wasi-libc     <none>

-- no debconf information

--- End Message ---
--- Begin Message --- In clang-16 and onwards, the resource directory has a stable path (because it no longer includes the patch version number). As such, the rocm-device-libs for clang-15 can continue to use the global directory, while rocm-device-libs for clang-16 and later can use the appropriate clang resource directory.

Sincerely,
Cory Bloor

--- End Message ---

Reply via email to