clang: missing symbolic links #7

New Issue

sdaoden · 2024-06-22T21:34:35+02:00

sdaoden commented

2024-06-22 21:34:35 +02:00

When running scan-build of clang suite it fails because it expects analyzers in different paths.
I need to to install symlinks (since at least .4 update of clang, 'not using it that often)

ln -s /usr/lib/clang/ccc-analyzer /usr/bin/
ln -s /usr/lib/clang/c++-analyzer /usr/bin/

When running scan-build of clang suite it fails because it expects analyzers in different paths. I need to to install symlinks (since at least .4 update of clang, 'not using it that often) ln -s /usr/lib/clang/ccc-analyzer /usr/bin/ ln -s /usr/lib/clang/c++-analyzer /usr/bin/

👎 1

tb commented

2024-06-23 10:39:18 +02:00

If that's so, you should report a bug upstream. I have never had an issue with it like it is.

tb closed this issue

2024-06-23 10:39:18 +02:00

sdaoden commented

2024-06-24 16:17:43 +02:00

The package is broken without the symbolic links, if it worked for you, you never used it.

$ scan-build make -f s-postgray.makefile CC=clang
scan-build: 'ccc-analyzer' does not exist at '/usr/bin/ccc-analyzer'

The package is broken without the symbolic links, if it worked for you, you never used it. $ scan-build make -f s-postgray.makefile CC=clang scan-build: 'ccc-analyzer' does not exist at '/usr/bin/ccc-analyzer'

sdaoden reopened this issue

2024-06-24 16:17:43 +02:00

tb commented

2024-06-24 18:14:57 +02:00

I have never said that I used that tool, I said the port works for what I want from it and that if it belongs in the bindir, this ticket belongs upstream, not here.

In addition, the way that you express yourself makes it sound like it has been in /usr/bin, but going through the git history reads to me like it never was. [1]

Distros that ship it seem to have it live in libexecdir [2,3], exactly like we do - therefor, for me, this is a no and stays a no if you don't have any better arguments. Please go seek help upstream.

1:

clang/Pkgfile Line 41 in 6d0d5af670

mv $PKG/usr/libexec/{c++-analyzer,ccc-analyzer} $PKG/usr/lib/clang

2: https://src.fedoraproject.org/rpms/clang/blob/rawhide/f/clang.spec#_606 (libexec dir)
3: https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-devel/clang/clang-18.1.8.ebuild (no special move so.. libexec dir?)

I have never said that I used that tool, I said the port works for what I want from it and that if it belongs in the bindir, this ticket belongs upstream, not here. In addition, the way that you express yourself makes it sound like it has been in /usr/bin, but going through the git history reads to me like it never was. [1] Distros that ship it seem to have it live in libexecdir [2,3], exactly like we do - therefor, for me, this is a no and stays a no if you don't have any better arguments. Please go seek help upstream. 1: https://git.crux.nu/ports/opt/src/commit/6d0d5af670cc90c0997c52a2692fc19efe732c19/clang/Pkgfile#L41 2: https://src.fedoraproject.org/rpms/clang/blob/rawhide/f/clang.spec#_606 (libexec dir) 3: https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-devel/clang/clang-18.1.8.ebuild (no special move so.. libexec dir?)

tb closed this issue

2024-06-24 18:14:57 +02:00

Sign in to join this conversation.