From: "Deepak Barua" <dbbarua@gmail.com>
To: "Andrew Haley" <aph@redhat.com>
Cc: gcc-help@gcc.gnu.org, "Daniel Jacobowitz" <drow@false.org>
Subject: Re: [help] undefined reference to `_Unwind_SjLj_Register'
Date: Mon, 24 Mar 2008 20:59:00 -0000 [thread overview]
Message-ID: <b5a19cd20803241358j36fe3f60h2fd5d16f3a12ad97@mail.gmail.com> (raw)
In-Reply-To: <47E79966.7050008@redhat.com>
Hi Andrew,
Thanks for clearing up the confusion , i have a
2.6.24.3 arm-linux kernel so i should ---enable-sjlj-exceptions while
compiling gcc-4.2.2 ...
I'll try it with my crosstool setup and get back to you...
Regards
Deepak
On 3/24/08, Andrew Haley <aph@redhat.com> wrote:
> Deepak Barua wrote:
>
> > I am trying to run crosstest for the new toolchain i
> > built but i am getting this linking error.
> > (Have attached file with errors )
> >
> > Can you tell me what seems to be the problem ...?
> >
> > I am compiling the toolchain with NPTL and TLS support for the ARM
> > architecture gcc-4.2.2 and glibc-2.7
> >
> > Should i enable sjlj exceptions while compiling gcc-4.2.2 ...?
> > But as i understand from your post
> > http://sourceware.org/ml/libc-ports/2005-11/msg00030.html
> >
> > enabling sjlj exception handling is a obsolete method of exception
> > handling .... so what can i do ....?
>
> That depends on whether it's armel or arm. This is your kernel: it'll
> be one or the other. If it's arm you use sjlj.
>
> Andrew.
>
--
Hack Hack Hack
next prev parent reply other threads:[~2008-03-24 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 9:04 Deepak Barua
2008-03-24 12:07 ` Andrew Haley
2008-03-24 20:59 ` Deepak Barua [this message]
2008-03-26 14:35 ` Deepak Barua
2008-03-26 14:39 ` Andrew Haley
2008-03-26 15:48 ` Deepak Barua
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=b5a19cd20803241358j36fe3f60h2fd5d16f3a12ad97@mail.gmail.com \
--to=dbbarua@gmail.com \
--cc=aph@redhat.com \
--cc=drow@false.org \
--cc=gcc-help@gcc.gnu.org \
/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).