public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Carmelo Amoroso <carmelo73@gmail.com>
To: suma sharma <sumasamyukta@gmail.com>
Cc: glibc-bugs@sourceware.org
Subject: Re: glibc configure error: forced unwind support is required
Date: Thu, 02 Apr 2009 15:39:00 -0000 [thread overview]
Message-ID: <49D4DC34.6060505@gmail.com> (raw)
In-Reply-To: <aaa6f2a40904010941y4d2eaa7ey56ac729df1708f4b@mail.gmail.com>
suma sharma wrote:
> Hi,
> I am trying to build a native toolchain using the following sources:
> Binutils-2.19
> Gcc-4.4-20090327
> Glibc-2.9
> Linux kernel headers-2.6.29
>
> I am using the following variables:
> HOST: i686-linux
> TARGET: i386-linux
>
> The configure options specified for the various stages of the build are
> as follows:
> LINUX KERNEL HEADERS:
> ---------------------
> HEADERS_SRC_DIR=/home/sumas/src/linux-2.6.29
> cp -r ${HEADERS_SRC}/include/linux ${HEADERS_DIR}
> # HEADERS_DIR=/home/sumas/prefix/i386-linux/sys-root/usr/include
> cp -r ${HEADERS_SRC}/include/asm-x86 ${HEADERS_DIR}/asm
> cp -r ${HEADERS_SRC}/include/asm-generic/ ${HEADERS_DIR}/include
>
> BINUTILS:
> ---------
> ${BINUTILS_SRC}/configure \
> --host=${HOST} \
> --target=${TARGET} \
> --prefix=${PREFIX} \ #PREFIX=/home/sumas/prefix
> --with-sysroot=${SYSROOT_DIR} \
> #SYSROOT_DIR=$PREFIX/i386-linux/sys-root
> --disable-nls &> configure.out
>
> GLIBC HEADERS:
> --------------
> CC=gcc \
> ${GLIBC_SRC}/configure \
> --build=${HOST} \
> --host=${TARGET} \
> --prefix=/usr \
> --disable-sanity-checks \
> --without-cvs \
> --with-__thread \
> --with-headers=${HEADERS_DIR} \
> --enable-add-ons=nptl &> configure.out
>
> BOOTSTRAP GCC:
> -------------
> ${GCC_SRC}/configure \
> --host=${HOST} \
> --target=${TARGET} \
> --prefix=${CORE_PREFIX} \ #
> CORE_PREFIX=${BUILD_DIR}/gcc-core-prefix
> --with-local-prefix=${SYSROOT_DIR} \
> --with-sysroot=${SYSROOT_DIR} \
> --without-headers \
> --without-libs \
> --disable-nls \
> --disable-shared \
I think that you need --enable-shared for generating libgcc,
that will provide stack unwind support.
> --with-tls \
> --enable-threads=posix \
> --enable-symvers=gnu \
> --with-gmp=/home/sumas/linux-gmp-mpfr/prefix
> --with-mpfr=/home/sumas/linux-gmp-mpfr/prefix \
> --disable-__cxa_atexit \
> --enable-languages="c,c++" &> configure.out
>
> 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"
> ------------------------------------------------------------------------
>
> Could anyone please throw some light on this issue.
> Thanking you in anticipation.
>
> Regards,
> Suma Samyukta
>
next prev parent reply other threads:[~2009-04-02 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 16:41 suma sharma
2009-04-02 15:39 ` Carmelo Amoroso [this message]
2009-04-03 9:12 ` suma sharma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D4DC34.6060505@gmail.com \
--to=carmelo73@gmail.com \
--cc=glibc-bugs@sourceware.org \
--cc=sumasamyukta@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).