Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Moschny <thomas.moschny@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Exception support
Date: Thu, 31 Aug 2006 09:05:18 +0200	[thread overview]
Message-ID: <200608310905.18546.thomas.moschny@gmx.de> (raw)
In-Reply-To: <c1bf1cf0608301523u1970bd8en61c048b94e796167@mail.gmail.com>

ON Thursday 31 August 2006 00:23 Ed Swierk wrote:
> On 8/28/06, Thomas Moschny <thomas.moschny@gmx.de> wrote:
> > is there a way to get a toolchain built for i686, that supports C++
> > exceptions?
>
> I've got C++ exceptions working with gcc 4.1.1 by enabling
> BR2_GCC_USE_SJLJ_EXCEPTIONS in my buildroot configuration,

This seems to work. Btw, it took me a while to find out what 'sjlj' stands 
for :)

> and changing --disable-__cxa_atexit to --enable-__cxa_atexit in
> gcc-uclibc-3.x.mk.

I tried setting --enable-__cxa_atexit as an extra gcc option, but got an 
undefined reference afterwards.

> Apparently it is even possible to get stack unwinding to work, but I
> have not tried it myself. See the thread beginning at
> http://uclibc.org/lists/uclibc/2006-August/016090.html .

I know this thread, but it is unclear to me how to force usage of stack 
unwinding. unwind-dw2-fde.o seems not to work (that's why I started this 
thread). Now, if I edit toolchain/gcc/4.1.1/100-uclibc-conf.patch to not 
change LIB2ADDEH, then unwind-dw2-fde-glibc.o is built (and would be used), 
but it contains an undefined reference to dl_iterate_phdr.

Thomas

      reply	other threads:[~2006-08-31  7:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 22:41 [Buildroot] Exception support Thomas Moschny
2006-08-30 22:23 ` Ed Swierk
2006-08-31  7:05   ` Thomas Moschny [this message]

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=200608310905.18546.thomas.moschny@gmx.de \
    --to=thomas.moschny@gmx.de \
    --cc=buildroot@busybox.net \
    /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