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#55279 - [clingo] Why is clang++ enforced?
Attached to Project:
Community Packages
Opened by Andreas Baumann (andreas_baumann) - Friday, 25 August 2017, 08:36 GMT
Last edited by Alexander F. Rødseth (xyproto) - Friday, 01 September 2017, 10:26 GMT
Opened by Andreas Baumann (andreas_baumann) - Friday, 25 August 2017, 08:36 GMT
Last edited by Alexander F. Rødseth (xyproto) - Friday, 01 September 2017, 10:26 GMT
|
DetailsDescription:
Just a question: is clang++ required? Doesn't it build also with g++. clang++ seems to fail in C++ atomics on 32-bit. See also discussion on https://github.com/potassco/clingo/issues/57. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Friday, 01 September 2017, 10:26 GMT
Reason for closing: No response
Friday, 01 September 2017, 10:26 GMT
Reason for closing: No response
It only works correctly with clang++, yes. And it does not work for i686 (which will be dropped in November, in any case).