Package Base Details: libc++

Git Clone URL: (read-only, click to copy)
Submitter: WoefulDerelict
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 251
Popularity: 2.23
First Submitted: 2017-02-04 16:09
Last Updated: 2020-11-20 22:58

Pinned Comments

eschwartz commented on 2019-01-21 03:57

PSA: Due to repeated abuse, this package is now a ZERO-TOLERANCE ZONE for rules violations.

Hi people, sorry for the interruption if you're the majority of users just innocently doing your thing, if so, feel free to just move on. For the rest of you, this is your final reminder regarding the following points, which shall now be grounds for having your account suspended:

  • Thou shalt not complain about makepkg's validpgpkeys feature.

  • Thou shalt not complain about makepkg's check() feature.

  • Thou shalt not under any circumstances ever insult the maintainer for implementing said features.

This package is doing the correct thing, and there has been a great deal of pointless moaning and whining about it despite the pinned comments explaining why these complaints are not only null and void, but also ridiculous because they can already be disabled. This nagging stops now.

The banhammer is ready and waiting in case you still want to ignore all this on top of the Trusted User warning(s).

Alad commented on 2018-08-22 12:58

Holy shit guys. What's unclear about "AUR helpers are not supported"? Stop this incessant spam and learn how to use makepkg.

Any comments on AUR helper issues will be deleted from now on. Repeat offenders will have their accounts suspended.

WoefulDerelict commented on 2018-07-21 11:45

If you experience issues when using an AUR helper please try again using makepkg. AUR helpers are not supported here. The AUR article in the ArchWiki documents the prerequisites and supported process.

The test suite contains tests for multiple locales including: en_US.UTF-8, fr_FR.UTF-8, ru_RU.UTF-8, zh_CN.UTF-8, fr_CA.ISO8859-1 and cs_CZ.ISO8859-2. If a locale isn't present on the system the related tests will be marked as unsupported and skipped.

If you encounter issues when building with makepkg please attempt to build this in a clean chroot using using the appropriate devtools script. The Arch Linux DeveloperWiki has an article focused around building packages in a clean chroot which contains information on the devtools scripts and explains the process of building in a clean chroot:

There is an active community of users on IRC along with a vibrant Discord server and Forums should you require assistance.

Picking a fight with one of the Trusted Users is a terrible idea.

WoefulDerelict commented on 2017-02-05 03:42

This PKGBUILD verifies the authenticity of the source via PGP signatures which are not part of the Arch Linux keyring. In order to complete the process it is necessary to import the key(s) from the ‘validpgpkeys’ array into the user’s keyring before calling makepkg. There is a helpful article explaining this process by one of Arch Linux's developers located here:

Instructions on importing keys from a keyserver and how to automate the retrieval process can be found in the Arch Linux wiki here: This article also contains helpful information describing the installation of GnuPG, its configuration and usage.

Execute the following to import keys using gpg:

gpg --recv-keys <KEYID - See 'validpgpkeys' array in PKGBUILD>

The PGP signature check can be skipped by passing --skippgpcheck to makepkg.

The libc++ test suite can be skipped by passing --nocheck to makepkg.

Consult the makepkg manual page for a full list of options. []

Latest Comments

1 2 3 4 5 6 ... Next › Last »

WoefulDerelict commented on 2020-12-13 01:42

anatolik: Everything looks good to me.

anatolik commented on 2020-12-11 19:09

Thank you very much for maintaining this package.

libc++ has landed [community]. Please take a look and let me know if there are any problems.

WoefulDerelict commented on 2020-12-09 18:35

anatolik: It does seem there is a contingent of users who find having the library around useful. I guarantee the majority of them would prefer an easy to install binary package from [Community].

anatolik commented on 2020-12-08 19:09

Hi, I found this package useful and based on votes a lot of other people as well.

I would like to move it to [community] to make installation and usage easier.

What do you feel about it?

jthill commented on 2020-12-02 16:00

The PKGBUILD trips what I regard as a bug in bash, but don't expect to ever see fixed: package_libc++ is a valid shell function name, but package_libc++() { is rejected. You can source the packagebuild if you add a space before the lparen or switch to the function keyword.

rustemb commented on 2020-11-18 20:32

how to use libc++ in ArchLinux with simple hello world?

ilario commented on 2020-05-28 10:57

I acknowledge that the check() function is a sensible topic (some times it has been broken and some users complained it is inconvenient), but looking at the comments this was not asked: does it make sense to run an integration test (as those currently included in the PKGBUILD/check() function, the check-cxx function is documented here and uses LIT which is LLVM Integrated Tester) by default (as defined in makepkg.conf/BUILDENV, I know that is can be disabled with makepkg's --nocheck option) when installing a package?

WoefulDerelict commented on 2020-05-07 19:15

eschwartz: Indeed that is an argument that could be made right alongside the argument for not forcing it to build with clang. Sadly the only real argument the end users seem to bring here is that the test suite is inconvenient and I should remove the check() function. It should be filtered out and working in the latest update at any rate.

eschwartz commented on 2020-03-11 21:17


You have makepkg.conf "debug" turned on, I suspect, which means that clang is being passed -fvar-tracking-assignments by default, and clang doesn't support this.

I think an argument could be made that this should be filtered out in the PKGBUILD, since it is a stock makepkg.conf DEBUG_C(XX)?FLAGS and the PKGBUILD enforces building with clang.

tallero commented on 2020-03-11 21:11

Failing with:

-- Check for working C compiler: /usr/bin/clang -- broken
CMake Error at /usr/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message):
  The C compiler


  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/user/Projects/aur/libc++/src/build/CMakeFiles/CMakeTmp

    Run Build Command(s):/usr/bin/ninja cmTC_d7905 && [1/2] Building C object CMakeFiles/cmTC_d7905.dir/testCCompiler.c.o
    FAILED: CMakeFiles/cmTC_d7905.dir/testCCompiler.c.o 
    /usr/bin/clang   -march=native -mtune=coreI7 -O2 -pipe -fno-plt -g -fvar-tracking-assignments -fdebug-prefix-map=/home/user/Projects/aur/libc++/src=/usr/src/debug -o CMakeFiles/cmTC_d7905.dir/testCCompiler.c.o   -c testCCompiler.c
    clang-9: error: unknown argument: '-fvar-tracking-assignments'
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:49 (project)

-- Configuring incomplete, errors occurred!
See also "/home/user/Projects/aur/libc++/src/build/CMakeFiles/CMakeOutput.log".
See also "/home/user/Projects/aur/libc++/src/build/CMakeFiles/CMakeError.log".
==> ERROR: A failure occurred in build().