Package Base Details: libc++

Git Clone URL: (read-only, click to copy)
Submitter: WoefulDerelict
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 250
Popularity: 1.40
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. []

pointhi commented on 2017-04-03 13:44

cxxabi.h is missing in the installer package

sharivegas commented on 2017-03-26 11:54

It may say that the latter of the two keys failed. Retrieve both keys in the PKGBUILD, and it'll verify properly.

That was not fun to fight with.

WoefulDerelict commented on 2017-03-06 16:34

andrewchen: I have a feeling that may come back to bite other users in the future. Thanks for reporting it back here.

andrewchen commented on 2017-03-06 07:05

@WoefulDerelict: Thanks. I found the issue. The error is due to building with the debug option enabled: the default DEBUG_CFLAGS (in makepkg.conf) includes -fvar-tracking-assignments, but the option is not supported by clang.

WoefulDerelict commented on 2017-03-05 12:41

andrewchen: Your system is failing to pass a basic check of of the compiler before the build even begins. This is most definitely not a packaging issue. This is not something I can reproduce and is way beyond the scope of maintaining the PKGBUILD.

You need to figure out why clang isn't working properly and the test is failing with that error. Checking the log file mentioned in the output would be a good place to start. There is plenty of fine documentation to reference and the Arch Linux community is available for support via forums and IRC. Fair warning: the IRC community does not like pastebin as it is blocked for some of them and commits a litany of sins. There are plenty of alternatives that won't aggravate the community to choose from.

andrewchen commented on 2017-03-05 08:05

I am getting this compile error: clang-3.9: error: unknown argument: '-fvar-tracking-assignments'

Full output:

WoefulDerelict commented on 2017-02-18 02:46

giorgosioak: I'm going to reiterate what doskoi said: trusting the key is not part of the process as the /trusted/ keys are in the validpgpkeys array. In a perfect world one could verify said fingerprints and keys via an https connection to upstream but we take the cookies they give us.

brunocodutra: That is indeed a pretty valid use case. Sadly you also present a decent argument to wait and check in with the maintainer of llvm-svn as posting libc++-svn packages would impede publishing a convenient split package that handled the entire bundle at once and was able to run the checks. It wouldn't be too hard to mock such a thing up for use in testing while the maintainer is working to resolve other issues. Issues with AMD silicon are definitely out of area of expertise.

abouvier commented on 2017-02-17 18:03

@giorgosioak You don't have to trust it if the key is in the validpgpkeys array.

giorgosioak commented on 2017-02-17 15:37

If gpg signatures can't be verified, add the key as regular user by gpg:
gpg --recv-keys KEYID
and trust it:
gpg --edit-key KEYID
When you see a gpg prompt, run command: trust
and choose full or ultimate.
Re-run build procedure. And done. Hope it helps.

brunocodutra commented on 2017-02-17 15:37

@WoefulDerelict Thanks for the heads up, in fact I was aware of those guidelines and I followed them to the best of my knowledge.
I don't know about the vast majority of users, but I believe anyone interested on llvm-svn, would also be interested on libc++-svn, which is not provided by the former yet:

For the record, these are the main changes I made to build from trunk


pkgver() {
cd "${srcdir}/llvm"

# shamelessly stolen from llvm-svn PKGBUILD
echo $(awk -F 'MAJOR |MINOR |PATCH |SUFFIX |)' \
'BEGIN { ORS="." ; i=0 } \
/set\(LLVM_VERSION_/ { print $2 ; i++ ; if (i==2) ORS="" } \
END { print "\n" }' \
CMakeLists.txt)_r$(svnversion | tr -d [A-z])

prepare() {
[[ -d llvm/projects/libcxx ]] || ln -s ${srcdir}/libcxx llvm/projects/
[[ -d llvm/projects/libcxxabi ]] || ln -s ${srcdir}/libcxxabi llvm/projects/

sed -i 's/CREDITS.TXT/CREDITS/' llvm/projects/libcxx/LICENSE.TXT
sed -i 's/CREDITS.TXT/CREDITS/' llvm/projects/libcxxabi/LICENSE.TXT
[[ -d build ]] || mkdir build