Arch Linux

I can confirm this now when building in a clean chroot as well... (x86_64 without [testing] enabled):

rch -I../nptl/sysdeps/x86_64 -I../sysdeps/x86_64 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -I../nptl -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/include -isystem /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/include-fixed -isystem /usr/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DNOT_IN_libc=1 -DIS_IN_libm=1 -o /build/src/glibc-build/math/s_ilogb.o -MD -MP -MF /build/src/glibc-build/math/s_ilogb.o.dt -MT /build/src/glibc-build/math/s_ilogb.o
make[2]: *** [/build/src/glibc-build/math/s_floor.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/build/src/glibc/math'
make[1]: *** [math/others] Error 2
make[1]: Leaving directory `/build/src/glibc'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Build failed, check /tmp/WORK/chroot64/facade/build

graysky: your report does not even include the build error...

Edit: I now realize you are the original reporter too. So it is only your second comment that does not include it.

Please give details on your CFLAGS etc. They do not seem to be the default.

Allan - building outside of the chroot (original report):

CFLAGS="-march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
CXXFLAGS="${CFLAGS}"

Building inside of the chroot used the makepkg.conf that pacman provides; I didn't edit it.

I should add that I have been using this set of CFLAGS for a long time and never had a problem building the toolchain before.

Inside the chroot, are all the packages as provided by Arch (i.e. not rebuilt yourself)?

Correct:

CHROOT=/tmp/WORK/chroot
mkdir $CHROOT
sudo mkarchroot $CHROOT/root base base-devel sudo
cp /var/abs/core/glibc ./ && cd glibc
sudo makechrootpkg -c -r $CHROOT

I can not replicate on multiple machines...

Can you post the build log from the clean chroot?

@Allan - I just nuked the chroot and rebuilt. This time it completed without error. I then edited $CHROOT/root/etc/makepkg.conf changing the CFLAGS and CXXFLAGS from:

CFLAGS="-march=x86_64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
CXXFLAGS="-march=x86_64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"

to:

CFLAGS="-march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
CXXFLAGS="-march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"

When I repeated the build, it errored out as it did outside of my chroot. I cannot explain why it didn't complete the first time; I know I didn't edit anything when constructing the chroot.

In any case, it seems as though the march=native CFLAG is to blame. Is this an upstream regression or something in our files? Again, I have been using the march=native CFLAGS since gcc v4.2

EDIT: Failing to build with the march=native CFLAGS is a problem since using a custom set of CFLAGS is the whole reason why users would want to rebuild the tool chain in the first place.

This is likely caused by the "math64crash" patch which is a hack that works for -march=x86_64. When you use -march=native, the compilation is going down a different code path which this will break.

Nothing I can do about this until upstream fixes the crashing.

Thanks, Allan. Just want our stuff to be as rock stable as possible. You wanna close the bug report since it's upstream and not us?

=============================
CFLAGS="-march=core2 -mtune=generic -O2 -pipe -msse4.1 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu,--no-keep-memory"
=============================

I compile unsuccessful，I remove -msse4.1, compile successful

Try this version of the patch.

@Allan - You're the man. Built successfully using your new patch in a clean chroot using:

$ grep FLAGS $CHROOT/root/etc/makepkg.conf
CFLAGS="-march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu"
MAKEFLAGS="-j4"

Anyone care to test this package out?
http://dev.archlinux.org/~allan/glibc-2.15-3.1-x86_64.pkg.tar.xz

Thank you Allan.
With your new package everything works fine. I am now able to use Xen again :-)

Works here too, Allan.

Not much I can do to fix this properly at the moment. If you are rebuilding glibc-2.15-4, remove the "rm sysdeps..." line. You will want to change "--enable-multi-lib" to "--disable-multi-lib" anyway...