Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: include-what-you-use 0.22-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/include-what-you-use.git (read-only, click to copy)
Package Base:	include-what-you-use
Description:	A tool for use with clang to analyze #includes in C and C++ source files
Upstream URL:	https://include-what-you-use.org
Keywords:	c c++ format header include iwyu
Licenses:	LicenseRef-LLVM-Release-License
Submitter:	Mindless
Maintainer:	sebschrader (jetm)
Last Packager:	jetm
Votes:	45
Popularity:	0.52
First Submitted:	2011-12-03 05:58 (UTC)
Last Updated:	2024-07-06 16:25 (UTC)

Pinned Comments

jetm commented on 2023-11-10 00:05 (UTC) (edited on 2024-11-13 11:49 (UTC) by jetm)

IWYU v0.23 is out, but clang v19 has not been released in Arch Linux. Please don't flag out-of-date until the new clang version is available. Thanks.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

Arvedui commented on 2018-08-29 07:46 (UTC) (edited on 2018-08-29 07:47 (UTC) by Arvedui)

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.

selmf commented on 2018-07-01 20:34 (UTC)

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

pseyfert commented on 2018-05-29 17:18 (UTC)

@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

Parkotron commented on 2018-05-15 18:24 (UTC)

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.

spider-mario commented on 2018-04-29 21:06 (UTC) (edited on 2018-04-29 21:07 (UTC) by spider-mario)

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

sebschrader commented on 2018-02-24 00:34 (UTC)

I had to change line 31 that reads

Sorry, I dropped thank chunk during a git rebase.

Tristero commented on 2018-02-23 16:34 (UTC)

I had to change line 31 that reads

cd $srcdir/$pkgname/build

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

then package() worked

sebschrader commented on 2018-02-22 21:21 (UTC)

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

marmistrz commented on 2017-07-06 10:01 (UTC)

@mmlb, and the very issue says that: > In the meantime, I've been using current master with llvm 4.0 and it "seems" to be working ;) Isn't it just the problem with the prebuilt binaries?

mmlb commented on 2017-04-24 21:41 (UTC)

@johnchen902, iwyu is very much tied to a specific version of clang/llvm. You can track llvm 4.0 release status here https://github.com/include-what-you-use/include-what-you-use/issues/397.