Request 1156747 (accepted)

Overview

Request 1156747 accepted

- New package based on version 18.1.1.
* For details, see the release notes:
- https://releases.llvm.org/18.1.0/docs/ReleaseNotes.html
- https://releases.llvm.org/18.1.0/tools/clang/docs/ReleaseNotes.html
- https://releases.llvm.org/18.1.0/tools/clang/tools/extra/docs/ReleaseNotes.html
- https://releases.llvm.org/18.1.0/projects/libcxx/docs/ReleaseNotes.html
- https://releases.llvm.org/18.1.0/tools/lld/docs/ReleaseNotes.html
* New LLVM tool: llvm-readtapi, LLVM TAPI file reader and
transformer.
* Removed LLVM tools: llvm-tapi-diff, llvm-remark-size-diff.
* New LLDB tool: lldb-dap debug adapter.
* Removed LLDB tool: lldb-vscode.
- Rename libomp-devel symbolic name to libomp-devel-provider.
We want to introduce a metapackage named libomp-devel.
- Rebase patches:
* assume-opensuse.patch
* link-clang-tools-extra-shared.patch
* llvm_build_tablegen_component_as_shared_library.patch
* llvm-do-not-install-static-libraries.patch
* llvm-fix-find-gcc5-install.patch
* llvm-normally-versioned-libllvm.patch
* llvm-suse-implicit-gnu.patch
- Add patches to fix tests:
* clang-fix-modules-test-riscv.patch
* clang-fix-openmp-test-non-x86.patch
* clang-fix-openmp-test.patch
* llvm-fix-cov-test-i586.patch
- Restructure version macros in specfile for new versioning scheme.
- Fix packaging of ld.lld as ld alternative.
- Disable LLDB Python bindings on SLE/Leap. They now require Swig 4
which isn't available there.

Created by aaronpuchert 3 months ago
In state accepted

Submit llvm18

Comments for request 1156747 4

Marcus Rueckert (darix) - 3 months ago

reviewer

mrueckert wrote (1156747) (https://build.opensuse.org/request/show/1156747) if you do not set any %attr() on %ghost it will set the the attr to

----------    1 root     root                        0 Mär  8 21:47 /etc/alternatives/bugpoint

compared to the ls output

ls -ld /etc/alternatives/bugpoint
lrwxrwxrwx root root 20 B Mon Mar 11 01:19:15 2024  /etc/alternatives/bugpoint ⇒ /usr/bin/bugpoint-17

it is advisable to set the expected permissions via %attr(777,root,root)

Aaron Puchert (aaronpuchert) - 3 months ago

author source maintainer

My understanding is that these symlinks are installed by update-alternatives, and the %ghost files are just to track the symlinks as belonging to a package. After installation, the permissions seem to be as expected, and rpm -V doesn't complain about them.

This is in fact unchanged from previous LLVM versions. I could change it, but then it should probably be changed for all versions.

The Wiki also recommends plain %ghost without %attr. Also, I wonder why RPM can't just default to 777 for symlinks? Regular files don't need an explicit 755 as well. Or is the apparent 000 just meaningless for %ghost files?

Reinhard Max (rmax) - about 2 months ago

@aaronpuchert, it looks like this change broke build for PostgreSQL versions up to 15 (but not 16). The PostgreSQL server that gets started as part of the regression test suite crashes with a segfault. It does not happen when I disable LLVM support or build the affected PostgreSQL versions with LLVM 17.

Each time the PostgreSQL server segfaults the kernel logs this:

[ 9202.373975] [ T8029] postgres[8029]: segfault at 11d ip 00007f9dd38efedb sp 00007ffde8247850 error 4 in libLLVM.so.18.1[7f9dd29f4000+3a17000] likely on CPU 3 (core 3, socket 0)
[ 9202.373988] [ T8029] Code: 48 85 db 48 0f 44 c3 48 8b 48 30 80 79 e8 1d 48 8d 41 e8 bd 00 00 00 00 48 0f 44 e8 75 d1 8b 49 ec c1 e1 05 48 29 c8 4c 8b 38 <41> 0f b6 07 83 f8 1c 72 bc 83 c0 df 83 f8 33 77 b4 49 0f a3 c2 73

Do you have any idea what could be causing (or triggering) this?

Aaron Puchert (aaronpuchert) - about 2 months ago

author source maintainer

I don't know what's causing this, but I assume it simply doesn't support LLVM 18 yet. PostgreSQL 15.6 for example came out on February 8, but the first release of LLVM 18 was tagged on March 6. So there might be changes in LLVM 18 that PostgreSQL hasn't adapted to yet.

For now I'd just go back to LLVM 17 and try again with the next version. If that still doesn't work, we should investigate, but for now it's not surprising.