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#35114 - [gcc-multilib] Cannot build 32-bit code outside of a chroot
Attached to Project:
Community Packages
Opened by Laurent Carlier (lordheavy) - Monday, 06 May 2013, 15:11 GMT
Last edited by Laurent Carlier (lordheavy) - Monday, 06 May 2013, 17:17 GMT
Opened by Laurent Carlier (lordheavy) - Monday, 06 May 2013, 15:11 GMT
Last edited by Laurent Carlier (lordheavy) - Monday, 06 May 2013, 17:17 GMT
|
DetailsDescription:
I cannot build anymore 32-bit code outside. It was working fine with gcc-4.7.x. This is segfaulting with the following error, for example building a lib32 version of mesa: --config.log-- configure:4723: $? = 0 configure:4725: ar cru libconftest.a conftest.o >&5 Two passes with the same argument (-alloca-hoisting) attempted to be registered! ./configure: line 4726: 32013 Segmentation fault (core dumped) $AR cru libconftest.a conftest.$ac_objext 1>&5 configure:4728: $? = 139 configure:4734: ar -NOLOGO -OUT:conftest.lib conftest.o >&5 ar: invalid option -- 'O' -------------- Or lib32-apitrace from aur (https://aur.archlinux.org/packages/lib32-apitrace) https://paste.xinu.at/wIk/ Another user with this bug: http://forums.pcsx2.net/Thread-Arch-Can-t-seem-to-be-able-to-compile-from-AUR Of course, multilib-devel is installed. |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Monday, 06 May 2013, 17:17 GMT
Reason for closing: Won't fix
Additional comments about closing: Not our bug.
Monday, 06 May 2013, 17:17 GMT
Reason for closing: Won't fix
Additional comments about closing: Not our bug.
I have both regular llvm from our repos and a svn version that i use for mesa from git
(available here: http://pkgbuild.com/~lcarlier/mesa-git/x86_64/) named llvm-amdgpu-lib-svn.
Removing regular one or svn one fix the bug. It's weird because they are x86_64 libs, not 32-bit.
Any ideas ?
So closing this bug report as "Not our bug"