Arch Linux User Repository

@jetm might I suggest reinstating the pinned and top message?

IMHO it still makes sense to set the out of date flag even if the clang dependency is not yet up to date.

There is no pinned message and has not been such at least since I first saw this package a few months ago.

@pattop v18 depends on clang v14, and Arch Linux recently upgraded it. The out-of-date flag was wrong because the submitter didn't know about that requirement. In this package, the out-of-date flag is constantly submitted because the submitters don't know the iwyu versions have a solid dependency on specific clang versions. The latter takes time to update in Arch Linux. I stopped removing the out-of-date flag because they continue doing it, even with a pinned and top message.

@jetm it was flagged out of date almost 3 months ago by @MarsSeed as v0.18 was released. That's why I submitted an orphan request.

@pattop clang was updated very recently to v14 in Arch Linux. This package is not an orphan. I will update it this week.

This was flagged out of date on the 9th of April (~3 months ago) and the current maintainer has not updated it. I've submitted an orphan request.

Diff for support with clang v14.0

diff --git a/PKGBUILD b/PKGBUILD
index 057ae3c..9226518 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,16 +2,16 @@
 # Old Maintainer: Manuel Mendez <mmendez534@gmail.com>

 pkgname=include-what-you-use
-pkgver=0.17
+pkgver=0.18
 pkgrel=1
-_clang_major=13
+_clang_major=14
 _clang_minor=0
 _clang_ver="${_clang_major}.${_clang_minor}"
 pkgdesc="A tool for use with clang to analyze #includes in C and C++ source files"
 url="http://include-what-you-use.org"
 license=('LLVM Release License')
 source=("https://github.com/${pkgname}/${pkgname}/archive/${pkgver}.tar.gz")
-sha512sums=('2439e3dd37163d3953fc1e45614fb4325be093a162f25d0f45fa8126b2313942a7c8d45ed12454dfbfeb4cb4fcf2f4e3eebdc0ec5da14dad23533f7a0bf58290')
+sha512sums=('bfce2ff00b572961dcba83519959cbedaf1c2ec4bd4e0a2b8b6d12f440887ee64a1c9970fa1a80c7517898ce936219436ab709893cfed92891c5c2aa5d76770e')
 arch=('x86_64')
 _min="${_clang_ver}"
 _max=$((_clang_major + 1)).0

Patch is not required now for clang 14.0.6.

Patch for 0.18 with mentioned simplification: https://pastebin.com/nkC5xCZM Upd. fixed tabs in patch.

Same question @sebschrader: would you mind updating the version? Currently, this leads to a dependency conflict with the newest arch repo version of clang (v14.0.6-1).

The official clang package has been bumped to version 14. Can you update to 0.18v?

May I suggest simplifying PKGBUILD by using -B build, -DCMAKE_INSTALL_PREFIX=/usr and calling cmake --build and cmake --install instead of hardcoded ninja counterparts? See https://wiki.archlinux.org/title/CMake_package_guidelines#Template.

iwyu 0.17 is released for Clang v13, but I am getting a build error:

make: make: Permission denied
make: *** [Makefile:146: all] Error 127

I did open a case in upstream: https://github.com/include-what-you-use/include-what-you-use/issues/979

Edit: Package updated. As a workaround, I changed CMake to generate Ninja. Maybe is a CMake bug

Clang 13 is out

For the impatient ones...

diff --git a/PKGBUILD b/PKGBUILD
index 862a5c9..e927299 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,16 +1,16 @@
 # Maintainer: Manuel Mendez <mmendez534@gmail.com>

 pkgname=include-what-you-use
-pkgver=0.15
+pkgver=0.16
 pkgrel=1
-_clang_major=11
+_clang_major=12
 _clang_minor=0
 _clang_ver="${_clang_major}.${_clang_minor}"
 pkgdesc="A tool for use with clang to analyze #includes in C and C++ source files"
 url="http://include-what-you-use.org"
 license=('LLVM Release License')
 source=("https://github.com/${pkgname}/${pkgname}/archive/${pkgver}.tar.gz")
-sha512sums=('db15efa9b92015322e9a188be6cf16a5c6fd71271c94fde45245676f2a8f6ffe4c7837e3b0bb5f9be6cbe78aab245129816a3b046c44c261a2b7ab5c3a9ea7b9')
+sha512sums=('2923e18c40ddc5c03458b896d991adde03d489c6645ecc3cc4f69a508e323534afdef3233943e99533ffc21c64a10a8a5c635dc4797a61edf09d0a7a918a3cd5')
 arch=('x86_64')
 _min="${_clang_ver}"
 _max=$((_clang_major+1)).0

Wait for the maintainer to bump the clang dependency.

I was able to build the tool with the latest master and clang 11 as suggested here https://github.com/include-what-you-use/include-what-you-use/issues/850#issuecomment-727545771 with this PKGBUILD by just bumping the _max to _clang_major+2.

Clang 10 is out, so this package is now out of date. Hopefully the maintainer updates the package soon.

Checking the git history, the Python 2 requirement has been baked in since the initial commit. As best I can determine, the iwyu codebase has since been updated and is expected to be entirely Python 3 clean.

Could you try removing the sed lines and python2 dependency from this PKGBUILD and see if everything just works for you? (I built it myself and it seems fine.) We can report any problems we find with the Python 3 support upstream.

Looking forward for the update, thank you :)

Clang v11 is out, but the project upstream is not updated yet. I will update after upstream project update. See:

https://github.com/include-what-you-use/include-what-you-use/issues/850

@a216: Done. Thanks!

This project doesn't seem to show up in a search for "iwyu" - could this term be added as a keyword?

@Aetf: Clang v8 is out, but project upstream is not updated yet. I will update after upstream project update. Removing flag.

Clang v8 is out...

Please update to use the most recent clang v7.

And please replace patch -Np1 -i "../../fix-clang-6.patch" with patch -Np1 -i "${srcdir}/fix-clang-6.patch" as you can not rely on a relative position for source files.

The PKGBUILD is currently broken. Please add fix-clang-6.patch to the sources list to fix it.

@Parkotron Ran into the same error building by hand from github (tag clang_6.0). Cherry-picking more commits from master solves the issue. I suspect it's due to https://github.com/include-what-you-use/include-what-you-use/commit/0003739b52e0bcefa574ed6dbc5dc7cf78da3cb4. See also https://github.com/include-what-you-use/include-what-you-use/issues/499

I just attempted to modify the PKGBUILD for the recently released v0.10 (the Clang 6.0 version). After just changing the versions and hashes, everything build and installed without issue. Unfortunately, the tool fails to run, yielding

LLVM ERROR: inconsistency in registered CommandLine options
: CommandLine Error: Option 'asan-instrument-assembly' registered more than once!

Apparently this is due to linking against LLVM both statically and dynamically, but at this point I'm in over my head. Hopefully smarter folks will to take a look at packaging 0.10 soon.

It seems that the PKGBUILD could use clang50/llvm50 now that the repo packages are 6.0. Quick and dirty patch that does not use $_clang_major/$_clang_minor: https://ptpb.pw/AH_XTjlQV2P2ne1dJYUbaEkc99jN.patch

I had to change line 31 that reads

Sorry, I dropped thank chunk during a git rebase.

I had to change line 31 that reads

cd $srcdir/$pkgname/build

to

cd "$srcdir/$pkgname-clang_${_clang_ver}/"build

then package() worked

Upstream didn't post a release on their website but a release on GitHub.

See this GitHub issue: https://github.com/include-what-you-use/include-what-you-use/issues/462