This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: glibc configure error: forced unwind support is required
- From: Ian Lance Taylor <iant at google dot com>
- To: suma sharma <sumasamyukta at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Wed, 01 Apr 2009 13:18:26 -0700
- Subject: Re: glibc configure error: forced unwind support is required
- References: <aaa6f2a40904010940p7abb79c2mc6631a2489e7522@mail.gmail.com>
suma sharma <sumasamyukta@gmail.com> writes:
> GLIBC:
> ------
> CC="${TARGET}-gcc \
> AR=${TARGET}-ar \
> RANLIB=${TARGET}-ranlib \
> ${GLIBC_SRC}/configure \
> --build=${HOST} \
> --host=${TARGET} \
> --prefix=/usr \
> --enable-shared \
> --enable-kernel=2.6.0 \
> --disable-profile \
> --disable-debug \
> --with-headers=${HEADERS_DIR} \
> --with-tls \
> --with-__thread \
> --without-cvs \
> --without-gd \
> --enable-add-ons=nptl &> configure.out
>
> I am getting an error in the glibc configure stage. The error is as
> follows:
> ------------------------------------------------------------------------
> "checking size of long double... 12
> running configure fragment for sysdeps/i386/elf
> checking for i386 TLS support... yes
> running configure fragment for nptl/sysdeps/pthread
> checking for forced unwind support... no
> configure: error: forced unwind support is required"
> ------------------------------------------------------------------------
This question might be better directed to the glibc maintainers. See
http://www.gnu.org/software/libc/ .
The general rule for this sort of thing is to look at the config.log
file. It will show the test that the configure script tried to run, and
the errors that it got.
Ian