Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39442 - [libc++abi] build fails
Attached to Project:
Community Packages
Opened by Joel Teichroeb (klusark) - Saturday, 15 March 2014, 04:23 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 06 September 2014, 01:17 GMT
Opened by Joel Teichroeb (klusark) - Saturday, 15 March 2014, 04:23 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 06 September 2014, 01:17 GMT
|
DetailsDescription:
+ clang++ -c -g -O3 -fPIC -std=c++0x -stdlib=libc++ -fstrict-aliasing -Wstrict-aliasing=2 -Wsign-conversion -Wshadow -Wconversion -Wunused-variable -Wmissing-field-initializers -Wchar-subscripts -Wmismatched-tags -Wmissing-braces -Wshorten-64-to-32 -Wsign-compare -Wstrict-aliasing=2 -Wstrict-overflow=4 -Wunused-parameter -Wnewline-eof -I../include ../src/stdexcept.cpp ../src/stdexcept.cpp:69:44: error: expected ';' at end of declaration list __libcpp_nmstr(const __libcpp_nmstr& s) _LIBCPP_CANTTHROW; ^ ; ../src/stdexcept.cpp:70:55: error: expected ';' at end of declaration list __libcpp_nmstr& operator=(const __libcpp_nmstr& s) _LIBCPP_CANTTHROW; ^ ; ../src/stdexcept.cpp:71:22: error: expected ';' at end of declaration list ~__libcpp_nmstr() _LIBCPP_CANTTHROW; ^ ; 3 errors generated. ==> ERROR: A failure occurred in build(). Aborting... Steps to reproduce: sudo extra-x86_64-build |
This task depends upon
Closed by Daniel Micay (thestinger)
Saturday, 06 September 2014, 01:17 GMT
Reason for closing: Fixed
Additional comments about closing: libc++abi-3.5.0-1
Saturday, 06 September 2014, 01:17 GMT
Reason for closing: Fixed
Additional comments about closing: libc++abi-3.5.0-1
Comment by Daniel Micay (thestinger) -
Monday, 28 April 2014, 08:50 GMT
It doesn't seem that there's any sane way to deal with this beyond convincing upstream to do a release or switching to following trunk. There hasn't been a release as part of the LLVM project since 3.2... perhaps libc++ feels like working with libsupc++ again, but our bleeding edge gcc upgrades were problematic before.