Package Base Details: libc++

Git Clone URL: https://aur.archlinux.org/libc++.git (read-only)
Submitter: WoefulDerelict
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 236
Popularity: 5.949938
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 9 ... Next › Last »

mb1cnhqge7c5y5vs commented on 2018-08-26 17:10

How long is this supposed to take to build? I've been trying to install it for half an hour and the bottom of my terminal displays:

-- Testing: 5874 tests, 4 threads --
Testing: 0 .. 10.

If it's only up to 10 and it has 5874 to go... should I expect this to take weeks to install?

WoefulDerelict commented on 2018-08-25 21:37

Rosslaew: I'm unsure of the exact nature of the failure; however, it centres around the components of the test suite designed to evaluate support of the fr_FR.UTF-8 locale. None of the other localisations cause issues with the tests. I suspect this warrants further investigation; however, you can avoid the failures by building libc++ in a clean chroot or passing --nocheck to makepkg and skipping the test suite. Granted, if the failed tests are anything to go by you may experience some issues with applications using libc++ and the fr_FR.UTF-8 locale should that application attempt to localise currency: quite possibly inappropriate decimal and thousands separators.

Rosslaew commented on 2018-08-24 21:02

I want to report that I could not build libc++ even with makepkg, until i commented out my fr_FR locales in /etc/locale.gen and rerun locale-gen. So despite following the localization guide, it failed with French locale. I am unsure where exactly the blame is though.

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.

dpriedel commented on 2018-08-12 18:40

SOLVED. Building against the latest clang-6.0.1-3 packages works.

I'm having a problem building this library. I get most of the way through the build then this error pops up:

[56/59] Linking CXX static library lib/libc++.a
FAILED: lib/libc++.a 
: && /usr/bin/cmake -E remove lib/libc++.a && /usr/bin/ar qc lib/libc++.a  projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/algorithm.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/any.cpp.o

[snip]

projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/valarray.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/variant.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/vector.cpp.o && /usr/bin/ranlib lib/libc++.a && :
: CommandLine Error: Option 'asm-instrumentation' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
[57/59] Linking CXX shared library lib/libc++.so.1.0
ninja: build stopped: subcommand failed.

I can't find where this is controlled from.

Thanks for any help.

Dave R.

maxlefou commented on 2018-08-05 13:14

Simple question: Is this package eventually available in any unofficial user repository? I'm getting tired of either using --nocheck or wait almost 2 hours to get it to fail in the end... :/

Joan31 commented on 2018-07-21 14:14

I know why I can't import the keys using gpg.

I use systemd-networkd and systemd-resolved services.

However, it is a common practise to store DNS resolver information in /etc/resolv.conf, and many applications still rely on /etc/resolv.conf. Thus for compatibility reason, we have to create a symlink to /etc/resolv.conf as follows.

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

And now if we try to execute gpg --recv-keys 474E22316ABF4785A88C6E8EA2C794A986419D8A it work fine.

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 2018-07-21 11:28

SupKurtJ: As has already been mentioned earlier, AUR helpers are not supported. yaourt conducts the build in /tmp which is volatile and resides entirely in memory by default [https://wiki.archlinux.org/index.php/tmpfs]

The libc++ test suite has some memory heavy functions which users have already noted can cause issues when using yaourt on systems with limited memory. This is not an issue when building with makepkg. You can pass --nocheck to makepkg in order to skip the test suite as noted in the pinned post.

WoefulDerelict commented on 2018-07-20 17:12

SupKurtJ: It is difficult to to accurately diagnose a problem without the program's output. There are a number of factors that can cause key retrieval to fail. The most common culprit is strict firewalls that block the default HKP/HKPS port. You could try specifying a different port and see if that resolves the issue. The default HTTP and HTTPS ports tend to be the most viable options. The following is an example using HKPS and the http over TLS/SSL port 443.

gpg --keyserver hkps://pgp.mit.edu:443 --recv-keys 474E22316ABF4785A88C6E8EA2C794A986419D8A

Here is an example using the standard hypertext transfer protocol port 80.

gpg --keyserver hkps://pgp.mit.edu:80 --recv-keys 474E22316ABF4785A88C6E8EA2C794A986419D8A

You can get more detailed output from gpg using the -vvv and --debug-all options. If neither of those work you can skip the PGP signature check by passing --skippgpcheck to makepkg as noted in the pinned post above.