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#43538 - gcc / g++ include cstdlib with -m32 compiler flag broken
Attached to Project:
Arch Linux
Opened by Thijs Brouwer (tbrouwer) - Thursday, 22 January 2015, 09:53 GMT
Last edited by Allan McRae (Allan) - Thursday, 22 January 2015, 10:37 GMT
Opened by Thijs Brouwer (tbrouwer) - Thursday, 22 January 2015, 09:53 GMT
Last edited by Allan McRae (Allan) - Thursday, 22 January 2015, 10:37 GMT
|
DetailsDescription:
#include <cstdlib> together with -m32 compiler flag leads to error: expected unqualified-id before ‘__int128’ Not sure if this bug belongs with arch or with the gcc guys and gals. Additional info: * package version(s) gcc (GCC) 4.9.2 20141224 (prerelease) * config and/or log files etc. $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Steps to reproduce: $ g++ -m32 test.cxx In file included from test.cxx:1:0: /usr/include/c++/4.9.2/cstdlib:178:10: error: expected unqualified-id before ‘__int128’ inline __int128 ^ $ cat test.cxx #include <cstdlib> int main() { return 0; } $ gcc --version gcc (GCC) 4.9.2 20141224 (prerelease) Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 22 January 2015, 10:37 GMT
Reason for closing: Not a bug
Additional comments about closing: Use gcc in [multilib] if you want multilib support
Thursday, 22 January 2015, 10:37 GMT
Reason for closing: Not a bug
Additional comments about closing: Use gcc in [multilib] if you want multilib support