Package Base Details: libc++

Git Clone URL: https://aur.archlinux.org/libc++.git (read-only)
Submitter: WoefulDerelict
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 237
Popularity: 6.061200
First Submitted: 2017-02-04 16:09
Last Updated: 2019-07-16 14:59

Pinned Comments

eschwartz commented on 2019-01-21 03:57

Hi people, this is your regular reminder to SHUT UP about validpgpkeys checks and complaints about the fact that test suites exist.

This package is doing the correct thing, and there has been a great deal of pointless moaning and whining about it, but there is also multiple pinned comments explaining why every one of those complaints is not only null and void, but retroactively ridiculous.

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

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.

https://wiki.archlinux.org/index.php/Makepkg https://wiki.archlinux.org/index.php/Arch_User_Repository

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. https://wiki.archlinux.org/index.php/Arch_User_Repository

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: https://wiki.archlinux.org/index.php/DeveloperWiki: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: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

Instructions on importing keys from a keyserver and how to automate the retrieval process can be found in the Arch Linux wiki here: https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver 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. [https://www.archlinux.org/pacman/makepkg.8.html]

Latest Comments

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

lesebas commented on 2018-10-06 16:35

I try to compile the package, by the way libc++abi is required at the installation :

résolution des dépendances… avertissement : impossible de résoudre « libc++abi=7.0.0-1 », une dépendance de « libc++ »

But libc++abi require libc++ as make dependency ?????

Morganamilo commented on 2018-10-04 16:00

Because nothing in the repos depend on it.

stefnix commented on 2018-10-04 15:47

I'm curious. Is there a reason why this is not in the standard repository?

abdulhakeem commented on 2018-10-04 12:14

Skipping the Stress Test should really be the default. Should be opt-in instead of opt-out

fightcookie commented on 2018-10-03 16:30

WoefulDerelict: Thanks a lot, that fixed it! :)

WoefulDerelict commented on 2018-10-03 16:23

fightcookie: Neither of the keys is expired.

[llewelyn@Archilochus libc++]$ gpg --list-keys B6C8F98282B944E3B0D5C2530FC3042E345AD05D
pub   rsa4096 2015-01-20 [SC] [expires: 2023-01-15]
      B6C8F98282B944E3B0D5C2530FC3042E345AD05D
uid           [ unknown] Hans Wennborg hans@chromium.org
sub   rsa4096 2015-01-20 [E] [expires: 2023-01-15]

[llewelyn@Archilochus libc++]$ gpg --list-keys 474E22316ABF4785A88C6E8EA2C794A986419D8A pub rsa4096 2018-05-03 [SC] [expires: 2019-05-03] 474E22316ABF4785A88C6E8EA2C794A986419D8A uid [ unknown] Tom Stellard tstellar@redhat.com sub rsa4096 2018-05-03 [E] [expires: 2019-05-03]

I suggest you run gpg --refresh-keys

fightcookie commented on 2018-10-03 12:38

It seems like the gpg keys are expired, is that correct? Are there newer ones with which new releases are signed?

==> Verifying source file signatures with gpg... llvm-7.0.0.src.tar.xz ... Passed (WARNING: the key has expired.) libcxx-7.0.0.src.tar.xz ... Passed (WARNING: the key has expired.) libcxxabi-7.0.0.src.tar.xz ... Passed (WARNING: the key has expired.) ==> WARNING: Warnings have occurred while verifying the signatures. Please make sure you really trust them.

WoefulDerelict commented on 2018-10-02 16:22

bastiendurel: It shouldn't be surprising that the test suite for libc++ 6.0.1 isn't compatible with clang 7.0.0. Try again with the PKGBUILD for libc++ 7.0.0.

bastiendurel commented on 2018-10-02 14:35

I build in a clean chroot and get errors in check():

Compilation failed unexpectedly!
********************
Testing Time: 1284.29s
********************
Failing Tests (7):
    libc++ :: libcxx/experimental/filesystem/class.path/path.itr/iterator_db.pass.cpp
    libc++ :: libcxx/thread/futures/futures.promise/set_exception.pass.cpp
    libc++ :: libcxx/thread/futures/futures.promise/set_exception_at_thread_exit.pass.cpp
    libc++ :: libcxx/utilities/tuple/tuple.tuple/diagnose_reference_binding.fail.cpp
    libc++ :: std/experimental/any/any.class/any.assign/copy.pass.cpp
    libc++ :: std/utilities/any/any.class/any.assign/copy.pass.cpp
    libc++ :: std/utilities/function.objects/func.wrap/func.wrap.func/func.wrap.func.con/copy_assign.pass.cpp

  Expected Passes    : 5694
  Expected Failures  : 4
  Unsupported Tests  : 169
  Unexpected Failures: 7

6 warning(s) in tests.
FAILED: projects/libcxx/test/CMakeFiles/check-cxx 
cd /tmp/libc++/src/build/projects/libcxx/test && /usr/sbin/python /tmp/libc++/src/build/./bin/llvm-lit -sv /tmp/libc++/src/build/projects/libcxx/test
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in check().
    Aborting...

version 6.0.0-1 built fine, 6.0.1-1 fails

WoefulDerelict commented on 2018-08-26 18:07

mb1cnhqge7c5y5vs: How long the build and tests will take to complete is entirely dependent on your hardware and the resources available. The build and test suite complete in about 15 minutes on a build/test machine I use which is built around an Intel i7-870 and had 16GB of RAM. This system is almost a decade old.

If you're using an AUR helper like yaourt it could be causing issues with the tests. The tests can be skipped by passing --nocheck to makepkg as noted in the pinned comments.