Package Details: zapcc-git r57.9bd04e761-1

Git Clone URL: (read-only, click to copy)
Package Base: zapcc-git
Description: caching C++ compiler based on clang, designed to perform faster compilations
Upstream URL:
Licenses: custom:University of Illinois/NCSA Open Source License
Conflicts: zapcc
Provides: zapcc
Submitter: xantares
Maintainer: PhCl
Last Packager: PhCl
Votes: 7
Popularity: 0.074560
First Submitted: 2018-06-17 17:46
Last Updated: 2018-11-18 18:46

Latest Comments

1 2 Next › Last »

PhCl commented on 2018-11-18 18:49

It should now work to install it next to clang. If the headers are not found, you can explicitly pass them:

zapcc++ -I /usr/lib/zapcc/7.0.0/include

PhCl commented on 2018-11-15 02:13

Need to test a bit more but for me it works if I rename /usr/lib/clang to /usr/lib/zapcc before creating the package. Here is the current version, in case someone wants to give it a try:

mbunkus commented on 2018-11-13 08:48

Building the package today I get file system conflicts with clang (one example of many similar lines):

zapcc-git: /usr/lib/clang/7.0.0/include/xmmintrin.h exists in filesystem (owned by clang)

The "zapcc" community package doesn't have this problem and can be installed alongside the "clang" package, probably because it installs in a different place (/usr/lib/clang/5.0.0/include/xmmintrin.h for the aforementioned file). Current git seems to be based on newer clang and uses a higher version number, it seems.

If this isn't solvable, "zapcc-git" should conflict with "clang".

xyproto commented on 2018-06-29 08:10

When using zapcc together with SCons, I had to pass the --gcc-toolchain=/usr flag to zapcc.

zapcc is roughly twice as fast as clang here, which is neat!

Thanks for maintaining.

diggit commented on 2018-06-19 09:52

@xantares It's ok now. I had old PKGBUILD. Thanks for updating!

xantares commented on 2018-06-19 09:11

@diggit I dont get any conflicts with these packages, are you up to date ?

diggit commented on 2018-06-19 07:48

I have file conflicts with: llvm, clang, llvm-libs. If I understand, zapcc is fork of llvm and those conflicting packages should be added to PKGBUILD conflicts and provides. Am I right?

Other solution would be install to /opt

xantares commented on 2018-06-18 21:02

fixed, I proposed the patch upstream

this thing is super fast!

hcorion commented on 2018-06-18 20:27

Looks like patch is no longer needed?

FoPref commented on 2018-06-18 10:15

Package does not link on my system. Hundreds of undefined reference errors.